FutureLanguageSelectorImprovements
Launchpad Entry: foo
Created:
Contributors:
Packages affected: language-selector
Summary
Add new functionality to language-selector. This is not bound to any specific release, but merely a collection of what needs to be done in future releases.
Release Note
TBD
Rationale
Users have requested additional features, like detailed locale settings and user based language settings instead of only providing the system wide settings.
Use Cases
- Abdul and Ping-An share a computer and prefer to have different language settings for their desktops. GDM provides the possibility to choose the language per user profile, but since this is hidden in the Options menu, Abdul and Ping-An don't know about this functionality. Instead they found the system setting in language-selector. However, since this sets the system wide language, they are confused and would like to have the possibility to set their preferred language for their session only.
- Bob lives in Finland, but prefers his desktop to be in English. Since the English locales don't use the metric system, he would like to have more fine grained control over his environment variables and set the relevant ones to use fi_FI instead.
- A Brazilian user found that not all applications are fully translated into Brazilian Portuguese. Instead a fallback to general Portuguese is used. Since Brazilian Portuguese differs a lot from Portuguese spoken in Portugal, he would prefer US English as a fallback instead.
Assumptions
Design
You can have subsections that better describe specific parts of the issue.
Implementation
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:
UI Changes
Should cover changes required to the UI, or specific UI that is required to implement this
Code Changes
Code changes should include an overview of what needs to change, and in some cases even the specific details.
Migration
Include:
- data migration, if any
- redirects from old URLs to new ones, if any
- how users will be pointed to the new way of doing things, if necessary.
Test/Demo Plan
It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.
This need not be added or completed until the specification is nearing beta.
Unresolved issues
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
BoF agenda and discussion
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.