Thanks John,
I was aware of those characters ... just not sure whether to treat them as
variant glyphs or separate characters.
and yes the private use area could be used for for the additional two
characters (with diacritics) .. i'd started playing around with that idea
... not ideal, but workable ... dependent on the software and ime's being
used ...
i can throw something together for my own use ... but the actual people who
will be typing the material have medium to minimal levels of experience with
computers ... whatever input method I end up using will have to be fairly
transparent ... and simple to switch to and from ...
since i'm not a typographer .. any font solution I'm likely to come up with
will be crude at the best ...
Cha`o
Andrew Cunningham
Information Systems Librarian
Maribyrnong Library Services
----- Original Message -----
From: John Hudson <tiro@tiro.com>
To: Unicode List <unicode@unicode.org>
Sent: Sunday, 26 September 1999 4:10
Subject: African letters (Was: A basic question on encoding Latin
> At 08:32 AM 25-09-99 -0700, Andrew Cunningham wrote:
>
> >U+0254 LATIN SMALL LETTER OPEN 0
>
> >There is an uppercase version of this character ... U+0186 .. but from
what
> >I understand the Dinka character is subtly different
>
> I would consider this to be a glyph variant. That is, you can legitimately
> encode a Dinka form of the uppercase open O as U+0254.
>
>
> >U+014B LATIN SMALL LETTER ENG
>
> The uppercase encoding is
>
> U+014A LATIN CAPITAL LETTER ENG
>
> Note that there is, again, a glyph variant question. The form of uppercase
> Eng printed in the Unicode standard is the form preferred for the Saami
> languages which use this character; the form used for African languages is
> different but the encoding is the same.
>
>
> >U+0263 LATIN SMALL LETTER GAMMA
>
> The uppercase encoding is
>
> U+0194 LATIN CAPITAL LETTER GAMMA
>
>
> >the six "breathy vowels" are represented by the vowel with dieresis
> >
> >The vowels in question are : a, e, I, o, U+0254, U+025B
> >
> >The vowel 'u' does not have a breathy form.
> >
> >All of which probably means that we'll have to resort to the undesirable
> >solution of creating a custom character set and font ...
>
> ...unless you are working with a text processing system which has a way of
> accessing unencoded glyphs -- e.g. glyph substitution routines or
> on-the-fly diacritic composition. If you are working with Unicode savvy
> apps, you can also encode the breathy vowels in the Private Use Area.
>
> John Hudson
>
> Tiro Typeworks
> Vancouver, BC
> www.tiro.com
> tiro@tiro.com
>
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:53 EDT