Difference between revisions of "Features/Fast Language Switch"
(Created page with "== Summary == The way to fast switch between languages. == Owner == * Name: User:alsroot * Email: send an email == Current status == * Targeted...") |
(→Owner) |
||
| Line 5: | Line 5: | ||
== Owner == | == Owner == | ||
| − | * Name: [[User:alsroot]] | + | * Name: [[User:alsroot|alsroot]] |
* Email: [[User:Alsroot#Contacts|send an email]] | * Email: [[User:Alsroot#Contacts|send an email]] | ||
Revision as of 14:43, 18 November 2011
Summary
The way to fast switch between languages.
Owner
- Name: alsroot
- Email: send an email
Current status
- Targeted release: 0.96
- Last updated: (Fri Nov 18 19:33:30 UTC 2011
- Percentage of completion: 0%
Detailed Description
The frame icon will contain two sections:
- list of languages to fast switch to (with restarting Sugar Shell),
- list of languages to change current keyboard layout for, i.e., having the same language for Sugar Shell, it will be possible to type in different languages.
All language options need to have associated shortcuts to have the fastest witch method.
Benefit to Sugar
This feature is important for multilingual communities when it is important to have the fast way to switch between languages, e.g., people are all time speaking in several languages and educational process is also basing on multilingual culture.
Scope
New frame component.
UI Design
- an icon for frame button
How To Test
TODO
User Experience
This entirely feature is optional.
Dependencies
Nothing except already existing dependencies.
Contingency Plan
Nothing special.
Documentation
Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.
Release Notes
The Sugar Release Notes inform end-users about what is new in the release. An Example is 0.84/Notes. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.