I know Bahnschrift is a problematic font.
But the _TextObject is dropping some of the geometry:
Not considered an issue?
@Gijs perhaps?
What is the issue here exactly? If thereâs something wrong with the fontâŚnothing anyone can legally do anything about that. Fonts were never designed to be CNCâd and often need all sorts of repairs.
The issue is that the inner shape of the e is missing.
The single stroke option was only used to show that the geometry really exists.
Itâs not about machining.
i am just guessing that because the letter is selfintersecting that some form of curveboolean might take place. like when you click outside. the e then naturally would not work anymore. have you got any other letters from that font that exhibit the same issue? i mean to fix it you obviously could curveboolean the letter yourself.
I donât have Bahnschrift here to test. What happens if you make normal text and explode it?
Ok, I now see that it is a Windows font:
RH-84478 Textobject handling of (self) intersecting curves
and so do most of the fonts. I think Bahnschrift is an exception. The font itself is the bug imo.
In typography forming the glyph from a single curve is bad practice. There should be two curves, one for the outline, one for the inner cutout. Curve direction distinguishes inner and outer curves.
The question is why Rhino can show the inside of the e as text but doesnât manage to get the vector when exploded.
@Charles
I also did a number of things with Bahnschrift and had noticed that. I just ended up offsetting the outer curve of the `eâ to the inside with the stroke thickness.
Yeah, looks like the e is the only self-intersecting single curve, all the other overlaps are two or more curves. Probably something in Rhinoâs âexplode textâ algorithm that could use some fine-tuning.