##### level-1 quote by johnroshell (on) 04.03.08 (at) 16:49 +0000

>Hi, Raymond. Welcome aboard!
>
>> 1. Make a Windows TT font with these symbols.
>
>Pretty much everything you see on the keyboard is fair game for
>windows and macs. Are
>all of those characters used up in your font? I'm not a Windows
>user, but I think the upper
>and lowercase option-letters (minus i, e and u, which indicate
>accents to be placed over
>the next letter entered) should be safe.

Actually the lower 95 accessible characters are all used but 1, but
in the code space above 128 only 38 are used. But the main problem is
choosing an encoding so that on the Windows TT font nothing is lost,
and so far I lose 5-10 glyphs. If I change the Mac encoding to Adobe
Standard it may work, but then all of the Mac character codes and
keyboard associations change, and we have hundreds of people using
this font in existing documents, since 2000.

>
>> 2. The Windows font should allow documents to be made and editable on
>> Mac, and visa-versa.
>
>Windows TTFs work in Mac OSX with no problem.

OK, but again, compatibility with old documents is an issue.

>
>> 3. The original Mac font should not be changed, or else it will break
>> many files in many people's archives.
>
>Well, try leaving the characters in the original location as well as
>the new location, and
>give it a try. I'd be happy to install it on the Mac and try it out
>if you need a tester.

You mean place the same glyph in two slots? But then it will not
allow a document to be carried across platforms.

This mail list seems very quiet. Is it always like this??

Ray