It's a syntax error in the FEA code file created by FontLab during compile. I think it is the line number, and line 1 would almost certainly be in the prefix header, perhaps the languagesystem statement.
But if you can check the temp .fea file created during the build, you should be able to tell for sure. As the build failed, I think it should still be there.
thank you Thomas. I spotted this file appearing for ca. 1sec in that Library>…>…Features folder and instantly it disappeared, I had no chance to get hold of it. What can be done about it?
FL5 holdouts unite! Check the names of the classes to make sure there are no conflicts. Check for syntax errors within those classes. I think FL5 compiles the content of the classes panel into the OT code before compiling so you won't see any of those errors in the OT panel.
If export starts with classes, then presumably that is also where the error lay? Def try font generation again!
(Sorry, this is all super old for me. I was using pre-release versions of FontLab VI for a couple of years before it even shipped, so this is like 5+ years ago for me.)
Hi Andreas, you may want to consider using OTM for a compiler check. The messages log (in the File menu) will inform you about the location of syntax errors, such as:
syntax error at "[class-name]" missing ";" [/TypeDrawers/02-02-2022/A_66_03T_1000.fea 26]
If there are mismatches in the classes or features definitions, OTM will compile anyway by subsetting them:
HOT [NOTE] Glyph "Andreas" not in font. [/TypeDrawers/02-02-2022/A_66_03T_1000.fea 25]
However, as shown below, the aforementioned log will inform you about the what and why of the subsetting. Of course, one can export subsetted features files for use in another font-tools based workflow.
Comments
I think it is the line number, and line 1 would almost certainly be in the prefix header, perhaps the languagesystem statement.
But if you can check the temp .fea file created during the build, you should be able to tell for sure. As the build failed, I think it should still be there.
Yeah!!! You can count on me Ray.
(Sorry, this is all super old for me. I was using pre-release versions of FontLab VI for a couple of years before it even shipped, so this is like 5+ years ago for me.)
syntax error at "[class-name]" missing ";" [/TypeDrawers/02-02-2022/A_66_03T_1000.fea 26]
If there are mismatches in the classes or features definitions, OTM will compile anyway by subsetting them:
HOT [NOTE] Glyph "Andreas" not in font. [/TypeDrawers/02-02-2022/A_66_03T_1000.fea 25]
However, as shown below, the aforementioned log will inform you about the what and why of the subsetting. Of course, one can export subsetted features files for use in another font-tools based workflow.