Example:
http://dlang.org/phobos/std_process.html#.Pid.processID
The anchor name is ".Pid.processID" instead with an leading dot. That will result in ugly names when referring to that symbol:
$(XREF process, .Pid.processID)
Will expand to a link with the text:
std.process..Pid.processID
Comment #1 by andrej.mitrovich — 2013-06-15T17:39:50Z
I don't understand how that page ended up with the leading dot, when building locally this doesn't happen for me.
Comment #2 by doob — 2013-06-16T03:41:27Z
It happens for me locally and, as you see, on dlang.org as well.
Comment #3 by issues.dlang — 2013-06-16T03:49:51Z
Maybe it depends on the platform you're on for some reason? IIRC, the site gets generated on Linux, Jacob uses Mac OS X, and Andrej uses Windows, so maybe the posix builds end up adding a dot for some reason, but the Windows builds don't?
Comment #4 by andrej.mitrovich — 2013-06-16T06:03:43Z
We need a small test-case first.
Comment #5 by nick — 2014-08-09T16:38:58Z
BTW this is by design. When we added qualified anchors, I wanted to keep all existing anchors working. This would have been broken without the leading dot, e.g.:
Foo.bar
bar
Foo.bar gets the original anchor 'bar', bar also gets the new anchor '.bar'. Without the dot, an existing link to 'bar' would change from pointing to the 1st to the 2nd item.
Comment #6 by robert.schadek — 2024-12-13T18:08:15Z