Closed Bug 413138 Opened 18 years ago Closed 15 years ago

[calendar] Provide instructions of activating a language pack

Categories

(Calendar :: Website, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: rimas, Assigned: Tobbi)

References

()

Details

„Donwload Sunbird“ page currently offers not just to download localized builds of Sb, but also language packs (these links don't work, but that's Bug 413120). The problem is that there's no instruction how to activate that installed language pack, so it's a kind of unclear ATM. Furthermore, first result for the Google search for "Sunbird switch language" points at http://wiki.mozilla.org/Sunbird:language-switch, which is (cough) outdated. My suggestion is to add a short instruction before or after the list of those language packs, explaining how to install and activate them. On Linux that would be going to "Edit -> Preferences" menu, choosing the tab "Advanced", clicking the "Config Editor" button, filtering for preference names with "locale" in them and altering the value of "general.useragent.locale". Perhaps a friendlier choice would be to suggest installing Locale Switcher along with the language pack, if the Switcher works with Sunbird. That would be similar to what is offered for Firefox at http://www.mozilla.com/en-US/firefox/all.html#lang_packs .
Component: www.mozilla.org → Website
Product: mozilla.org → Calendar
QA Contact: www-mozilla-org → website
Version: other → unspecified
I'm very aware of the fact that this bug is now 2 years old. However, I'll start working on it now, and add an item to the FAQ and link to that from the download pages.
Assignee: nobody → tobbi.bugs
Status: NEW → ASSIGNED
We'll postpone it until / if we get a calendar SUMO set up. Then we can create an article on it.
Sunbird won't be maintained anymore. There's also no documentation for this, anymore (We currently only cover Lightning articles).
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.