Adam Twardoch (FontLab)
Product and marketing manager, Fontlab Ltd.
Administrator
Hero Member
Karma: +12/-4
 Germany
Posts: 304
FontLab Studio 5.0.4, Mac OS X 10.4.11
|
 |
« on: 2009-03-16, 08:03:49 » |
|
I have just posted updated guidelines for implementing the "locl" feature for the Romanian language. |
|
|
|
|
Logged
|
|
|
|
Dezcom
Beta: FontLab Studio Mac
Hero Member
Karma: +6/-0
 United States
Posts: 109
FLS 5.1.1 beta; Mac OSX 10.7.2
|
|
« Reply #1 on: 2009-03-17, 11:11:07 » |
|
So we should not use the commaaccent name at all and just use the opentype number?
|
|
|
|
|
Logged
|
|
|
|
Adam Twardoch (FontLab)
Product and marketing manager, Fontlab Ltd.
Administrator
Hero Member
Karma: +12/-4
Germany
Posts: 304
FontLab Studio 5.0.4, Mac OS X 10.4.11
|
|
« Reply #2 on: 2009-03-18, 19:23:15 » |
|
Not just the Unicode number. Instead of the glyph names such as "Scommaaccent", you should use glyph names such as "uni0218", i.e. uniXXXX where XXXX corresponds to the glyph's Unicode codepoint — for all the glyphs with a commaaccent, i.e. also the Baltic glyphs (K with commaaccent, G with commaaccent etc.) This has to do with bugs in Mac OS X which did not recognize the "commaaccent" names in Mac OS X 10.4 and earlier, even though those were the glyph names recommended by Adobe. Adobe has since adjusted their recommendations.
|
|
|
|
|
Logged
|
|
|
|
Dezcom
Beta: FontLab Studio Mac
Hero Member
Karma: +6/-0
United States
Posts: 109
FLS 5.1.1 beta; Mac OSX 10.7.2
|
|
« Reply #3 on: 2009-03-20, 21:55:55 » |
|
Thanks, Adam. This seems like a similar issue with some Greek glyphs that have a math position as well. Will the soon-to-come FontLab 6 use this nomenclature as standard before the OS developers fix it?
Chris
|
|
|
|
|
Logged
|
|
|
|
Adam Twardoch (FontLab)
Product and marketing manager, Fontlab Ltd.
Administrator
Hero Member
Karma: +12/-4
Germany
Posts: 304
FontLab Studio 5.0.4, Mac OS X 10.4.11
|
|
« Reply #4 on: 2009-03-21, 13:31:27 » |
|
Chris, we keep in sync with the Adobe Glyph List for New Fonts. Last year, we proposed some changes to AGLFN, Adobe incorporated them into the most recent version: http://www.adobe.com/devnet/opentype/archives/aglfn.txtwhich of course will be used by FLS6. Adam |
|
|
|
|
Logged
|
|
|
|
malinka
Full Member
Karma: +0/-0
 United Kingdom
Posts: 2
|
|
« Reply #5 on: 2009-05-11, 05:53:17 » |
|
Adam,
I don't quite understand the AGL, how does it relate to SID encoding for PostScript OpenType fonts? What I mean is this:
both OpenType and TrueType fonts have PostScript and Unicode encodings, if a letter has no Unicode number, say it is in Corporate pagew, it can have an entry in PostScript list and no entry in Unicode encoding - that makes sense.
Some letters in SID encoding, onesuperior, etc. (26 letters altogether) have perfectly normal Unicode numbers in page 00 and page 20 but have no entries in AGL, that would mean they should be called "uniXXXX" in PostScript encoding but in CFF they would be called by their proper name. Since one normally makes PostScript encoding identical to SID in OpenType fonts, I have to call "onesuperior", "onesuperior"
in both PostScript and SID, or call it "uni00B9" in both PostScript and SID. Or am I supposed to do something
else? I em lost!
Edward
|
|
|
|
|
Logged
|
|
|
|
Adam Twardoch (FontLab)
Product and marketing manager, Fontlab Ltd.
Administrator
Hero Member
Karma: +12/-4
Germany
Posts: 304
FontLab Studio 5.0.4, Mac OS X 10.4.11
|
|
« Reply #6 on: 2009-05-13, 19:36:16 » |
|
Edward,
what do you mean by "SID"?
A.
|
|
|
|
|
Logged
|
|
|
|
malinka
Full Member
Karma: +0/-0
United Kingdom
Posts: 2
|
|
« Reply #7 on: 2009-05-16, 07:01:22 » |
|
Standard Strings - SID as in Appendix A of The CFF Specification, Adobe, ver 1, Edward
|
|
|
|
|
Logged
|
|
|
|
|
ShashaCorleone
Guest
|
|
« Reply #8 on: 2009-08-24, 23:31:52 » |
|
Thanks! Adam. That really helped me since I'm using MAC...
|
|
|
|
|
Logged
|
|
|
|
Adam Twardoch (FontLab)
Product and marketing manager, Fontlab Ltd.
Administrator
Hero Member
Karma: +12/-4
Germany
Posts: 304
FontLab Studio 5.0.4, Mac OS X 10.4.11
|
|
« Reply #9 on: 2010-02-17, 03:22:48 » |
|
Edward,
1. Forget AGL.
2. Forget the CFF standard strings.
3. AGLFN is mandatory, of course combined with the algorithmic rule i.e. if a glyph name is not found in AGLFN, then a uniXXXX (for 4-digit Unicodes) and uXXXXX (for 5-digit Unicodes) should be used.
AGLFN has been constantly updated by Adobe and the names included there represent the most up-to-date recommendations. Some of the AGLFN names are found among the CFF standard strings, some not -- they should be used anyway. Names that are part of CFF standard strings but are not in AGLFN should not be used as glyph names.
A.
|
|
|
|
|
Logged
|
|
|
|
Dezcom
Beta: FontLab Studio Mac
Hero Member
Karma: +6/-0
United States
Posts: 109
FLS 5.1.1 beta; Mac OSX 10.7.2
|
|
« Reply #10 on: 2010-03-15, 13:32:56 » |
|
Using the unicode designation as the glyph name is a dyslexic's nightmare. There are some glyphs in the Romanian group above that are so similar to each-other that they are easy to switch by accident. I found this out testing a font I was working on and found I had mislabeled the Ibreve. I sure wish Apple would fix their system so we won't have to look cross-eyed at screen renderings of glyph names in the uni format :-)
|
|
|
|
|
Logged
|
|
|
|
|
