534
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + − + Line 14:
Line 14: − + − do not lend themselves to this approach. − * First are the FLOSS manuals (documentation) and its Sugar activity embodiment, Help Activity. − * Second, the Sugar-web-activities (based on html5 and javascript). − + Line 26:
Line 23: − + Line 37:
Line 34: − + + + Line 49:
Line 48: − + Line 67:
Line 66: − * Bislama+ − * Central Pame − * Huastec − * Kosreaean − * Songhai languages − * Tzotzil − + + + − + − * It must be possible to touch and change PO files on local machines in Sugar.+ − * It must be possible to capture that local work back at the central − Pootle server for the benefit of others. + − * Priority to Spanish language activities+ − * Other important or popular Sugar activities+ + + + + + + + + − + − Provide the I18n infrastructure to support localization of Sugarizer and sugar-web-activities.+ − * All strings not in comments are referenced by gettext+ − * All strings match a msgstr in the corresponding en.po file + − + + + − Develop a tool to parse the strings in the master files to identify the vocabulary used.+ − (see http://www.lextutor.ca/research/nation_waring_97.html" - interesting but not directly relevant − − Paul Nation developed a simple program 'range' which scans a text and identifies words by a presence − in one or more included word lists. For example, one of the 1000 most frequently used words would be printed in the default font/color. A word not on this list would be printed in red. Such a tool could be used to check the base strings for consistent use of words and for use of common English words. The cited article explains whythis is important and links to specific lists of commonly used words. − +
Obsolete
{{Obsolete}}
[[ Translation Manager ]]
This goal requires two steps - internationalization (I18n) and localization (l10n). The first step (I18n) is to provide tools and documentation to facilitate the second step (L10n). Sugar has adopted Pootle as the primary tool for I18n. However, there are two important elements which
This goal requires two steps - internationalization (I18n) and localization (l10n). The first step (I18n) is to provide tools and documentation to facilitate the second step (L10n).
In general, I18n is the reponsibility of the Sugar development team. Localization, l10n, requires effort by volunteers who know the native language as well as English (the language of the POT master files).
In general, I18n is the responsibility of the Sugar development team. Localization, l10n, requires effort by volunteers who know the native language as well as English (the language of the POT master files). Translation into mother tongues by bilingual non-English speakers (e.g. Spanish-Aymara) is also supported by keeping Spanish PO files translated at high levels of completion.
Sugar is distributed in a release (e.g. Sugar 0.108 is released in 13.2.7) with the master files updated for new and changed strings. These master files are available from http://translate.sugarlabs.org". Specifically, the files for the current releases of Sugar are identified as projects: sugar and sugar-toolkit-gtk3.
Sugar is distributed in a release (e.g. Sugar 0.108 is released in 13.2.7) with the master files updated for new and changed strings. These master files are available from http://translate.sugarlabs.org". Specifically, the files for the current releases of Sugar are identified as projects: sugar and sugar-toolkit-gtk3.
In addition, this site tracks localization of Sugar activities which support Pootle localization. There are currently seven activities which are integral to Sugar (not-erasable): Browse, Image Viewer, Log, Read, Record, Terminal, and Write (excluding Journal which is localized in Sugar). These seven activities enable Pootle localization (are projects on tranlate.sugarlabs.org).
In addition, this site tracks localization of Sugar activities which support Pootle localization. There are currently seven activities which are integral to Sugar (not-erasable): Browse (Web), Image Viewer, Log, Read, Record, Terminal, and Write (excluding Journal which is localized in Sugar). These seven activities enable Pootle localization (are projects on tranlate.sugarlabs.org).
Monitoring new activity development and advocating for i18n of code<br>
Monitoring new activity development and advocating for i18n of code<br>
(gettext formatting).
(gettext formatting for Python activities, other similar methods for JavaScript work).
Setting up new languages for availability in Pootle.
Setting up new languages for availability in Pootle.
Act as Sugar Labs i18n coordinator for oversight of performance on contracts to develop L10n projects approved by SLOBs.
Reaching upstream to create the glibc locales for new languages required for them to be selectable languages in Linux-based systems.
Reaching upstream to create the glibc locales for new languages required for them to be selectable languages in Linux-based systems.
Arranging 'L10n' days at deployments where teachers have students improve strings in the relevant .po or supply missing strings. The outcome of an 'L10n' day should be an updated localization for that native language.
Arranging 'L10n' days at deployments where teachers have students improve strings in the relevant .po or supply missing strings. The outcome of an 'L10n' day should be an updated localization for that native language.
Arrange for participating deployments to be publically recognized for their contribution.
Arrange for participating deployments to be publicly recognized for their contribution.
Suggestions by Sebastian:
Suggestions by Sebastian:
Recover L10n work done in the following languages that was lost in Pootle migration:
Recover L10n work done in the following languages that was lost in Pootle migration:
* Crioulo-PT
* Crioulo-PT
* Dari
* Dari
* Kinyarwanda
* Kinyarwanda
* Marovo
* Marovo
* Nauruan
* Nauruan
* Sindhi
* Sindhi
* Tuvaluan
* Tuvaluan
* Urdu
* Urdu
Recover L10n and grepo connections to numerous missinga ctivities
Recover L10n and repo connections to numerous missing activities
===ToDo:===
===ToDo:===
Discussion in the committee shows that our I18n infrastructure is in need of urgent maintenance.
ASLO no longer provides links to the git version. Many activities were repaired by the GCI participants. These need to be reviewed to make sure that the translation files are available and current. Chris Leonard has provided a list of 'missing activities', i.e. activities which had localization files but which were misplaced in a pootle migration. Etoys has not been updated since 2009 and the localization files are no longer available in Pootle, but we do have backups. The translate.sugarlabs.org which is the repository for the localization files is missing some files.
The technical means for localization at the local level do not exist.
Provide a documented process for a local deployment to localize Sugar and some activities to a local language. The goal of the deployment is to make Sugar (and use of the XO more accessible).
* Chris Leonard has suggested that we base localization by a deployment on virtaal (a component of Pootle). He has installed and run this tool on an XO in the gnome desktop.
* As Caryl has pointed out, we also need to document this process so that it can be accomplished at a school as a classroom activity. This involves training teachers and providing tutorials for students.
Identify Sugar activities in ASLO which do not support localization (are not projects in translate.sugarlabs.org). Arrange for them to use gettext. Create master files (localize) to English.
Identify Sugar activities in ASLO which do not support localization (are not projects in translate.sugarlabs.org). Arrange for them to use gettext. Create master files (localize) to English.
* Priority to Spanish language activities
* Other important or popular Sugar activities
Make L10n activity more visible.
Adam Holt has suggested some regular blogging or microblogging to highlight achievements by the L10n community. There are some potentially low-cost ways to achieve this by making Pootle a little "noisier" (in the ggod sense). By way of example, we used to havea mailing list that monitored every commit made by the old Pootle instance http://lists.sugarlabs.org/archive/pootle-commits/
The new Pootle has a number of RSS feeds that could be channeled to a more visible format echoing more loudly the action happening on Poolte.
Sugar development could review Sugar (Python) activities to see if they support Pootle and attempt, eg. through GSOC, to get activities upgraded to implement Pootle and to include a base set of English Pootle files.
Sugar development could review Sugar (Python) activities to see if they support Pootle and attempt, eg. through GSOC, to get activities upgraded to implement Pootle and to include a base set of English Pootle files.
Define a standard I18n method for Sugarizer and sugar-web-activities.
Define a standard I18n method for Sugarizer and sugar-web-activities. Chris Leonard recommends using the procedure adopted for turtleblocks.js. We need corresponding documentation of this process to enable it to be used immediately by GSOC participants who implement or port activities as sugar-web-activities.
Determine whether a common process can be used to localize sugar-web-activities and Sugarizer and its activities. (e.g. by using polyglot.js)
Provide a tool to to test python source code for compliance with the needs of Pootle
Provide a tool to to test python source code for compliance with the needs of Pootle
* All strings not in comments are referenced by gettext
* All strings match a msgstr in the corresponding en.po file
Provide a tool to verify that the .po file for all localizations are included in a release.
This may not be feasible since some strings ought not to be localized (e.g. the gsettings schema).
Provide a tool to verify that the available localizations are included in a release.
Develop a glossary of terms needed to refer to the XO, Sugar, and actions to be taken by users (e.g. close the XO, switch to the Group View).
Develop a glossary of terms needed to refer to the XO, Sugar, and actions to be taken by users (e.g. close the XO, switch to the Group View).
The range.py (needing refinement) can be used to look at the strings in a po file to be localized to ensure that they do not use conflicting words or a more technical vocabulary that necessary. Every extra string in the master file may result in 50-100 translations.
Prepare a GSOC task to develop an I18n strategy and supporting tools for javascript activities. The following can be a good starting point:
Prepare a GSOC task to develop an I18n strategy and supporting tools for JavaScript activities. The following can be a good starting point:
"http://www.localeplanet.com/"
"http://www.localeplanet.com/"