- From: Keld J|rn Simonsen <keld@dkuug.dk>
- Date: Fri, 16 Oct 1998 13:03:41 +0200 (CEST)
- To: duerst@w3.org
- Cc: carrasco@dragoman.org, Harald.Alvestrand@maxware.no, www-international@w3.org
> At 19:20 98/10/15 +0200, Keld J|rn Simonsen wrote: > > > If we use locales, and the locale naming scheme of ISO/IEC 15897 > > I think not many people are familliar with the ISO standards you > mention. Can you give us a bit of background or a reference (URI)? I hope I can give you a URL with the text something like next week. > > > then that can be done within that scheme. I believe RFC 1766 > > allows for locale names to be referenced. > > The way I understand it, RFC 1766 language codes work in parallel > with locale names in as far as they can contain two-letter language > codes followed by two-letter country codes. But these two codes are > separated by a "-". And RFC 1766 language codes don't include > any character encoding related parameters. > > Would you use the character encoding to indicate to which script > something is transliterated, i.e. use iso-8859-8 to say something > is transliterated to Greek? That is interesting, but rather limited. > Or is there another mechanism? The character set can be done, yes, but also which two languages that is in question can be specified. > > > ISO/IEC FCD 14652 has provisions for language to language simple > > tranliteration specifications. > > What do you mean by "simple"? Are these just tags, similar to > what Tomas is proposing, or is it a mechanism to actually specify > what should happen in the transliteration (i.e. a Cyrillic C > goes to a Latin S,...)? You can say this string goes to that string, regardless of coded character set. See FCD 14652 at http://www.dkuug.dk/jtc1/sc22/wg20 (projects page). Keld
Received on Friday, 16 October 1998 07:03:51 UTC