Home › Forums › Build

Certain named glyphs appear as unicode in FL now.

Nick Cooke's picture
Posted by Nick Cooke in
6 Sep 2012 — 8:07am

I am building a font in FontLab. When using codepages certain characters are not named as they used to be, ie. Kcommaaccent is now uni0136, and all other commaaccent glyphs are not 'named' in the font or glyph window either. Why has this changed, have I accidentally changed preferences somehow?

Any answers welcome. Thanks.

daverowland
6 Sep 2012 — 9:30am
daverowland's picture

Mine changed too, so I doubt it's your preferences. It's either an upgrade in Fontlab, or it might have happened (for me at least) when I installed Fontographer demo to get different different encoding options for the font window. It's a little annoying because double clicking on the cell no longer automatically puts the components in there.

Theunis de Jong
6 Sep 2012 — 10:35am
Theunis de Jong's picture

... it might have happened (for me at least) when I installed Fontographer demo to get different different encoding options for the font window ..

Same for you, Nick?

Perhaps a shared resource file got changed -- a mapping from Unicode numbers to common glyph names.

Michel Boyer
6 Sep 2012 — 10:56am
Michel Boyer's picture

Could it be related to this (old) post http://typophile.com/node/82230#comment-464839 (may 2011)?

Michel Boyer
6 Sep 2012 — 11:25am
Michel Boyer's picture

... by the way the unicode character U+0136 is named uni0136 in the new Adobe font Source Sans Pro ... I checked all the ttf and otf files :).

Nick Cooke
6 Sep 2012 — 12:21pm
Nick Cooke's picture

It's a little annoying because double clicking on the cell no longer automatically puts the components in there.

Same for me too.

No, I don't have Fontographer, I abandoned it years ago.

agisaak
7 Sep 2012 — 7:50am
agisaak's picture

MacOS has problems with these glyph names, hence the change.

André

Jens Kutilek
7 Sep 2012 — 8:25am
Jens Kutilek's picture

«Has problems with these glyph names» or «purportedly had problems with these glyph names about 7 years ago»? I've never been able to successfully trigger that bug, in Mac OS X 10.4 or any other version.

What I know though, is that Mac Office 2004 and 2008 couldn't handle when the *commaaccent glyphs had uni-names on Mac OS X 10.5.

hrant
7 Sep 2012 — 8:59am
hrant's picture

Love the guillemet usage, Jens! :-)

hhp

Nick Cooke
7 Sep 2012 — 10:39am
Nick Cooke's picture

But I can't remember having updated FL lately and all commaaccent glyphs used to have names. Why the change?

Edit: And how do I restore it?

gargoyle
7 Sep 2012 — 1:28pm
gargoyle's picture

Why the change?

As mentioned, apparently an issue with Mac OS X. Adam goes into more detail here:
http://www.typophile.com/node/36473#comment-223275

Edit: And how do I restore it?

To get the automatic-component function working with the new names, you could add some definitions to the alias.dat file (which apparently was not updated to reflect the changes to the encoding tables). Add lines for commaaccent characters such as:

uni0122 G+commaccent
uni0136 K+commaaccent
uni013B L+commaaccent

The file is in FL's global Data folder— try /Library/Application Support/FontLab/Data on Mac, or \My Documents\FontLab\Shared\Data on Windows, or just run a search.

Syndicate content Syndicate content