Closed Bug 44063 Opened 25 years ago Closed 25 years ago

language pref- the region code is lower case while it should be upper case

Categories

(SeaMonkey :: Preferences, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: ftang, Assigned: ftang)

References

Details

According to RFC 1766 ( http://www.cis.ohio-state.edu/htbin/rfc/rfc1766.html ) and ISO 3166 ( http://www.ics.uci.edu/pub/ietf/http/related/iso3166.txt ) the region code of the language code should be in upper case. However, we currently use lower case. We should correct this so we meet the standard/RFC.
Status: NEW → ASSIGNED
Blocks: 44068
I supplied jbetak with the revised & expanded "regionNames.properties" file not so long ago. In that file, all iso-3066 names are in uppercase. The plan was for juraj to to check this file in but this has not happened yet. I can attach that file on this report if that is desired.
From RFC 1766: NOTE: The ISO 639/ISO 3166 convention is that language names are written in lower case, while country codes are written in upper case. This convention is recommended, but not enforced; the tags are case insensitive. ------------------------------------------------ It seems there are a two files which need fixing: http://lxr.mozilla.org/seamonkey/source/intl/locale/src/language.properties http://lxr.mozilla.org/seamonkey/source/xpfe/global/resources/locale/en-US/regio nNames.properties
*** Bug 44559 has been marked as a duplicate of this bug. ***
It seems that I am WRONG. the tag is "case insenstive" and are not "enforced". so... do we NEED to change it to upper case ? Should I invalid this bug ? momoi- please attache your file anyway
Frank, this is the very point jbetak and I discussed. Code internally, we don't distinguish between upper and lower cases for Lang & Region codes. The only thing that matters is that if we send out such information to the net, we do so following the lower and upper case conventions of Language and Regions codes. There is another bug which requests addition of 2 Norwegian locales. That would be the best place to attach the files I have in mind. In these files -- though it does not matter, I plan to follow uppercase and lowercase conventions -- just so that knowledgeable people don't raise this type of issue in the future.
mark this bug as invalid since the RFC 1766 said This convention is recommended, but not enforced; the tags are case insensitive
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
mass verification of Invalid bugs: to find all bugspam pertaining to this, set your search string to "MagaritaLuisaChascarilloAvoidsInvalidBugs". if you think this particular bug is *still* an open issue, please make sure of the following before reopening: a. where relevant, do check that it's actually still a problem with ***recent trunk builds*** on the all appropriate platform[s] b. provide clear, compelling reasons why this bug should be considered a valid one.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.