LanguageSelectorImprovements

Differences between revisions 9 and 10
Revision 9 as of 2006-02-22 11:34:13
Size: 3190
Editor: p54A652EB
Comment: Input methods
Revision 10 as of 2006-02-22 12:27:17
Size: 2957
Editor: p54A652EB
Comment: more flesh
Deletions are marked like this. Additions are marked like this.
Line 46: Line 46:
There are > 50 packages that deal with input methods in dapper (including universe) currently. In main we have "anthy" (japanese), "nabi" (korean), "scim" (multiple backends, but none of them in main). The input methods for the languages we want to support and "scim-gtk2-immodule" need to move to main.

We need a mapping in language-selector so that it understand what language needs what input method (and what package belongs to it). Then the package with the input method needs to be installed and activated.
The language-support-* packages depend on input methods and dictionaries.
Line 54: Line 51:
We could have better fonts for some languages (e.g. arabic). We need to evaluate what fonts are available and under what license we can use them.
Line 56: Line 55:
The language-support-* packages depend on the dictionaries.

Summary

Language selector should offer more suppot than installing langauge-packs and setting /etc/environment. It should take care of setting a a system-wide keyboard and the required input methods, fonts and dictionaries as well.

Rationale

Once the system is installed it's not easy to add a new language, there is too much hand-holding needed and configurations that need to be changed by hand.

Use cases

Bob switched to dvorak and wants to have this layout system-wide. The computer is used by a new user how speaks arabic and wants fonts, input methods, dictionaries etc setup.

Scope

Langauage selector needs to be modified.

Design

There are various different goals here:

  1. Keyboard selection
  2. Input methods
  3. Font selection
  4. Dictionaries

Keyboard selection

  • The default keyboard layout should be automatically suggested from the selected language.
  • relationship between language and layout
  • simple list of those relationships to choose default
  • list includes only what is installed, rather than the entire set of languages (and you click 'add...' to install more)
  • unsure if there's a standard place to store the selection of relationships

Example how others do it: ["http://www.muhammadanism.org/Unicode/text_services_input_languages_xp.gif"]

Input methods

The language-support-* packages depend on input methods and dictionaries.

Font selection

We could have better fonts for some languages (e.g. arabic). We need to evaluate what fonts are available and under what license we can use them.

Dictionaries

The language-support-* packages depend on the dictionaries.

Implementation

There are three things to do here:

  1. change gdm so that it reads a gconf (root) variable to setup it's keyboard
  2. have a sensible way to configure the keyboard in language-selector
  3. make sure that the user gets the updated keyboard if he hasn't configured his own

gdm

The gdm keyboard setting can be applied using:

setxkbmap - layout ... -model ... -option .. -print | xkbcomp - :0.0

Finding available keyboard

The gnome-control-center keyboard capplet has code to figure the list of available keyboards and already maps keyboard layout and languages.

users keyboard

It should just work, if no settings are done by the user, the layout shouldn't changed.

Code

Data preservation and migration

Outstanding issues

BoF agenda and discussion


CategorySpec

LanguageSelectorImprovements (last edited 2008-08-06 16:26:47 by localhost)