##### level-1 quote by Michael Everson (on) 03.03.08 (at) 09:54 +0000

>From our newest member:
>
> >I'm an engineer, have designed a few fonts over the past 12 years in
>>FOG 4.1.5, need help with updating an old custom Mac font for TT
> >Windows, has glyphs in upper 128 space that are lost.
>

I was going to lurk for a bit here, but it seems very quiet, so I'll
pop up and awaken the crew...

First, I use FOG 4.1.5 on an older Mac because the font stuff I do is
just volunteer work, no income, labour of love, yada-yada. I'd *love*
to get a newer FOG or whatever, but can't justify the cost.

The font was created using Macintosh encoding and has a bunch of
zero-width symbols and very large ascender and descender values
because many symbols reside above regular characters. (It is for
notation of central Javanese music, which uses numbers 1-7, some with
dots under or above for octave, plus much more.)

In 1990 I had no Windows box so I created a Windows encoded TT font.
But now I found out that quite a few glyphs vanished from that
version due to the original chap who made it having relied on Mac
keyboard shortcuts, when those characters are on the list of .notdef
on Windows. In particular, a string of elevated numbers 1-7 using
shift-opt-1 thru 7.

I'm trying to achieve three possibly mutually exclusive goals.

1. Make a Windows TT font with these symbols.

2. The Windows font should allow documents to be made and editable on
Mac, and visa-versa.

3. The original Mac font should not be changed, or else it will break
many files in many people's archives.

What is encouraging is that documentation done on the Mac, and
Acrobat Distilled with embedded fonts, can be opened on Windows with
100% perfection, nothing lost. Distiller knows what I want to know ;-)

Any suggestions, crew? TIA!

Raymond Weisling
from Yogyakarta, Java, Indonesia