Frank Dana

> This difference should not matter for Python packages, since both of these forms normalize to the same value under the hood And just to reinforce that a bit more,...

The ReadTheDocs team are also working on a `position="inline"` mode for the tag (readthedocs/addons#500), which would allow the flyout to be placed at a specific location in the theme DOM....

@2br-2b @lkk7 Indeed, in graphviz's language the pairing of `` is just another form of quoting, one which triggers interpretation of the value contained within as an "HTML-like string". Unfortunately,...

> Maybe a separate **explicit** way of adding an HTML-valued string. If it's not used, then quote everything. But that would break things for people who did it the old...

Coming back to the HTML-like strings... there is one thing that _might_ work: If we encounter a string that's surrounded by ``, what if we were to _strip off_ those...

Nope! Never mind, that still doesn't detect ``. Balls.

Oh, wait, duh, yes it DOES. Because that _is_ a valid string that we DON'T need to wrap ourselves. Got myself turned around backwards for a second, there.

@lkk7 > * `abc>` --> `>abc` --> we hit a ``so it would appear to be correct, even though it isn't? Or should we check twice, starting both from front...

Basically, it wouldn't help us determine whether _any **arbitrary** string_ is HTML-like, but it would let us make better quoting decisions about **correct** HTML-like strings that may or may not...

I've also done some experimenting just now in the [Graphviz Visual Editor](http://magjac.com/graphviz-visual-editor/), and confirmed/determined: * `` is a parse error, as I mentioned earlier * `` is also a parse...