Closed Bug 394999 Opened 17 years ago Closed 14 years ago

Localizing via em:localized doesn't work as expected

Categories

(Core :: Internationalization: Localization, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 416350

People

(Reporter: joh_walt, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a8pre) Gecko/2007083102 SeaMonkey/2.0a1pre
Build Identifier: 

I'm about to localize an extension and followed http://developer.mozilla.org/en/docs/Localizing_extension_descriptions to accomplish it using the em:locale property in the install.rdf.
It looks nice but I stumble over two issues.

1. Localization doesn't use global (those directly under install manifest) properties if there's a matching locale for an em:locale but without that particular property populated.
E.g. em:creator normally isn't locale dependent, so why include it in each em:localized? Gecko should use the global one if the current locale doesn't provide one.

2. If there's an em:locale of "de-DE" for example in an em:localized, an useragent with de-AT gets the default language instead of the nearer de-DE. Even creating an em:locale simply with "de" does work neither for useragents of "de-DE" nor "de-AT".

But the mechanism for choosing the right properties file *does* work the way that useragents of "de-AT" or "de-DE" find the german ones, regardless of chrome.manifest contains "locale extension de-DE" or "locale extension de".
Thus also the old mechanism using default preferences file works different and better than the new one using em:localized.

I think it should work like the present way using localized properties files.

Reproducible: Always
This happens for Firefox too: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5) Gecko/2008040514 Firefox/3.0b5

Very annoying and very unexpected.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.