Closed
Bug 442754
Opened 16 years ago
Closed 16 years ago
Some strings not displayed localized for locale 'NO' due to Accept-Language issues
Categories
(support.mozilla.org :: Localization, task)
support.mozilla.org
Localization
Tracking
(Not tracked)
VERIFIED
FIXED
0.8
People
(Reporter: mail, Assigned: nkoth)
References
()
Details
(Keywords: push-needed, Whiteboard: sumo_only)
The 'NO' l10n version of SUMO has a few "untranslatable" strings, notably those on the SUMO login page. When accessing http://support.mozilla.com/tiki-login_scr.php in Firefox, the strings "Username:" and "Password:" are in english. When accessing it with Internet Explorer, they are displayed as translated. I have tracked this down to being an Accept-Language issue, i.e.: This will show correct output "Brukernavn:" (note: Using only 'no' as accept-lang, as Internet Explorer does): wget -q -O- --header="Accept-Language: no,en-us,en;q=0.5" http://support.mozilla.com/tiki-login_scr.php | grep login-user This will show incorrect output "Username:" (note: Using 'nb-no' as preferred locale): wget -q -O- --header="Accept-Language: nb-no,no,en-us,en;q=0.5" http://support.mozilla.com/tiki-login_scr.php | grep login-user Can SUMO be modified to not recognize 'nb-NO' Accept-Language, and instead fall back to NO? (nb-NO is supposed to be removed from SUMO, as a result of bug 426853)
Comment 1•16 years ago
|
||
Not sure but I think this is a Tiki thing, and not a server setup issue. Nelson or LP, could you take a look? Assigning this to the 0.7 milestone.
Target Milestone: --- → 0.7
Assignee | ||
Comment 2•16 years ago
|
||
I think this might be because lang/nb-NO is still in SVN and has to be completely removed. I'll test it.
Assignee | ||
Updated•16 years ago
|
Assignee: nobody → nelson
Assignee | ||
Comment 3•16 years ago
|
||
Is this ok now? I notice though, that Firefox 3 lists [nb] and [nn] as separate languages -- this makes it not possible to fall back those to [no] unless we code in some aliasing for that.
Target Milestone: 0.7 → 0.8
Reporter | ||
Comment 4•16 years ago
|
||
This works fine now. Thanks! Resolving to fixed; assuming that was the case. :-)
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Updated•16 years ago
|
Keywords: push-needed
Updated•15 years ago
|
Whiteboard: sumo_only
You need to log in
before you can comment on or make changes to this bug.
Description
•