Internationalization technology is the technology for representing and composing the languages spoken, taught or used in your countries. Localization is the process of taking software or content and adapting it for local use.
Localization involves fonts, script layout, input methods, speech synthesis, musical instrumentation, collating order, number & date formats, dictionaries, and spelling checkers, among other issues.
Linux is already more widely localized than Microsoft Windows since no cooperation from a vendor is required to do so: having said this, cooperation with the free software and content community is vital to reduce overall work required.
The size of the problem is huge. Ethnologue has extensive information on the languages of the world.
- See also Wikipedia's definition
This is an outline of (some of) the core topics and tools, and issues of localization.
Basic Localization Topics
Unicode is fully supported in “modern” applications and toolkits used in free software. Legacy character set support also present, but modern applications use Unicode.
Collation order (the sorting order when text is sorted by Linux) is generally well supported in the C library.
OLPC primarily concentrates on using the Pango library, which is able to layout most of the “hard” languages, including: Arabic, the Indic languages, Hebrew, Persian, Thai, etc. It has a modular puggable layout engine and supports vertical text, as well as supporting bi-directional layout. Overall, some issues remain – but overall Pango is in pretty good shape and can handle most scripts already.
- See also: Category:Languages (international)
To share content and preserve cultural heritage OLPC's goal must be and is for full coverage of all the world's languages. By using the Fontconfig system Linux has a better concept of language coverage of fonts than other systems. This system is used to configure the font system and determine what set of fonts are needed to cover a set of languages.
The formats of fonts supported on Linux include OpenType, TrueType and many others: see Freetype for details. Most of the current font formats supported by Freetype are obsolete, and by far the best results on the screen will be had from OpenType and TrueType format fonts. Type 1 fonts are useful primarily for printing; the renderer for Type1 fonts in Freetype we have today is not very good, and Type 1 does not support programmatic hinting for low resolution screens.
OLPC itself has a relatively high resolution screen; this helps us considerably, particularly in grayscale mode at 200DPI.
Free fonts are available for most scripts in the world, though some fonts are licensed incorrectly for completely free redistribution.
Need for Screen Fonts
Regardless of the XOs resolution, we also need our applications and content to be usable on other screens everywhere, so we need to work together on extending the coverage we have today on high quality screen fonts. The "DejaVu" font family (derived from Bitstream Vera) covers most Latin alphabets and some other languages. This family has in general good "hinting" for screen use.
SIL International also builds fonts for a number of additional languages of local interest.
Helping with these or other efforts to build fonts or to increase coverage of existing fonts is greatly appreciated. Pooling efforts on hinting glyphs, which is boring but important work, and/or donations and buyouts are also being investigated.
OLPC Keyboard layouts document OLPC's currently available keyboard layouts: further layouts are a modest amount of work, requiring people with local expertise to work with OLPC staff to generate new layouts.
An input method is software that allows typing of complex characters, for example for languages such as Chinese, Japanese, Korean. Some issues remain, for example: Arabic ligatures, by avoiding putting them on the keyboard we've avoided the need for an input method. However, such workarounds may not be feasible for your language.
Free software systems now are using SCIM - Smart Common Input Method Platform. SCIM is replacing older input method systems.
We need to know what languages are taught as “foreign” languages, as well as are native, to design keyboards that are most useful in each country. For example, the Nigerian keyboard is designed to allow easy entry of English, Hausa, and Yoruba, which are common languages in much of Nigeria. The "US/International" covers most of the western European languages.
Espeak is small enough for us to often bundle and covers quite a few languages: ~10 languages currently supported tuned by native speakers with 10 more languages underway.
Synthesis is essential or accessibility to content by people with vision problems, and will need to be integrated with the ATK library used, as well as literacy training, other uses as part of a GUI. Full localization therefore involves selection of a suitable synthesis system and integration into the ATK framework, along with localization of that system for the particular language involved.
Speech synthesis is usually not a good guide for pronunciation learning languages – but it may be better than a poor teacher who has never had the opportunity to learn from a native speaker of that language.
- See also Category:Accessibility
Music and Sound Samples
We want much more than dead white male western instruments for dead white male composers!
Clean samples of your musical instruments and music needed!
Samples need appropriate licensing terms.
- See also TamTam: Sounds
Dictionaries, Spelling Checkers, Thesaurus
Support exists for most major languages.
Spelling, Hyphenation, Thesaurus dictionaries may be needed for different parts of Linux, which may or may not apply to OLPC directly; for example you can check:
Of these, the first three are most immediately interesting to OLPC.
Stroke/character recognizer localization is of some interest with the pen/tablet: in the future (Gen 2) when we have a touch screen they will become essential. xstroke is one such individual character/stroke recognizer, sufficient for alphabets of up to about 100 characters.
There are some real shortcomings where help is needed. These include:
- Non-Gregorian calendars
- Non-Latin digits (Roozbeh Pournader has patches, but these are not yet integrated and may need help).
- and the sheer scale of the localization problem will eventually require changes in free software projects.
It only takes a small team to localize Linux for a language: e.g. Welsh, Icelandic, which are relatively small languages, have been pretty fully localized by small teams.
You can do the work yourself, hire the work out, or find volunteers among universities (worldwide), the world wide internet and free software community. Add to existing projects whenever possible. By checking with some of the major free software projects (e.g. Gnome, OpenOffice, Mozilla, KDE), you can often locate people already at work in your language.
Work directly in the software and content projects whenever possible. This makes your work available worldwide, while lessens the ongoing work. If you keep your localization work local, others cannot benefit from your work and effort and your software and content will be that much harder to localize.
Some example tools include pootle, kbabel and rosetta. Most software uses the GNU “gettext” libraries and standard .po files, including Sugar; Firefox and OpenOffice have their own systems for historical reasons. Wordforge is a good place to get plugged into tools and the community efforts.
The cldr project is worth watching, though OpenOffice is the first major project using this.
Remember, contribute your translations to the “upstream” projects to minimize long term effort: share your work with the world. Do not presume that if one Linux distribution has your effort that you are finished; some Linux distributions are not good about working with the community that builds and distributes the original software.
Translated strings will often be useful among many projects, not just the the project you are working on translating, therefore, since the MIT/BSD (3 clause) licenses are usable by all projects, these are the safest licenses to use for translation to enable widest sharing.
The SIL OFL license recommended for Fonts. An often overlooked issue with fonts is that they are incorporated into documents themselves (for example, into PDF documents) and that therefore licensing needs to be considered carefully.
- See also Software licensing
Localization is by nature local: but languages often crosses borders. Please contact Jim Gettys to identify issues.
We need identified people/organizations responsible for language, translation, keyboards, speech synthesis, an effective free software community leaders to help with local deployment and "on the ground" knowledge.
Sugar and sugar applications use standard .po files, and can be localized using the usual tools.
General Linux Localization
Current l10n projects
- Library strings -- header and descriptive strings for an OLPC sample library. Includes some PO-like strings for the following sections:
- Localization/www.laptop.org -- The l10n effort for the new www.laptop.org website
- We can't translate everything, but we sure want to hear what you would like to see translated into your language. If you got a translation to suggest please let us know!
Add / include links to upstream localization where appropriate.
- camera — en | es | ko | pt
Country groups and descriptions
- 한국 (S.Korea)
- 조선 (N.Korea)
- South Africa
- Sri Lanka
Korean-based Nations and Regional Communities using Korean
People using Korean as their native language are those in South Korea (한국인) and North Korea (조선인). Some Chinese and those with other nationalities, living in the Nothern part of Korea also are using Korean as their second language, because of some historical issues. They are called as 고려인(Korea-in) and 조선족 (Chosun-zok or Korean Chinese) respectively.