Skip to main content



      Home
Home » Eclipse Projects » Babel » Obsolete [iw] or invalid [tl] locale codes; using three-letter language codes
Obsolete [iw] or invalid [tl] locale codes; using three-letter language codes [message #16685] Wed, 30 July 2008 02:00 Go to next message
Eclipse UserFriend
One of my colleagues noticed that the Hebrew entry shown in
http://babel.eclipse.org/babel/translate.php was using the obsolete code
"iw" instead of "he", and I saw that Klingon is using "tl" which belongs
to Tagalog.

http://www.iana.org/assignments/language-subtag-registry

Are there any plans to change obsolete codes in Babel, or would this
break Java ResourceBundle lookups? (Perhaps a GUI/database change only,
but this might be more effort than it is worth.)

The Klingon problem is probably more interesting. java.util.Locale is
supposed to be constructed using two-letter ISO-639 codes, but Klingon,
like many other languages, doesn't possess a two-letter code, only a
three-letter code.

I've seen suggestions that you can nonetheless get away with
three-letter codes, at least for languages that don't have two-letter
codes.

So as a rule, Babel should probably use three-letter codes for languages
don't have two-letter codes. If three-letter codes stop working, at
least they'll be easy to identify, and thus straightforward to change.


As for Klingon, I think it should be changed to "tlh" in Babel. We
shouldn't have any angry Klingons to deal with, as they haven't bothered
to provide a single translation...


Sean.
Re: Obsolete [iw] or invalid [tl] locale codes; using three-letter language codes [message #18102 is a reply to message #16685] Thu, 14 August 2008 01:02 Go to previous message
Eclipse UserFriend
I did the investigation about "iw" and "he" locale support before. I can
answer the question. I found that Java Locale class constructor maps "he"
to "iw" for backward compatibility. And, as Sun Developer Network Bug ID
4778440 reported, resource bundle with "he" suffix does not load in 1.3.1
and 1.4.2. For compatibility to Java 1.4.2 reasons, we should keep using
"iw" until Sun fixes the compatibility issue.
Re: Obsolete [iw] or invalid [tl] locale codes; using three-letter language codes [message #572767 is a reply to message #16685] Thu, 14 August 2008 01:02 Go to previous message
Eclipse UserFriend
I did the investigation about "iw" and "he" locale support before. I can
answer the question. I found that Java Locale class constructor maps "he"
to "iw" for backward compatibility. And, as Sun Developer Network Bug ID
4778440 reported, resource bundle with "he" suffix does not load in 1.3.1
and 1.4.2. For compatibility to Java 1.4.2 reasons, we should keep using
"iw" until Sun fixes the compatibility issue.
Previous Topic:Eclipse 3.4, Update Babel Simplified Chindese to v20080727043401, start error!
Next Topic:Eclipse 3.4, Update Babel Simplified Chindese to v20080727043401, start error!
Goto Forum:
  


Current Time: Sun Jul 13 09:20:57 EDT 2025

Powered by FUDForum. Page generated in 0.03726 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top