Forum Replies Created
-
AuthorPosts
-
Aha, need to select all those glyphs first in the destination UFO. Thanks.
Or is it just a bug in RoboFont?
http://doc.robofont.com/documentation/workspace/font-info/postscript/
I assume a value of “.039625” should be possible to enter as BlueScale. But RoboFont doesn’t allow me to enter this value…
Yes, exactly what I meant to say.
Thanks.
Would be a useful improvement for RoboFont.
Aha, the drop down menu is very well hidden in the preferences because of the narrow size of the pref window.
So it’s an either-this-or-that option? Not possible to have one shortcut for “Next Glyph” and another for “Next Glyph in Set” I assume?
Indeed, this works. Pfff… thanks.
Okay. So why does RoboFont ‘freeze’ while opening a glyph with curves?
Plausible point of view.
(The spec isn’t the problem, but it’s sometimes problematic to operate in a world where many people are not following the spec (and end-users suffer). In a world where font foundries and application developers are making workarounds for each others workarounds, it’s meanwhile impossible to define who is the chicken and who’s the egg. Indeed, we’re way off topic… :-)
I’m very much in favor of ‘a standard’, which has sadly been lacking in the type industry the last 15 years. But as long as not all applications are following that standard, fonts just won’t fully work. I’ve spend a reasonable amount of time in the last decade modifying correct fonts to make them also usable in obstinate apps like MS Word. Making fonts that are non-conformant with the spec is generally a bad idea, but making fonts conform the spec which don’t work (everywhere) is also a bad idea.
Of course it’s totally legitimate to tell your clients to wait for un update of MS Word which is bug free and following the specs. But that might take a while. You just won’t always make friends this way.
To have fully functioning fonts (also in certain versions of MS Word and Quark for example), it’s essential that Mac ID 1 & 2 = ID 16 & 17, while Win ID 1 & 2 follow the style mapped family name & style.
For example:
Mac ID 1: My Family
Mac ID 2: Light ItalicWin ID 1: My Family Light
Win ID 2: ItalicThis is an FDK issue, because this behaviour changed from FDK v2.0 to FDK v2.5.
See “FDKReleaseNotes.txt” or: http://forum.fontlab.com/adobe-fdk-for-opentype-afdko/afdko-25-font-grouping-doesnt-work-in-quarkxpress-t7095.0.html;msg24042#msg24042Until FDK 2.0 Mac ID 1 & 2 were always identical to ID 16 & 17, but since FKD 2.5 (Jan 22 2009) Mac ID 1 & 2 are identical to Win 1 & 2 by default. Which is correct and according to the specs. But there are quite some applications nowadays still not following these specs, and I would like to make fonts functioning within these applications as well.*
This can be simply achieved by generating with FDK in Terminal. Using the old, outdated syntax (using c= instead of l= & using c=1 instead of m=1) makes Mac ID 1 & 2 identical to Win 16 & 17, like FDK v2.0 was doing. But Robofont doesn’t have the option to use this old syntax.
I believe this is an essential preference within a font editor.
Can this be added to Robofont?
*
(I don’t know how Adobe treats this issue currently with their fonts, but I would find it hard to believe they are using the new syntax because their fonts wouldn’t function anymore in MS Word, Quark, etc)Does it make a difference between Mac & Win ID’s? (Mac ID 1 & 2 ≠ Win ID 1 & 2)
“The reason is not clear”
btw.
What does the checkbox than actually do? Or is it a future feature?Yes, different versions installed. So, is it possible to link to another version of FDK?
-
AuthorPosts