On Fri, Oct 13, 2000 at 01:41:29PM +0200, Karlsson Kent - keka wrote:
>
>
> > -----Original Message-----
> > From: Markus Kuhn [mailto:[EMAIL PROTECTED]]
> ...
> > use. By making transliteration part of the locale, that is an integral
> > part of the wide character to multi-byte conversion process, any
> > application that has undergone what I called "hard conversion" in my FAQ
> > to be UTF-8 enabled (i.e., use wchar_t internally and let the library do
> > the UTF-8 I/O conversion) will automatically also start to behave
> > gracefully on old ASCII terminals, because UTF-8 and transliteration are
> > produced by the very same mechanism.
>
> Can we please call this "fallback" rather than "transliteration",
> since this is about having some kind of fallback for characters
> not representable in the target encoding.
>
> It is *NOT* about transliteration (or transcription), which
> 1) can be done within an encoding for the UCS (and normally
> would be done so), 2) is done to make the text (more)
> understandable/readable for the reader, and 3) is completely
> unrelated to what can and cannot be represented in a particular
> (non-UCS) encoding.
the 14652 transliteration spec is both meant for transliteration
(but not for transcription) and simpler fallback, eg based on
hardware limitations. It is certainly intended for transliteration
in eg UCS, for example as in transliteration of cyrillic names.
Kind regards
Keld
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
