MakeOTF Error: "invalid token (text was "Â")" in Feature file at line: 34


#1

This message appears when I try to export my font. What should I do to solve?
The exported files that are after it are completely empty. What is line 34? how do i find it? Grateful for answers.38


#2

Please read this:
https://glyphsapp.com/tutorials/troubleshooting-a-font-that-does-not-export

I assume there is a non-ASCII character in your feature code.


#3

I am having the same issue with a simple all-cap font. What does this mean?

Has this been solved?


#4

There is an invalid token in your feature code in File > Font Info > Features. Most likely an illegal glyph name or a non-ASCII character in your handwritten code, or in your font names.

Steps to trace the source of the problem are described in the tutorial linked above.


#5

So I am a complete noob with this. I do not see features in font info.

And here is my fatal line. With a Question Mark in line 34

Thanks for your help.


#6

Are you using Glyphs or Glyphs Mini?


#7

Ahh, I’m using mini


#8

Do you have a funny glyph name somewhere? Only ASCII letters and no spaces are allowed in glyph names.

Same is true for the font family name.


#9

Yeah, I only have Capitals and a spacing set. All are titled with their corresponding Capital Letter with no spaces. The title of the actual font is UMIBE Display with no spaces or ASCII letters. I am Stumped and this is my first attempt.


#10

Can you send me the .glyphs file please to support (at) (this website without www). I will have a look.


#11

Hey Mekkablue thanks for the feedback. I started a new file and basically copied and pasted each character into it and had to redo my kerning, but it was able to export on the new file. So I don’t know what it was, but I got it.

Thanks again.


#12

Can you send me the old file anyway? Maybe we can prevent the error with a simple fix in Glyphs Mini.


#13

For sure, I just sent it your way. Thanks again for the support.


#14

For the record: the Manufacturer URL had an illegal character in it.


#15

Well I’ll be. I feel dumb, for some reason it had the copyright info in that field. Thanks again for looking into this for me.


#16

Don’t sweat it. Happens to the best of us. The software should check and validate the entries.