I'm amazed that this hasn't been addressed. It's been there for years.
Makes the end products impracticable for distribution in a professional setting. It's Ok if you're the only consumer ... not great for other cases.
I'm amazed that this hasn't been addressed. It's been there for years.
Makes the end products impracticable for distribution in a professional setting. It's Ok if you're the only consumer ... not great for other cases.
The relevant code starts around https://gitlab.com/graphviz/graphviz/-/blob/main/lib/common/... If this isn't right, maybe somebody can figure out why. Perhaps the loop stops sometimes on the wrong side of the boundary? Anyway, it's equally possible that when the endpoint coord is handed off to a lower level driver, the arrowhead mitering is wrong. There is no question there was once upon time explicit code to try to cope with this problem, at least in the native PSgen, but I can't find it now. Maybe it wore away as waves of open source development washed over it, along with static tables for a bunch of "standard" PS fonts.
For more background, see for example https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/s...
In the worst case, this has to be debugged for all the drivers in https://gitlab.com/graphviz/graphviz/-/tree/main/plugin
No doubt there are more details if anyone can remember them.
If nothing like that exists, I can see how it would be a very troublesome refactor.
I'm talking by heart and I could be wrong in any case.