Thanks for the info. One problem, though, in the 2nd option I
mentioned, U+1FBD is not a combining character, so it's not
supposed to follow the "base" character. At least, that's my
understanding, and it's the ordering that results in the
biggest problem in the normalisation.
Peter
From: jehe@kabelfoon.nl AT internet on 08/27/99 03:46 PM
Received on: 08/27/99
To: Peter Constable/IntlAdmin/WCT, unicode@unicode.org AT
internet@Ccmail
cc:
Subject: Re: encoding polytonic Greek
I think this reply does not answer the original question. I do
agree that the clearest way of encoding classical Greek is to
avoid the precomposed stuff, and use only base letters with
combining accents. However, some existing tools may only allow
you to use the precomposed stuff because they cannot position
accents properly.
To answer the Peter's question, the right order is, even for
capital letters where the accents go in front of the letter,
first the base letter, then the combining accents. The software
should be smart enough to handle this special case in Greek.
Jeroen
-----Original Message-----
From: Rick McGowan <rmcgowan@apple.com>
To: Unicode List <unicode@unicode.org>
Date: Friday, August 27, 1999 20:34
Subject: Re: encoding polytonic Greek
>> Let suppose that we're encoding the text using the Greek
>> Extended block at U+1Fnn in addition to the Greek block at
>> U+03nn.
>
>Ah, that's the first mistake.
>
>> Q: Which approach should be considered preferable?
>
>The clearest way to encode polytonic Greek text is to avoid
using all the
>extended precomposed stuff. Use fully decomposed sequences.
>
>Some people might have a different opinion, of course.
>
> Rick
>
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:51 EDT