Hello McNeel,
Are there any plans to implement shx fonts into Rhino? shx fonts work much better with my CNC toolpathing software. The Mecsoft single line font doesn’t work as expected.
Image of two text items in the toolpathing software:
cheers,
Nick
Normally single line fonts should automatically check the “Engraving font” setting in the TextObject command.
Rhino also has another single line font - SLF-RHN Architect - included since V7.
I know that using SHX fonts in Rhino has been asked for occasionally, but I don’t think it’s on the radar.
If you are using Text and not TextObject to generate your stuff, make sure you explode the text to get curves before exporting.
Thanks @Helvetosaur
These are just very basic scribe marks for identifying parts, so I’m not sure textobject is what I’m after. We use Textobject for our embossed work. I will look into it though.
I was using exploded text, which works, but is a pain to maintain the files. The toolpathing is now much more automated in our processes, hence the desire to just export shx fonts because then there’s no intermediate steps (exploding text, changing fonts, etc.)
I’ve tried SLF-RHN Architect also, but it works better exploded too. Image below of this font toolpathed as text.
I do a lot of toolpathing, hence the need for this to be simplified.
Are there any licencing hurdles that would get in the way of using SHX fonts?
cheers,
Nick
Hi Nick -
How are you getting your Rhino geometry into your CNC toolpathing software?
We have an SHX request on the list for DWG export, and I’ve added this thread to that ticket.
→ RH-84796 DWG Export - Font Substitution for Single Stroke Fonts
I suppose that if Rhino can substitute an SLF with an SHX during export, Rhino would need to “support” SHX fonts but there might be a need to expose more in the UI?
(Also note that we apparently read - and convert - SHX fonts during import… → RH-37900 File IO: DWG: Reading SHX font fails)
-wim
G’day @wim,
I am exporting a dxf. Perhaps there’s a simple way by just substituting *.ttf with *.shx on dxf lines such as this.
Bingo! It works manually. How about a tick box on the export options, “Export fonts as shx?” All it does is find and replace ttf to shx. Leave the font name unchanged, user needs to ensure the ttf and shx font names match.
cheers,
Nick
I am intrigued by this thread, we do a lot of CNC work yet i hadn’t come across these shx fonts - I think they from the AutoCAD world? What are their specific advantages?
We use the Rhino single line font and have not had any issues - it works very well for us.
Well, IMO, if you are exporting curves from Rhino - the result of TextObject or exploding a single-line text font - it will (should) be WYSIWYG no matter what software you import it into for toolpathing. If you are exporting text, then you are dependent on the receiving end software to convert the text to paths and that can invite problems. That’s just my opinon, YMMV.
All toolpaths are closed. Are you rebuilding polylines?
Exporting curves works, no arguments. But it is a workaround.
I’m want to toolpath text to try to avoid intermediate steps to use polylines (explode or textobject) or change the font at toolpathing. Creating and maintaining the nests with these intermediate steps is a pain.
That’s how the toolpathing software interprets ttf fonts. Yes, it is closing the font unnecessarily.
I am also putting this question to the toolpathing developer. It’s proprietary software from the machine maker, hence why I’m not bothering to name it here. This is a 9x2.2m alloy CNC, lots of parts are being cut, lots of files created, lots of text scribing.
SHX fonts work. I might even run the files through a batch process to just change the file extension in the dxf, but again, this is another intermediate step that I think can be easily avoided.
Cheers to everyone for the discussion. I have been doing exactly as you are all describing, but I think there’s a better way, hence the question.
