Ja, I know these system services and was always wondering whether »Make Nice Glyph Names« is the answer to my need.
But I get an error message. Is there anything broken in my system?
OK, very strange.
After successfully testing TextEdit, TextWrangler, Chrome and Safari now TextMate and Firefox work as well.
Only Glyphs itself generates this error.
Thank you – now I will manage it.
That is a second issue. (My first problem was more or less solved.):
When I first shipped the font family all the PUA glyphs got production names like »uniE440«.
For the recent version I have to keep the glyph order of this early exported OTF.
So I open the old OTF, copy the list of the glyph order custom parameter, paste it into TextMate, call Services > Make Nice Glyph Names and finally copy-paste it into the new glyph order custom parameter in the reworked master glyphsfile.
I have a custom GlyphData.xml for this project, that name the PUA glyphs (and some other) like »leftArrowHead«.
But these Glyphs were not corrected by the service …
OK, that works.
But being aware of the new possibility to have a project based GlyphData.xml next to the Glyphs file all this feels like a workaround until there is a »Make Nice Glyph Names«-one-click-script within Glyphs …
Why would you get the GlyphOrder from a different file? Why make an order parameter for the current file? And that copy it to the other file?
If you update the glyph info for the font first, you can build a changed name dict (get the name before and after the update) and then convert any text with this command: GSGlyphsInfo.convertNames_inString_(dict, string)