Closed Bug 424864 Opened 16 years ago Closed 16 years ago

Languages section in nav_help.xhtml needs an update

Categories

(SeaMonkey :: Help Documentation, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
seamonkey2.0a2

People

(Reporter: stefanh, Assigned: stefanh)

References

Details

Attachments

(1 file, 1 obsolete file)

In bug 420730, we forgot the "Setting Language Preferences" (To set your prefered language) in nav_help.xhtml.
Note: the link at line 1164 needs to be updated.
OK, so I've changed this a bit based on the theory that having duplicate content is evil (it's confusing and (most important) it makes maintenance a nightmare). Not sure of the link to the language codes - is it worth having it?
Assignee: neil → stefanh
Status: NEW → ASSIGNED
Attachment #343253 - Flags: review?(iann_bugzilla)
Attached patch New versionSplinter Review
This is perhaps a little bit better. Note that the old text regarding adding languages in the "Other" field was wrong - you can just add language codes (not language names). We actually support both 3- and 2-letter codes, but it seems we just automatically add language names for some 2-letter codes that are defined in toolkit/locales/en-US/chrome/global/languageNames.properties. It also seems that we send anything one types in the field - I tried to add "aaa", and "xyz" in 1.1.12 and Live HTTP headers shows this:
"Accept-Language: sv,en;q=0.8,en-us;q=0.6,aaa;q=0.4,xyz;q=0.2". I was under the impression that only *.accept="true" in intl/locale/src/language.properties was accepted, but it doesn't seems so.
Attachment #343253 - Attachment is obsolete: true
Attachment #343268 - Flags: review?(iann_bugzilla)
Attachment #343253 - Flags: review?(iann_bugzilla)
Attachment #343268 - Flags: review?(iann_bugzilla) → review+
(In reply to comment #4)
> Created an attachment (id=343268) [details]
> New version
> 
> This is perhaps a little bit better. Note that the old text regarding adding
> languages in the "Other" field was wrong - you can just add language codes (not
> language names). We actually support both 3- and 2-letter codes, but it seems
> we just automatically add language names for some 2-letter codes that are
> defined in toolkit/locales/en-US/chrome/global/languageNames.properties. It
> also seems that we send anything one types in the field - I tried to add "aaa",
> and "xyz" in 1.1.12 and Live HTTP headers shows this:
> "Accept-Language: sv,en;q=0.8,en-us;q=0.6,aaa;q=0.4,xyz;q=0.2". I was under the
> impression that only *.accept="true" in intl/locale/src/language.properties was
> accepted, but it doesn't seems so.
There are certain rules, has to be RFC1766 compliant, see http://mxr.mozilla.org/comm-central/source/suite/common/pref/pref-languages-add.js#66
Pushed 678:2c24ff550eb6.
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.0a2
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: