Re: Conlang Unicode Font (was Re: Kamakawi Unicode Font Question)

Tristan:
<<
Your explanation of the problem is wrong, as I hopefully explained
above. The few Latin ligatures, all those Korean codepoints, combined
accented Vietnamese letters, the Arabic characters, they're all there
for backwards compatibility or for political reasons. Somewhere,
there's a character set that included it because the font technology
wasn't able to automatically combine forms. Unicode just inherited a
lot of characters from that age it would rather just ignore.
 >>

Okay, then let me ask a practical question.

Herman's Olaetian font has, among other things, this ligature
for when the character "g" follows the character "n".  Presumably,
if there's a word typed "s-a-n-g-i", he'd want it to be appear as
"s-a-ng-i", where "ng" is the "ng" ligature.  That character doesn't
have a Unicode point (which, as you've pointed out, is as it
should be).  For someone creating a great big font like I am,
what should I do about this?  Should I include the "ng" ligature
in a place that doesn't have a Unicode point (or should I just
put it wherever, as long as nothing's being put there at the
moment...?)?  And at that point, is there something I have to
*do* to make it so that when you type "s-a-n-g-i", the word
processor spits out "s-a-ng-i"?  If there is, it might be something
that the font program I use (TypeTool 3) isn't capable of, in
which case maybe someone else should take over the Conlang
Unicode font project.  : \

-David
*******************************************************************
"A male love inevivi i'ala'i oku i ue pokulu'ume o heki a."
"No eternal reward will forgive us now for wasting the dawn."

-Jim Morrison

http://dedalvs.free.fr/

Reply