Mozilla.com/Localization: Difference between revisions
No edit summary |
No edit summary |
||
Line 3: | Line 3: | ||
Here is a stub of discussion areas to be filled in with input from the international community. | Here is a stub of discussion areas to be filled in with input from the international community. | ||
=Use Cases= | |||
These are the use cases that require internationalization of mozilla.com pages. They are listed in order of expected frequency. | |||
*''' | * '''(primary)''' International users coming to main mozilla.com URLs to learn about our products and obtain our software. | ||
*''' | * ''(secondary)'' Users looking for a build in a specific language which may or may not be their primary language (for testing, exploration, etc.) | ||
=The Team= | |||
Who'd like to help us? We'll need: | |||
* translators | |||
* sysadmins | |||
* testers | |||
* | =Potential Solutions= | ||
Add ideas for how we can best design the internationalization experience for our users. No idea is too wacky, simple or complex. For each, please list: | |||
* the idea in a nutshell | |||
* implementation requirements | |||
* any pros/cons you can think of | |||
*''' | == Use Accept-Language Headers == | ||
Use Apache's support for [http://www.auburn.edu/docs/apache/content-negotiation.html content negotiation] to serve the pages in the language requested by the browser's "Accept-Language" header. | |||
'''Requirements''' | |||
* user's browser sends the appropriate accept-language header | |||
* mozilla.com's apache can be configured to serve appropriate pages | |||
* fallback for languages we don't support / default language | |||
'''Pros''' | |||
* transparent to user and makes best use of available technology | |||
'''Cons''' | |||
* requires that user has browser that sends correct header | |||
=Timeline= | |||
* Dec 17 - collect potential solutions, build out team | |||
* Dec 20 - have plan for solution in place | |||
* Jan 20 - have implemented solution in place | |||
=Track implementation= | |||
Any bugs created to implement the plan will be listed here for tracking purposes. |
Revision as of 16:50, 12 December 2005
This page is a resource for discussing changes and updates to mozilla.com to improve access for non-English speaking users.
Here is a stub of discussion areas to be filled in with input from the international community.
Use Cases
These are the use cases that require internationalization of mozilla.com pages. They are listed in order of expected frequency.
- (primary) International users coming to main mozilla.com URLs to learn about our products and obtain our software.
- (secondary) Users looking for a build in a specific language which may or may not be their primary language (for testing, exploration, etc.)
The Team
Who'd like to help us? We'll need:
- translators
- sysadmins
- testers
Potential Solutions
Add ideas for how we can best design the internationalization experience for our users. No idea is too wacky, simple or complex. For each, please list:
- the idea in a nutshell
- implementation requirements
- any pros/cons you can think of
Use Accept-Language Headers
Use Apache's support for content negotiation to serve the pages in the language requested by the browser's "Accept-Language" header.
Requirements
- user's browser sends the appropriate accept-language header
- mozilla.com's apache can be configured to serve appropriate pages
- fallback for languages we don't support / default language
Pros
- transparent to user and makes best use of available technology
Cons
- requires that user has browser that sends correct header
Timeline
- Dec 17 - collect potential solutions, build out team
- Dec 20 - have plan for solution in place
- Jan 20 - have implemented solution in place
Track implementation
Any bugs created to implement the plan will be listed here for tracking purposes.