André G. Isaak

Is there anyone participating in this thread who is a Bulgarian speaker?

I recall reading somewhere that Bulgarian frequently used forms of д, и, п, and т which resemble latin g, u, n, and m in both cursive and upright forms, but I can't find the source for this and don't know if it is accurate (the use of 'g' contradicts Stefan Peev's example, but seems consistent with Michel Boyer's).

André

Thanks Stefan,

Your response was extremely useful.

André

Ray Larabie said:

Anyone know a trick to get automatically double encode in FontLab Studio 5? I have a custom name table with double encodes but I doesn't work when I try generate Unicode the values get blanked out. My allcaps.nam is formatted like this:

0x0041 A

0x0061 A

I use this trick all the time and have never had issues, though I would strongly recommend changing the second line above to

0x0061 !A

If your name table isn't generating the correct unicode values, make sure that the internal name you've given to your name table isn't conflicting with something else.

BTW: From a *user's* standpoint, I strongly prefer fonts that are built this way -- the reason for this is that while many all-caps fonts use the same characters for upper- and lowercase characters, many others include variants forms for some or all letters in the lowercase positions.

As an example, consider Gudrun Hesse's Ariadne font, in which upper- and lowercase characters are identical *except* for four or five characters -- if double encoding had been used it would be much easier to tell from the glyph palette which characters actually include alternate forms.

Although I understand the reasons why some avoid double-encoding, I find that fonts which include lots of duplication of identical glyphs (e.g A.sc a.sc A.alt.sc a.alt.sc etc) end up with extremely cluttered glyph palettes.