- From: Chris Lilley <chris@w3.org>
- Date: Wed, 01 Dec 1999 10:40:08 +0100
- To: "Martin J. Duerst" <duerst@w3.org>
- CC: Harald Tveit Alvestrand <Harald@Alvestrand.no>, www-international@w3.org
"Martin J. Duerst" wrote: > > Forwarded. > > At 13:35 1999/11/30 -0500, Harald Tveit Alvestrand wrote: > > At 17:25 28.11.99 -1000, Olin Lagon wrote: > > >How do people on this list work with Latin American Spanish, a popular > > >language to translate into yet one with no offical country-locale combination? > > (lists that I'm not a member of trimmed) > > > > If you feel the need for a code for "Latin American Spanish", I suggest > > that you use the RFC 1766 procedure for registering sp-LAT or similar tag. That would be es-lat, or es-latin. > > That will get you a tag you can use with several IETF and W3C protocols. You can use es-latin right now if you want. The definition is that if the first token is two letters, it is an ISO language code; if the second token is two letters, it is an ISO country code. Other lengths, and thirs and subsequent tokens, do not have a centralised registry. You can say en-GB-cheshire-southern-workingclass-1890s if you wish. I suggest not using three letter codes for the second token, since my understandingis thatthe ISO country codes are being/might be revised to use three-letter tokens; and thus a replacement for RFC1766 might mandate special meaning for three letter token in the second position. -- Chris
Received on Wednesday, 1 December 1999 04:40:20 UTC