Path: utzoo!utgpu!watserv1!watmath!att!rutgers!sun-barr!olivea!apple!agate!shelby!portia.stanford.edu!jessica.stanford.edu!davef
From: davef@jessica.stanford.edu (David Finkelstein)
Newsgroups: comp.sys.next
Subject: Re: Diacriticals under 2.0
Message-ID: <1990Oct17.165804.29323@portia.Stanford.EDU>
Date: 17 Oct 90 16:58:04 GMT
References: <97042@srcsip.UUCP>
Sender: news@portia.Stanford.EDU (USENET News System)
Organization: Academic Information Resources
Lines: 21

In article <97042@srcsip.UUCP> pclark@SRC.Honeywell.COM (Peter Clark) writes:
>Someone asked me to check the way 2.0 handles diacritical marks (umlauts and
>such) in the generic text object (i.e. in Edit). They seem to work as
>expected- alt-a gives an 'a' with a little circle on top.

Diacriticals are supported under 2.0, but not in the "correct" way.
That is, NeXT has each character like o-umlaut, n-circumflex, etc.
mapped as a distinct character -- o with an umlaut on top, u with an
umlaut on top, etc.  They don't generate the character and then add
the umlaut to it.  But it still works the way you'd expect, and seems
to be consistant with other schemes.

I remember reading somewhere in NeXT's documentation that there were
some characters that couldn't be mapped properly because NeXT was
already using those ASCII values for special characters, but I can't
seem to find that information again.

David Finkelstein
Academic Information Resources
Stanford University
davef@jessica.stanford.edu