FontLab Forum
2012-02-08, 20:46:48 *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: Welcome to the FontLab forum, read how to use it! Update: Archives from old MSN forums are now available on our forum.
 
   Home   Help Search Calendar Downloads Tags Login Register  
Del.icio.us Digg FURL FaceBook Stumble Upon Reddit SlashDot

Pages: [1]
  Print  
Author Topic: invalid token (text was @)  (Read 2499 times)
Ray Larabie
Hero Member
*****

Karma: +1/-0
Posts: 124



WWW Email
« on: 2009-10-18, 01:08:39 »

In FontLab studio, Ive been working with a client's fonts and have been getting some strange errors. There's nothing strange about the fonts them selves. They have a few kern classes and a couple of simple features which have been checked for errors. The features work in other fonts. and even if I reduce features to a simple "liga" feautre with no kern table the problem persists. The fonts in questiosn were imported from OTF.

When I generate an OTF compile I get an error: invalid token (text was @)

I search the code for extra @ signs and found none.

If I remove all features except for one, the error persists. If I rebuild the kern table, the error persists. If I remove all classes, the error persists. I checked the main window in the OT features window - it is completely empty - no extra class declarations or anything else. If I rename classes, something interesting happens:

The error code is now invalid token (text was @fontname-Regular")

Fontname is, of course, the name of the font I'm working on. How would the font name affect the OT compilation? I've restarted FontLab and the results are the same.
Logged
David Bergsland
Hero Member
*****

Karma: +0/-0
United States United States

Posts: 34


Author: "Practical Font Design: Fontographer"


WWW Email
« Reply #1 on: 2010-01-02, 09:35:25 »

Im having the exact same problem -- I just upgraded for 4.6.

How do I fix this?
Logged
Ray Larabie
Hero Member
*****

Karma: +1/-0
Posts: 124



WWW Email
« Reply #2 on: 2010-01-30, 22:43:01 »

The problem is probably a duplicate class name. FontLab's class auto-numbering should not be relied on as it can very easily create duplicate class names*. FontLab doesn't check for duplicate class names . . . so you end up with these strange invalid token errors.

* To recreate this bug: Add kerning classes. Delete a kerning class other than the last one. Add another kerning class. The class name will not be unique.
Logged
Tags:
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!