Hello Don
On 12-Jul-01, you wrote:
>
> 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.
But mainly the same as Latin 1 - 7bit will get ASCII, the other 128 chars
will be a mish-mash of accents and scientific symbols at predictable
places.
> Once Unicode is built into all OSes (and provided MS don't mess it up),
> these problems should go away.
Windows NT has had Unicode support from the very start. How can they
"mess it up", Don? You're talking rubbish talk again.
>> 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.
There's nothing bad about it at all: the font is as it should be, all it
does is specify that at certain codepoints there shall be certain
symbols: considering that these codepoints are blank in the Latin 1
charset, they made a very good design decision: better to have no
characters at all, than the wrong ones.
All it does on the Amiga is make ttf.library look at some higher-up
codepoints for those characters rather than accessing the first
255 verbatim.
> What happens in Linux?
Linux has quite comprehensive support IIRC. Most operating systems
have if they wish to support more than English; for example, KDE has
good support for Japanese, as has QNX Photon, I'm sure BeOS has the
same decent support for those more complex character sets (KDE will
be using some standard libraries + FreeType - the stuff ttf.libray and
the newer type1.library use. QNX and BeOS use Bitstream Font Fusion
which has support for lighter 'stroke fonts')
> person could use as a basis for a new set of Amiga libraries.
Isn't this what I was discussing on the ttflib mailing list? You
joined in the discussion. You obviously forgot to listen..
> be some code in AROS, too. Does AROS support Unicode?
Who knows? :)
Thanks
--
Matt <[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
