Typophile - Robofab Glyph to UFO - Comments

Are you using

andyclymer — Tue, 27 Nov 2007 12:52:14 -0800

Are you using “DumpOneGlyphToUFO.py”? Line 32 (which is the line traceback says the problem is in) is trying to print the glyph name and the path that the GLIF is being saved to, do either of those use non-ascii glyphs in their names? Check the folder name for any extended characters, FontLab doesn’t like non-ascii glyphs in its output panel.

Thanks. I did have some

JLM — Tue, 27 Nov 2007 10:02:26 -0800

Thanks. I did have some #’s in the name, and I fixed that but I’m still having the same problem.

I joined the Robofab group, so hopefully that will solve the problem.

Thanks!

Hi, It appears that Python

PvdL — Tue, 27 Nov 2007 09:49:17 -0800

Hi,

It appears that Python is trying to convert a string of text to ascii, and that some of the letters are outside the ascii range (0-127).
I would check the font info fields (font naming, copyright etc) of your font and check whether they contain non-ascii letters.

If you want to get in touch with the Robofab developers quickly I suggest to check the Robofab group at Google: http://groups.google.com/group/robofab

Robofab Glyph to UFO

JLM — Tue, 27 Nov 2007 09:29:27 -0800

Hey guys, I’m in the finishing stages of a font, and am having some trouble with Robofab UFO stuff.

I am able to export and import fonts to UFO format, using the macro panel in Fontlab.

But I want to be able to just export the glyphs that I have changed, instead of doing the time-consuming complete import/export over and over.

I get this weird message everytime. I have reinstalled Robofab and Python, and the problem persists.

Anyone know the workaround for this?

Many thanks!