On 11-Jul-01, Matt Sealey wrote:
> Basically a Unicode font is done in a funny way for compatibility,
> characters 0-255 are as the ISO-8859-1 (Latin 1) codepage is
> specified: since this is the standard ASCII character set, any system
> which uses plain 7 or 8 bit characters can use these fonts like any
> font that would come with the system.
Well, only the 7-bit characters are specified in ASCII. Characters from
128 to 255 can be, and are, different on various systems. So you have
for these Apple encoding, Adobe Standard encoding, etc, which have been
causing big problems in DTP for the past 14 years.
Once Unicode is built into all OSes (and provided MS don't mess it up),
these problems should go away.
> What the Windows 1252 codepage does is make TTF library make
> certain characters available in some special slots when you ask
> for those character codes.
I wish they hadn't done that. It is yet another custom encoding table,
so we are back where we were. They have unsolved the problem.
>> I never actually intended for my orignial question to have more than
>> a yes/no answer, I didn't realise what a can of worms it was. :)
>
> I added support for β • and • today. I can't find the
> code for alpha in the normal character set.
No, it isn't there, and anyway mathematicians will want hundreds of
special symbols. But your additions to V will help.
What happens in Linux? I wonder if there is any code that some diligent
person could use as a basis for a new set of Amiga libraries. There must
be some code in AROS, too. Does AROS support Unicode?
Regards
--
Don Cox
[EMAIL PROTECTED]
_____________________________________________________________________
Voyager Mailing List - http://v3.vapor.com/
Voyager FAQ....: http://faq.vapor.com/voyager/
Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP
Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
