Re: Java I18N

Hi Dave,

Take a look at the _real_ definition of the language tags and xml:lang, 
which is RFC 4647. For a good intro, see:

   http://www.w3.org/International/articles/language-tags/Overview.en.php

RFC 4647 incorporates more than just the language and country codes into 
tags. One of the types of subtags is the "script" subtag. In your 
particular case, the script subtag "Brai" represents Braille.

You might very well tags English braille texts as "en-Brai". US variants 
would be "en-Brai-US". British variants would be "en-Brai-GB". The Moon 
variation can be dealt with in two ways:

1. Private use code: "en-Brai-x-moon"

2. Registration with IANA (see RFC 4647) would allow it as a variant 
subtag, making either of these valid:

   en-Brai-moonw  // variants starting with a letter must be at least 5 
in length
   en-Brai-GB-moonw

Thanks,

Addison

-- 
Addison Phillips
Globalization Architect -- Yahoo! Inc.
Editor, RFC 4647

Internationalization is an architecture.
It is not a feature.


Dave Pawson wrote:
> 
> I'm working on a small project (I18N aware braille) where I'd thought
> to use xml:lang on the root  element to define a language+country
> specific variant of the content.
> 
> 
> Easy for most usage:
> http://java.sun.com/developer/technicalArticles/Intl/IntlIntro/ seems
> to point me
> in the right direction, and is based on iso639 and iso3166, having 
> 'variant'
> as a possible further extension (not sure how that might apply to 
> xml:lang).
> 
> My problem arises with UEBC, http://www.iceb.org/ubc.html
> which defines a braille format applicable to most of the English 
> speaking world.
> Is this a reasonable interpretation for xml:lang='en' ?
> 
> Then I have a tactile variant on Braille, Moon. 
> http://www.moonliteracy.org.uk/
> This is en-GB specific, but how might xml:lang encompass this?
> Any suggestions appreciated.
> 
> 
> regards
>

Received on Tuesday, 31 October 2006 20:08:01 UTC