zompist bboard

Lately I've been having some trouble with the Almean fonts. I used to have a computer with Mac OS 9 on it, and I had all of the Almean fonts installed and working fine. Then I got a new computer with 10.3 and went to zompist.com to get the fonts. The Axuna?in, Barakhinei, Eleisa, and SILIPA fonts work fine, but for some reason, the Verd?rian and Maraille fonts show up as if all of the character spaces are blank. Does anybody know what might be going on?

Valinta wrote:Lately I've been having some trouble with the Almean fonts. I used to have a computer with Mac OS 9 on it, and I had all of the Almean fonts installed and working fine. Then I got a new computer with 10.3 and went to zompist.com to get the fonts. The Axuna?in, Barakhinei, Eleisa, and SILIPA fonts work fine, but for some reason, the Verd?rian and Maraille fonts show up as if all of the character spaces are blank. Does anybody know what might be going on?

I believe the Verdurian font has Windows symbol encoding. Since Mac OS X makes full use of Unicode, and symbol encoding has it's own range in Unicode, you won't be able to use it by entering Latin characters. I've had the same problem. The following solutions are possible:

1. Reëncode the font, moving the Verdurian letters to the Latin positions where you would expect them.
2. Try an older word processor that doesn't support Unicode, like Word 10 (Office X) or Simple Text (it's included in the developer tools).
3. Get or make a keyboard layout for the symbol encoding.

The second is easier but will prevent you from using Unicode along with it. The third will allow this, but you'll probably have encoding issues of you try to share your documents. Also, good luck finding one.

Try grabbing Maraille.bin instead of maraille.ttf; the former is an actual Mac font suitcase.

(The encoding is actually the Mac one— it's really easy to use on a Mac, because e.g. you get circumflex-s by hitting Option-s, and so on.)

WurdBendur, you do realise it's possible he's worked out a way round the problem or even completely forgotten about it by now? This topic is two years old.

I actually ended up just giving up on Verdurian script in Mac OS X. The reason why I asked the question originally is because Mac OS X is supposed to read Windows TrueType fonts without problems, and it does, except for the Almean fonts. I just remembered that I have a Mac OS 9 utility that converts Windows TrueType fonts to Mac OS ones (it sounds like an automated way of doing what WurdBendur describes), so I'll try it and see if that resolves the issue.

UPDATE: That didn't work.

Valinta wrote:UPDATE: That didn't work.

The converter probably preserves the encoding, which was what caused the problem in the first place. Mark might be willing to reëncode it for you, or I could (well, I've already done it myself, but I guess I should ask first )

Yea, I think the problem is that Mac OS X expects everything to be Unicode. Maraille.bin didn't work either, so I guess re-encoding would be the only option. I have no idea how to do that, so if anyone wants to do it for me, point me to some directions, or has already done it themselves, that would be great.