+1
Namely, as long as we have only one representative country variant for a
given language, we should just put it at the top without a variant listing
so that the normal ResourceBundle algorithm finds it. I'll try to fix this
for 3.0.
Forcing specificity skirts any primacy argumants if we have more than one;
I'm not sure if we should do anything in such cases.
--a.
----- Original Message -----
From: "Sean Gilligan" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, September 08, 2006 2:30 PM
Subject: Locale hierarchy issue
(I think we talked about this back in January/February, but I don't see a
bug report for it. I have a 1-week old checkout of 3.0 and the problem
still exists.)
If I select "Spanish" or "Spanish (Mexico)" in my User Preferences page, I
still get pages in English. If I set "Spanish (Spain)", I get Spanish.
The same problem exists for Japanese and other languages.
The fix is to rename some files, we currently have:
ApplicationResources_de.properties
ApplicationResources_es_ES.properties
ApplicationResources_is.properties
ApplicationResources_ja_JP.properties
ApplicationResources_nl.properties
ApplicationResources_ru.properties
ApplicationResources_vi.properties
ApplicationResources_zh_CN.properties
ApplicationResources_zh_TW.properties
it should be:
ApplicationResources_de.properties
ApplicationResources_es.properties (was es_ES)
ApplicationResources_is.properties
ApplicationResources_ja.properties (was ja_JP)
ApplicationResources_nl.properties
ApplicationResources_ru.properties
ApplicationResources_vi.properties
ApplicationResources_zh.properties (was zh_CN)
ApplicationResources_zh_TW.properties
(I'm assuming that zh_CN should be the default for zh, but I could be
wrong on this one)
It seems silly to submit a patch as this is just a file rename. I didn't
see a bug entry for this, I'll create one if asked.
This issue could be the cause of this (unclear) bug report:
http://opensource.atlassian.com/projects/roller/browse/ROL-1059
It would be really nice to get this fix in 3.0.
Regards,
Sean
