Typophile

Question with regard to FontLab panel: Non-English or special font names

Arno Enslin

Platform 1Macintosh Encoding 0Roman Language 0English

How to I have to type in/encode the following characters, or is it unpossible to use them there?:
EnDash, CopyrightSign, Trademark, LeftSingleQuotationMark and RightSingleQuotationMark

For the Microsoft platform it is easy:
EnDash\2013, CopyrightSign\00A9, Trademark\2122, LeftSingleQuotationMark\2018 and RightSingleQuotationMark\2019

http://www.germantype.com/cms/front_content.php?idcat=193

\D0 results in an Eth, but not in an endash.

This is from the FontLab manual:
To add a new name record, click on the button on a toolbar, select
name record options using the controls below the list and type in the name record content. To enter non-ANSI characters use “\[unicode index]” or “\[code]” notation where [unicode index] is the Unicode index of the character if the name record is for the Unicode (0 or 1) platform and [code] is the character code in the Mac Roman codepage if the name record is for the Macintosh platform. For example you may enter “\0411” for the Cyrillic “beh”.

[\D0, \A9, \AA, \D4, \D5] results in [–, ©, ™, ‘, ’], when I open the generated Font in FontLab. Before it is generated
[\D0, \A9, \AA, \D4, \D5] is interpreted in this way: Ð, ©, ª, Ô, Õ

(When I decompile the name table with ttx, I get this: & #208;, & #169;, & #170;, & #212;, & #213;
)

But if I want to preserve the characters, when I regenerate the font, I have to insert [\D0, \A9, \AA, \D4, \D5] again. Otherwise I get this: , ©, ", ,  (& #19;, & #169;, ", & #24;, & #25;). Either FontLab does not generate the code correctly or it does not interpret the code correctly, when it imports the name table.

Captured from web.archive.org on 2 Feb 2010. view this capture