Since the step from 1.4 to 1.5 my old font folder is no more accepted by
MakeOTF. It stops compiling the font by the status "Running txlib...".
Him - I downloaded the examples and all works fine. So I`d copied my
fonts paths into the "Example Font Sources" directory and MakeOTF runs
like MakeOTF 1.4 before. But how can I change the path - so MakeOTF will
operate from each path my font files stored?
How can I apply my vendor ID to the font - of course I can extract the
table form the font, can use an hex editor and place it back. But I like
to do it with MakeOTF. I have checked the adobe samples and the vendor
id is ADBE in the final font. But I haven't find any code in the feature
files changing this value. If I compile my own fonts the result is UKWN
- unknown. The values from the source pfa and fontinfo file will be
ignored by MakeOTF.
Antoine Picard wrote:
> Question 1 is quite a puzzle. I suspect that I would need to some of
> the paths involved to even guess at what the problem might be.
> Question 2 is easy. You can use the line:
> Vendor "VDOR";
> is the OS/2 table definition in the feature file where "VDOR" is your
> desired vendor id and that should do it.
how exactly? I got an fatal error by MakeOTF saying: syntax error at
"VDOR" missing "}"
I need more info to figure this out. What are the paths, and in what context are they used (e.g are you using the UI for MakeOTF, or the command-line version, and where exactly do you specify the paths?). It would also be helpful if you could send me a project file that fails. MakeOTF makes a default project file in the same location as the the source font file, with the name 'current.fpr', when run in command-liner mode.