https://wiki.sugarlabs.org/api.php?action=feedcontributions&user=Dupuy&feedformat=atomSugar Labs - User contributions [en]2024-03-28T19:14:52ZUser contributionsMediaWiki 1.35.2https://wiki.sugarlabs.org/index.php?title=Features/Touchpad_control_panel_section&diff=70233Features/Touchpad control panel section2011-10-26T00:34:50Z<p>Dupuy: /* Summary */ selection, not section</p>
<hr />
<div><br />
<noinclude>{{TOCright}}<br />
[[Category:Feature|Touchpad section for Control Panel]]<br />
[[Category:Feature Ready for Release Manager]]<br />
</noinclude><br />
<br />
== Summary ==<br />
This is an enhancement to the Control Panel that enables the selection of resistive or capacitative mode for the Touchpad on the OLPC XO-1 CL1 laptop.<br />
<br />
== Owner ==<br />
* Name: [[User:Walter|Walter Bender]]<br />
* Email: <walter at sugarlabs dot org><br />
<br />
== Current status ==<br />
* Targeted release: (0.90)<br />
* Last updated: (16 Aug 2010)<br />
* Percentage of completion: 100%<br />
* Comment: feature accepted, patch pushed<br />
<br />
This feature is being tracked in [http://dev.sugarlabs.org/ticket/2006 Ticket 2006].<br />
<br />
=== Comment ===<br />
<br />
After further consideration, it was decided to move this feature to the device section of the Frame.<br />
<br />
The new device code (and related artwork) are attached to Ticket 2006.<br />
<br />
It was also decided to default to capacitive mode upon reboot (See http://lists.sugarlabs.org/archive/sugar-devel/2010-August/025955.html).<br />
<br />
[[File:Finger.png|300px]]<br />
[[File:Stylus.png|300px]]<br />
<br />
== Benefit to Sugar ==<br />
There are approximately 1000000 XO-1 CL1 deployed. Many have very flaky capacitive touchpads, which makes the Sugar experience very tedious. This patch would enable users to switch to the resistive touchpad and in theory have a better experience. (Tests are being conducted in Peru, Paraguay, and Nigeria.)<br />
<br />
== Scope ==<br />
To implement this feature:<br />
<br />
* two new icons were added to share/icons/sugar/scalable/devices:<br />
::capacitive.svg and resistive.svg<br />
* a new section was added to sugar/extensions/cpsection<br />
:: touchpad<br />
* a new icon was added to sugar/data/icons<br />
::module_touchpad.svg<br />
<br />
We still need a script to be added to olpc-utils that is executed at boot time to: (1) change the mode of<br />
/sys/devices/platform/i8042/serio1/ptmode to 666; and (2) write a 1 to that node if a flag file exists ("/home/olpc/.olpc-pentablet-mode").<br />
<br />
== How To Test ==<br />
{{:{{PAGENAME}}/Testing}}<br />
<br />
== User Experience ==<br />
Anyone who has used Sugar in a high-humidity or dust environment on the CL1 hardware has probably experienced the jumping cursor due to the malfunctioning capacitive touchpad. Using a stylus is a different experience, but more predictable and robust in these situations.<br />
<br />
Note that the section only will appear on CL1 hardware. There is no change to user experience with Sugar on other hardware platforms, including the more recent versions of the XO-1.0.<br />
<br />
== Dependencies ==<br />
No additional dependencies are required to implement this feature.<br />
<br />
== Contingency Plan ==<br />
None necessary, revert to previous release behavior.<br />
<br />
== Documentation ==<br />
<br />
== Release Notes ==<br />
<br />
[[File:Touchpad-control-panel-selection.png]]<br />
<br />
''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.''<br />
<br />
== Comments and Discussion ==<br />
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Traducciones_espa%C3%B1ol&diff=65803Traducciones español2011-05-17T21:00:46Z<p>Dupuy: hace funcionando los enlaces al Pootle</p>
<hr />
<div>El sistema que empleamos para traducir se llama Pootle, y se accede desde [http://translate.sugarlabs.org translate.sugarlabs.org]. El sistema Pootle tiene un glosario de terminología que se usa para sugerencias que aparece al lado derecho de la pantalla, baja "relacionado."<br />
<br />
== Convenciones ==<br />
<br />
Dado que las traducciones son realizadas por voluntarios, y no las hace una única persona, puede haber diferencias de criterio y en más de una oportunidad ha pasado que se cambian traducciones según el criterio de quien hace la traducción.<br />
<br />
El objetivo de esta página es definir criterios comunes y aplicarlos en todas las actividades, esto hará mas sencillo el aprendizaje, la documentacion, etc. Podemos usar la lista de correo olpc-sur para discutir las traducciones.<br />
<br />
Una vez convenidas, se pueden pasar al [http://translate.sugarlabs.org/es/terminology/glossary.po?view_mode=translate glosario de Pootle]<br />
<br />
'''ATENCION:'''<br />
<br />
Antes de agregar terminos en esta página, es conveniente discutir los mismos en las listas olc-sur o localization para lograr un consenso.<br />
<br />
No modifique palabras ya acordadas sin antes consultar en la lista.<br />
<br />
=== Zoom ===<br />
<br />
==== Definicion ====<br />
Se debe usar "Ampliar" para "Zoom in" y "Reducir" para "Zoom out".<br />
"Zoom to width" debe ser "Ajustar al ancho" y "Zoom to fit" debe ser "Ajustar a la pantalla"<br />
<br />
==== Razonamiento ====<br />
Para traducir "Zoom Out" se han usado los terminos "Alejarse" o "Reducir", y para "Zoom in" "Acercarse" o "Ampliar"<br />
El uso de "Alejar" o "Acercar" no es correcto, y se ha llegado a aplicar en sentido inverso. Por otro lado tambien tenemos que traducir "Zoom to width" y "Zoom to fit" que no se traducen correctamente con acercar y alejar.<br />
<br />
Al dia de la fecha, se utilizan estas traducciones en Browse, Colors, ImageViewer, Labyrinth, Read y Write<br />
<br />
==== Autor / Fecha ====<br />
<br />
Gonzalo Odiard - gonzalo at laptop dot org / 17/5/2011<br />
<br />
<br />
=== Heading ===<br />
<br />
==== Definicion ====<br />
<br />
Rumbo<br />
<br />
==== Razonamiento ====<br />
<br />
* Históricamente, total la linea de traducciones de WinLogo, MSWLogo, XLogo, FMSLogo utilizan estan traducción.<br />
<br />
* Se suele decir "tomo rumbo norte"<br />
<br />
==== Autor / Fecha ====<br />
<br />
--[[User:DanielAjoy|DanielAjoy]] 12:13, 17 May 2011 (EDT)</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Translation_Team/FAQ&diff=48979Translation Team/FAQ2010-02-26T19:55:17Z<p>Dupuy: /* What do you mean by "string frozen"? */ lang-pap -> your language</p>
<hr />
<div><noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}<br />
{{TeamHeader|Translation Team}}<br />
Welcome to the [[Translation Team]] FAQ! The aim of this page is to provide an up to date list of common questions that we get about the Translation Team. This page contains many frequently-asked questions along with some answers.<br />
We encourage you to answer questions and keep these pages organized.<br />
</noinclude><br />
: To ask the [[Translation Team]] a question, please '''[[Talk:Translation Team/FAQ|post questions here]]'''. <br />
<br />
=== General ===<br />
==== How do I find the Sugarlabs pootle projects? ====<br />
: See http://translate.sugarlabs.org.<br />
<br />
==== I have a question that is not answered here - how do I contact you? ====<br />
: You can find us on IRC at irc://irc.freenode.net#olpc-pootle. We also have a mailing list to discuss localisation related stuff. You can subscribe to the list by visiting http://lists.laptop.org/listinfo/localization. You can also [[#ask a question]].<br />
<br />
:If you face a problem that is affecting the way in which you (or others) would normally work, please mail [mailto:translate@rt.laptop.org translate@rt.laptop.org], stating the problems you are facing. The request will get logged in our Request Tracker installation.<br />
<br />
:You should use translate@rt.laptop.org for things like<br />
:* Forgotten passwords<br />
:* Error messages in Pootle<br />
:* Pootle being unresponsive<br />
<br />
:Requests like addition of new languages, addition of new projects, etc, follow the old workflow, and they should be done via Trac at dev.laptop.org.<br />
<br />
:The [http://www.translate.org.za Pootle developers] also have a mailing list for Pootle discussion - you can subscribe and or search the archives at http://lists.sourceforge.net/lists/listinfo/translate-pootle - however please post your questions to the SugarLabs/OLPC localization list above, as they may not be relevant to the larger Pootle community.<br />
<br />
==== Things that you should initially try to resolve your problems ====<br />
<br />
:* Log out, and log in again, with the language choice at log in time being set to "Default"<br />
:* Avoiding searching or uploading for large files (e.g. Etoys). If you need to upload/merge a large file, mail translate@rt.laptop.org<br />
<br />
==== Where do I find a list of language teams and their administrators? ==== <br />
: A current list of language teams, along with their administrators (if any) is available at [[olpc:Pootle#Sign-up]].<br />
<br />
==== There are so many projects. Which one do I start off with? ====<br />
: It depends on the decision of the language team you are a part of. We recommend that you translate at least Glucose, Fructose (and Terminology, to ensure consistency) before moving on to the other projects.<br />
<br />
==== I don't understand the nomenclature of the projects. Could you explain it to me? ====<br />
: Here's a table for your reference:<br />
<br />
{| {{table}}<br />
| align="center" style="background:#f0f0f0;"|'''Project Name'''<br />
| align="center" style="background:#f0f0f0;"|'''Description'''<br />
| align="center" style="background:#f0f0f0;"|'''String Frozen'''<br />
|-<br />
| Etoys||The entire Etoys package (excluding the example projects)||No<br />
|-<br />
| Fructose||A set of core activities which follow the Sugarlabs release schedule. This is the bleeding edge, development version, which will be stabilized every six months||No<br />
|-<br />
| Fructose 0.84||A set of core activities which follow the Sugarlabs release schedule. This is the 0.84 release||Yes<br />
|-<br />
| Fructose 0.82||A set of core activities which follow the Sugarlabs release schedule. This is the 0.82 release||Yes<br />
|-<br />
| Glucose||The core Sugar libraries. This is the bleeding edge, development version, which will be stabilized every six months||No<br />
|-<br />
| Glucose 0.84||The core Sugar libraries. This is the 0.84 release ||Yes<br />
|-<br />
| Glucose 0.82||The core Sugar libraries. This is the 0.82 release ||Yes<br />
|-<br />
| Honey||Non fructose activities (do not follow any regular schedule)||No<br />
|-<br />
| Terminology||A set of common terms and phrases which occur in Sugar, useful for maintaining consistency and for defining a standard.||Yes<br />
|-<br />
| OLPC Content||Strings related to OLPC PR materials||Yes<br />
|-<br />
| OLPC Software||Packages specifically for the XO Sugar - GNOME desktop switching||Yes<br />
|-<br />
| <br />
|}<br />
<br />
You can also refer to [[Translation_Team/Pootle_Projects | this page]] for more details.<br />
<br />
==== What do you mean by "string frozen"? ====<br />
:First and most important is that "string freeze" is a restriction on developers and not translators. String freeze means developers need to stop changing UI strings so that translators can do their final work prior to release, in other words, string freeze is a start signal for translators to perform their final reviews and commits of PO files, not a stop signal, even the release date itself is not a stop signal for localization.<br />
<br />
:Second is that even after a release is made and declared final and stable, localizers can complete their work and a deployment team can make a customization stick for a deployment that includes the post-release localization work, so you will not "miss the boat" for providing a localized UI environment for your deployment if work on your language is not complete by the next release date. This is part of the beauty of separating the code (release) from the strings (PO/MO files).<br />
<br />
==== Is it possible to edit more than one string at a time? ====<br />
: No. For on-line translations you can only edit one string at a time. Each project/language administrator has the power to enable off-line translations, but that needs to be coordinated and controlled; currently we lack the man-power (read administrators) to guarantee that workflow.<br />
<br />
==== Can we use translation memories? ====<br />
: Yes.<br />
<br />
==== Can I translate off-line? ====<br />
: Depends. Initially, Pootle's ability to import PO files is not enabled, and it will be up to each administrator (language/project) to decide if it will be allowed, who will have said ability and set up the appropriate workflow.<br />
<br />
==== How do I see/test/check my translations in action? ====<br />
: There are several methods to do that. See [[Translation_Team/Testing]] for the details.<br />
<br />
==== I am translating for a deployment of OLPC XO laptops. What version should I translate? ====<br />
:As of this writing (Feb. 2010) you are most likely looking at deploying the 0.84 versions of Fructose / Glucose as the details of deploying the very latest version of Sugar on the XO have not yet been fully worked out (at least to a level that is stable enough for a live deployment), although there is ongoing work on that. Version 0.84 Fructose / Glucose strings will not be changing and the string freeze for those was a long time ago, so they are a stable target.<br />
<br />
==== I have trouble translating the English to my language. Can I see translations in another language? ====<br />
: Pootle can show you the translations in an third language while you translate. In order to see that, select the alternate language from your options page (once you have logged in).<br />
<br />
==== How do I jump directly to the untranslated strings? ====<br />
: From the project page of your language (eg: Fructose for Spanish), click on the ''Show Editing Function'', and for each file, you will get a link called ''View untranslated'' which would take you directly to the untranslated strings.<br />
<br />
==== How do I integrate translations into a software release/build? ====<br />
:A language administrator must perform the Commit to VCS action through the Pootle user interface, it is on the Translate tab of Pootle for those users like admins that have the commit PO file privilege. Pootle is directly connected up to the git software repository (git). The language admin's action in Pootle triggers a commit in the software repository; the PO file for that language can be found in the /po directory of the git project's source code tree and after the commit of the PO file, you can see the evidence in the git commit log and in the date stamp of the PO file in the source tree.<br />
<br />
==== Why are strings that were translated in Pootle not showing up in the releases/language packs? ====<br />
:Suggested strings will not appear in the committed PO file and will not be shown to users. Translations marked as "fuzzy" will be committed, but will not be built into activities or language packs; for these strings, as well as ones that have not been translated at all, users will see the English version. There are no functional consequences of partially completed PO files, but as you can imagine, it is not a pretty or desirable result to have mixed language UI strings.<br />
<br />
:For suggested strings to be incorporated in the translation, they must be accepted. Accepting or rejecting suggestions is done by language admins (or other localizers that may be granted the review privilege in a given language). It is generally part of the review process, which should take place before any commit, to clear up any pending suggestions.<br />
<br />
==== How can I translate Pootle itself into my language? ====<br />
: Especially when working with less technical translators, having Pootle operate in their native language can be helpful. While Pootle supports many languages, some of the language targets for Sugar do not yet have Pootle translations. Previously Pootle used the "live" translations from the Pootle project in the Sugar Labs Pootle server, but this is no longer the case. All translations of Pootle should now be done at http://pootle.locamotion.org/projects/pootle/ - if your language is not listed there, contact the Pootle developers on the translate-pootle mailing list and it can be added. Once the translation is substantially complete, contact us and the translated strings can be copied over to the Sugar Labs Pootle. In general, however, if your translation team is able to use Pootle in English or another supported language, it is better to concentrate on translating Fructose/Glucose/etc. first.<br />
<br />
=== Trouble-shooting ===<br />
<br />
==== I can't translate! (or) I only get the "Suggest" button and not the "Submit" button ====<br />
: Several possibilities:<br />
:# Pootle account &mdash; by default, anonymous users aren't allowed to translate, so you need to register first.<br />
:# Pootle language &mdash; in order to to have 'access' to a given project you need to have a language in your user options that is associated to the project<br />
:# Pootle project &mdash; you must have the project in your list of projects in your user options in order to be considered as a non-anonymous translator<br />
:# Language+Project rights &mdash; although projects are relatively open (suffices to be registered to be able to translate) those rights are specified by the administrator. If all of the above are satisfied please ask your language administrator(s) or ask in the [http://lists.laptop.org/listinfo/localization mailing list].<br />
<br />
=== Administrative ===<br />
<br />
==== How do I add a project to be translated ? ====<br />
: If you are using the GIT services on git.sugarlabs.org, just file a ticket at http://dev.sugarlabs.org under the component localization, mentioning the name of the GIT repository. If your project is hosted somewhere else, please file a ticket detailing how to access your project's version control setup, and we'll try to figure out a way how to best integrate your project's translation related files.<br />
<br />
==== How do I start a translation team for my language ?====<br />
: File a ticket at http://dev.sugarlabs.org with your name, email address, Pootle username (if you have already registered), language name and language code. We will setup the relevant accounts and permissions for you. You should file the ticket under the component localization.<br />
<br />
==== Do you have any document/guide for a language coordinator ?====<br />
: The OpenOffice.org people have an excellent guide about Pootle - you can read it online at http://wiki.services.openoffice.org/wiki/Pootle_User_Guide#Pootle_Userguide_for_Translation_Leads<br />
<br />
=== Ask a question ===<br />
<br />
Have a question that is not answered above? Add it below, subscribe and send an email to '''<tt>[mailto:localization@lists.laptop.org localization@lists.laptop.org]</tt>''', or try the <tt>irc://irc.freenode.net#olpc-pootle</tt> [[IRC]] [http://webchat.freenode.net/?randomnick=1&channels=olpc-pootle&prompt=1 channel].<br />
<br />
:<b>Faster navigation</b><br />
:*I would thank a way to go directly to the "need to translated" parts. In this moment I need to "travel" (clicking and clicking) trough all the "translated" parts until I reach the "not translated". I know: easy to say... hard to do. Just letting you know (for the records). Javier Rodriguez, Lima. Peru 3 March 2008.<br />
:::This '''is''' possible with Pootle (although in the past it has sometimes failed due to timeouts for very large projects like Etoys). From a project translation page (e.g. the Spanish [https://dev.laptop.org/translate/es/terminology/ terminology] page), click on [https://dev.laptop.org/translate/es/terminology/index.html?editing=1 Mostrar Funciones de Edición] (Show Editing Functions) and then you will have an option to [https://dev.laptop.org/translate/es/terminology/translate.html?fuzzy=1&editing=1&blank=1 Ver No Traducidas] (Show Untranslated) which takes you directly to the parts that have not been translated (or have fuzzy translations). You can use the Regresar/Saltar buttons (Back/Skip) as well as the others next to those to go to the next untranslated item without having to page through parts that are translated. Note that if you use direct navigation to edit another entry, you will lose the extra restrictions embedded in the URL (translate.html?fuzzy=1&editing=1&blank=1) and the buttons will now just back/skip to the immediately preceding/following entries, whether translated or not. To recover the restriction, go back and re-click the Show Untranslated link or just add &fuzzy=1&blank=1 to the current URL (or just reload the page if those are already in the URL). --[[User:Dupuy|@alex]] 00:05, 18 April 2008 (EDT)<br />
<br />
<br />
<br />
<noinclude><br />
See the Community [[Sugar Labs/FAQ|FAQ]] list for more information.<br />
[[Category:Translation]]<br />
</noinclude><br />
<br />
[[Category:FAQ]]</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Translation_Team/FAQ&diff=48973Translation Team/FAQ2010-02-26T19:42:28Z<p>Dupuy: /* I have trouble translating the English to my language. Can I see translations in another language? */</p>
<hr />
<div><noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}<br />
{{TeamHeader|Translation Team}}<br />
Welcome to the [[Translation Team]] FAQ! The aim of this page is to provide an up to date list of common questions that we get about the Translation Team. This page contains many frequently-asked questions along with some answers.<br />
We encourage you to answer questions and keep these pages organized.<br />
</noinclude><br />
: To ask the [[Translation Team]] a question, please '''[[Talk:Translation Team/FAQ|post questions here]]'''. <br />
<br />
=== General ===<br />
==== How do I find the Sugarlabs pootle projects? ====<br />
: See http://translate.sugarlabs.org.<br />
<br />
==== I have a question that is not answered here - how do I contact you? ====<br />
: You can find us on IRC at irc://irc.freenode.net#olpc-pootle. We also have a mailing list to discuss localisation related stuff. You can subscribe to the list by visiting http://lists.laptop.org/listinfo/localization. You can also [[#ask a question]].<br />
<br />
:If you face a problem that is affecting the way in which you (or others) would normally work, please mail [mailto:translate@rt.laptop.org translate@rt.laptop.org], stating the problems you are facing. The request will get logged in our Request Tracker installation.<br />
<br />
:You should use translate@rt.laptop.org for things like<br />
:* Forgotten passwords<br />
:* Error messages in Pootle<br />
:* Pootle being unresponsive<br />
<br />
:Requests like addition of new languages, addition of new projects, etc, follow the old workflow, and they should be done via Trac at dev.laptop.org.<br />
<br />
:The [http://www.translate.org.za Pootle developers] also have a mailing list for Pootle discussion - you can subscribe and or search the archives at http://lists.sourceforge.net/lists/listinfo/translate-pootle - however please post your questions to the SugarLabs/OLPC localization list above, as they may not be relevant to the larger Pootle community.<br />
<br />
==== Things that you should initially try to resolve your problems ====<br />
<br />
:* Log out, and log in again, with the language choice at log in time being set to "Default"<br />
:* Avoiding searching or uploading for large files (e.g. Etoys). If you need to upload/merge a large file, mail translate@rt.laptop.org<br />
<br />
==== Where do I find a list of language teams and their administrators? ==== <br />
: A current list of language teams, along with their administrators (if any) is available at [[olpc:Pootle#Sign-up]].<br />
<br />
==== There are so many projects. Which one do I start off with? ====<br />
: It depends on the decision of the language team you are a part of. We recommend that you translate at least Glucose, Fructose (and Terminology, to ensure consistency) before moving on to the other projects.<br />
<br />
==== I don't understand the nomenclature of the projects. Could you explain it to me? ====<br />
: Here's a table for your reference:<br />
<br />
{| {{table}}<br />
| align="center" style="background:#f0f0f0;"|'''Project Name'''<br />
| align="center" style="background:#f0f0f0;"|'''Description'''<br />
| align="center" style="background:#f0f0f0;"|'''String Frozen'''<br />
|-<br />
| Etoys||The entire Etoys package (excluding the example projects)||No<br />
|-<br />
| Fructose||A set of core activities which follow the Sugarlabs release schedule. This is the bleeding edge, development version, which will be stabilized every six months||No<br />
|-<br />
| Fructose 0.84||A set of core activities which follow the Sugarlabs release schedule. This is the 0.84 release||Yes<br />
|-<br />
| Fructose 0.82||A set of core activities which follow the Sugarlabs release schedule. This is the 0.82 release||Yes<br />
|-<br />
| Glucose||The core Sugar libraries. This is the bleeding edge, development version, which will be stabilized every six months||No<br />
|-<br />
| Glucose 0.84||The core Sugar libraries. This is the 0.84 release ||Yes<br />
|-<br />
| Glucose 0.82||The core Sugar libraries. This is the 0.82 release ||Yes<br />
|-<br />
| Honey||Non fructose activities (do not follow any regular schedule)||No<br />
|-<br />
| Terminology||A set of common terms and phrases which occur in Sugar, useful for maintaining consistency and for defining a standard.||Yes<br />
|-<br />
| OLPC Content||Strings related to OLPC PR materials||Yes<br />
|-<br />
| OLPC Software||Packages specifically for the XO Sugar - GNOME desktop switching||Yes<br />
|-<br />
| <br />
|}<br />
<br />
You can also refer to [[Translation_Team/Pootle_Projects | this page]] for more details.<br />
<br />
==== What do you mean by "string frozen"? ====<br />
:First and most important is that "string freeze" is a restriction on developers and not translators. String freeze means developers need to stop changing UI strings so that translators can do their final work prior to release, in other words, string freeze is a start signal for translators to perform their final reviews and commits of PO files, not a stop signal, even the release date itself is not a stop signal for localization.<br />
<br />
:Second is that even after a release is made and declared final and stable, localizers can complete their work and a deployment team can make a customization stick for a deployment that includes the post-release localization work, so you will not "miss the boat" for providing a localized UI environment for your deployment if work on lang-pap is not complete by the next release date. This is part of the beauty of separating the code (release) from the strings (PO/MO files).<br />
<br />
==== Is it possible to edit more than one string at a time? ====<br />
: No. For on-line translations you can only edit one string at a time. Each project/language administrator has the power to enable off-line translations, but that needs to be coordinated and controlled; currently we lack the man-power (read administrators) to guarantee that workflow.<br />
<br />
==== Can we use translation memories? ====<br />
: Yes.<br />
<br />
==== Can I translate off-line? ====<br />
: Depends. Initially, Pootle's ability to import PO files is not enabled, and it will be up to each administrator (language/project) to decide if it will be allowed, who will have said ability and set up the appropriate workflow.<br />
<br />
==== How do I see/test/check my translations in action? ====<br />
: There are several methods to do that. See [[Translation_Team/Testing]] for the details.<br />
<br />
==== I am translating for a deployment of OLPC XO laptops. What version should I translate? ====<br />
:As of this writing (Feb. 2010) you are most likely looking at deploying the 0.84 versions of Fructose / Glucose as the details of deploying the very latest version of Sugar on the XO have not yet been fully worked out (at least to a level that is stable enough for a live deployment), although there is ongoing work on that. Version 0.84 Fructose / Glucose strings will not be changing and the string freeze for those was a long time ago, so they are a stable target.<br />
<br />
==== I have trouble translating the English to my language. Can I see translations in another language? ====<br />
: Pootle can show you the translations in an third language while you translate. In order to see that, select the alternate language from your options page (once you have logged in).<br />
<br />
==== How do I jump directly to the untranslated strings? ====<br />
: From the project page of your language (eg: Fructose for Spanish), click on the ''Show Editing Function'', and for each file, you will get a link called ''View untranslated'' which would take you directly to the untranslated strings.<br />
<br />
==== How do I integrate translations into a software release/build? ====<br />
:A language administrator must perform the Commit to VCS action through the Pootle user interface, it is on the Translate tab of Pootle for those users like admins that have the commit PO file privilege. Pootle is directly connected up to the git software repository (git). The language admin's action in Pootle triggers a commit in the software repository; the PO file for that language can be found in the /po directory of the git project's source code tree and after the commit of the PO file, you can see the evidence in the git commit log and in the date stamp of the PO file in the source tree.<br />
<br />
==== Why are strings that were translated in Pootle not showing up in the releases/language packs? ====<br />
:Suggested strings will not appear in the committed PO file and will not be shown to users. Translations marked as "fuzzy" will be committed, but will not be built into activities or language packs; for these strings, as well as ones that have not been translated at all, users will see the English version. There are no functional consequences of partially completed PO files, but as you can imagine, it is not a pretty or desirable result to have mixed language UI strings.<br />
<br />
:For suggested strings to be incorporated in the translation, they must be accepted. Accepting or rejecting suggestions is done by language admins (or other localizers that may be granted the review privilege in a given language). It is generally part of the review process, which should take place before any commit, to clear up any pending suggestions.<br />
<br />
==== How can I translate Pootle itself into my language? ====<br />
: Especially when working with less technical translators, having Pootle operate in their native language can be helpful. While Pootle supports many languages, some of the language targets for Sugar do not yet have Pootle translations. Previously Pootle used the "live" translations from the Pootle project in the Sugar Labs Pootle server, but this is no longer the case. All translations of Pootle should now be done at http://pootle.locamotion.org/projects/pootle/ - if your language is not listed there, contact the Pootle developers on the translate-pootle mailing list and it can be added. Once the translation is substantially complete, contact us and the translated strings can be copied over to the Sugar Labs Pootle. In general, however, if your translation team is able to use Pootle in English or another supported language, it is better to concentrate on translating Fructose/Glucose/etc. first.<br />
<br />
=== Trouble-shooting ===<br />
<br />
==== I can't translate! (or) I only get the "Suggest" button and not the "Submit" button ====<br />
: Several possibilities:<br />
:# Pootle account &mdash; by default, anonymous users aren't allowed to translate, so you need to register first.<br />
:# Pootle language &mdash; in order to to have 'access' to a given project you need to have a language in your user options that is associated to the project<br />
:# Pootle project &mdash; you must have the project in your list of projects in your user options in order to be considered as a non-anonymous translator<br />
:# Language+Project rights &mdash; although projects are relatively open (suffices to be registered to be able to translate) those rights are specified by the administrator. If all of the above are satisfied please ask your language administrator(s) or ask in the [http://lists.laptop.org/listinfo/localization mailing list].<br />
<br />
=== Administrative ===<br />
<br />
==== How do I add a project to be translated ? ====<br />
: If you are using the GIT services on git.sugarlabs.org, just file a ticket at http://dev.sugarlabs.org under the component localization, mentioning the name of the GIT repository. If your project is hosted somewhere else, please file a ticket detailing how to access your project's version control setup, and we'll try to figure out a way how to best integrate your project's translation related files.<br />
<br />
==== How do I start a translation team for my language ?====<br />
: File a ticket at http://dev.sugarlabs.org with your name, email address, Pootle username (if you have already registered), language name and language code. We will setup the relevant accounts and permissions for you. You should file the ticket under the component localization.<br />
<br />
==== Do you have any document/guide for a language coordinator ?====<br />
: The OpenOffice.org people have an excellent guide about Pootle - you can read it online at http://wiki.services.openoffice.org/wiki/Pootle_User_Guide#Pootle_Userguide_for_Translation_Leads<br />
<br />
=== Ask a question ===<br />
<br />
Have a question that is not answered above? Add it below, subscribe and send an email to '''<tt>[mailto:localization@lists.laptop.org localization@lists.laptop.org]</tt>''', or try the <tt>irc://irc.freenode.net#olpc-pootle</tt> [[IRC]] [http://webchat.freenode.net/?randomnick=1&channels=olpc-pootle&prompt=1 channel].<br />
<br />
:<b>Faster navigation</b><br />
:*I would thank a way to go directly to the "need to translated" parts. In this moment I need to "travel" (clicking and clicking) trough all the "translated" parts until I reach the "not translated". I know: easy to say... hard to do. Just letting you know (for the records). Javier Rodriguez, Lima. Peru 3 March 2008.<br />
:::This '''is''' possible with Pootle (although in the past it has sometimes failed due to timeouts for very large projects like Etoys). From a project translation page (e.g. the Spanish [https://dev.laptop.org/translate/es/terminology/ terminology] page), click on [https://dev.laptop.org/translate/es/terminology/index.html?editing=1 Mostrar Funciones de Edición] (Show Editing Functions) and then you will have an option to [https://dev.laptop.org/translate/es/terminology/translate.html?fuzzy=1&editing=1&blank=1 Ver No Traducidas] (Show Untranslated) which takes you directly to the parts that have not been translated (or have fuzzy translations). You can use the Regresar/Saltar buttons (Back/Skip) as well as the others next to those to go to the next untranslated item without having to page through parts that are translated. Note that if you use direct navigation to edit another entry, you will lose the extra restrictions embedded in the URL (translate.html?fuzzy=1&editing=1&blank=1) and the buttons will now just back/skip to the immediately preceding/following entries, whether translated or not. To recover the restriction, go back and re-click the Show Untranslated link or just add &fuzzy=1&blank=1 to the current URL (or just reload the page if those are already in the URL). --[[User:Dupuy|@alex]] 00:05, 18 April 2008 (EDT)<br />
<br />
<br />
<br />
<noinclude><br />
See the Community [[Sugar Labs/FAQ|FAQ]] list for more information.<br />
[[Category:Translation]]<br />
</noinclude><br />
<br />
[[Category:FAQ]]</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Translation_Team/FAQ&diff=48972Translation Team/FAQ2010-02-26T19:38:42Z<p>Dupuy: /* What do you mean by "string frozen"? */ line break</p>
<hr />
<div><noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}<br />
{{TeamHeader|Translation Team}}<br />
Welcome to the [[Translation Team]] FAQ! The aim of this page is to provide an up to date list of common questions that we get about the Translation Team. This page contains many frequently-asked questions along with some answers.<br />
We encourage you to answer questions and keep these pages organized.<br />
</noinclude><br />
: To ask the [[Translation Team]] a question, please '''[[Talk:Translation Team/FAQ|post questions here]]'''. <br />
<br />
=== General ===<br />
==== How do I find the Sugarlabs pootle projects? ====<br />
: See http://translate.sugarlabs.org.<br />
<br />
==== I have a question that is not answered here - how do I contact you? ====<br />
: You can find us on IRC at irc://irc.freenode.net#olpc-pootle. We also have a mailing list to discuss localisation related stuff. You can subscribe to the list by visiting http://lists.laptop.org/listinfo/localization. You can also [[#ask a question]].<br />
<br />
:If you face a problem that is affecting the way in which you (or others) would normally work, please mail [mailto:translate@rt.laptop.org translate@rt.laptop.org], stating the problems you are facing. The request will get logged in our Request Tracker installation.<br />
<br />
:You should use translate@rt.laptop.org for things like<br />
:* Forgotten passwords<br />
:* Error messages in Pootle<br />
:* Pootle being unresponsive<br />
<br />
:Requests like addition of new languages, addition of new projects, etc, follow the old workflow, and they should be done via Trac at dev.laptop.org.<br />
<br />
:The [http://www.translate.org.za Pootle developers] also have a mailing list for Pootle discussion - you can subscribe and or search the archives at http://lists.sourceforge.net/lists/listinfo/translate-pootle - however please post your questions to the SugarLabs/OLPC localization list above, as they may not be relevant to the larger Pootle community.<br />
<br />
==== Things that you should initially try to resolve your problems ====<br />
<br />
:* Log out, and log in again, with the language choice at log in time being set to "Default"<br />
:* Avoiding searching or uploading for large files (e.g. Etoys). If you need to upload/merge a large file, mail translate@rt.laptop.org<br />
<br />
==== Where do I find a list of language teams and their administrators? ==== <br />
: A current list of language teams, along with their administrators (if any) is available at [[olpc:Pootle#Sign-up]].<br />
<br />
==== There are so many projects. Which one do I start off with? ====<br />
: It depends on the decision of the language team you are a part of. We recommend that you translate at least Glucose, Fructose (and Terminology, to ensure consistency) before moving on to the other projects.<br />
<br />
==== I don't understand the nomenclature of the projects. Could you explain it to me? ====<br />
: Here's a table for your reference:<br />
<br />
{| {{table}}<br />
| align="center" style="background:#f0f0f0;"|'''Project Name'''<br />
| align="center" style="background:#f0f0f0;"|'''Description'''<br />
| align="center" style="background:#f0f0f0;"|'''String Frozen'''<br />
|-<br />
| Etoys||The entire Etoys package (excluding the example projects)||No<br />
|-<br />
| Fructose||A set of core activities which follow the Sugarlabs release schedule. This is the bleeding edge, development version, which will be stabilized every six months||No<br />
|-<br />
| Fructose 0.84||A set of core activities which follow the Sugarlabs release schedule. This is the 0.84 release||Yes<br />
|-<br />
| Fructose 0.82||A set of core activities which follow the Sugarlabs release schedule. This is the 0.82 release||Yes<br />
|-<br />
| Glucose||The core Sugar libraries. This is the bleeding edge, development version, which will be stabilized every six months||No<br />
|-<br />
| Glucose 0.84||The core Sugar libraries. This is the 0.84 release ||Yes<br />
|-<br />
| Glucose 0.82||The core Sugar libraries. This is the 0.82 release ||Yes<br />
|-<br />
| Honey||Non fructose activities (do not follow any regular schedule)||No<br />
|-<br />
| Terminology||A set of common terms and phrases which occur in Sugar, useful for maintaining consistency and for defining a standard.||Yes<br />
|-<br />
| OLPC Content||Strings related to OLPC PR materials||Yes<br />
|-<br />
| OLPC Software||Packages specifically for the XO Sugar - GNOME desktop switching||Yes<br />
|-<br />
| <br />
|}<br />
<br />
You can also refer to [[Translation_Team/Pootle_Projects | this page]] for more details.<br />
<br />
==== What do you mean by "string frozen"? ====<br />
:First and most important is that "string freeze" is a restriction on developers and not translators. String freeze means developers need to stop changing UI strings so that translators can do their final work prior to release, in other words, string freeze is a start signal for translators to perform their final reviews and commits of PO files, not a stop signal, even the release date itself is not a stop signal for localization.<br />
<br />
:Second is that even after a release is made and declared final and stable, localizers can complete their work and a deployment team can make a customization stick for a deployment that includes the post-release localization work, so you will not "miss the boat" for providing a localized UI environment for your deployment if work on lang-pap is not complete by the next release date. This is part of the beauty of separating the code (release) from the strings (PO/MO files).<br />
<br />
==== Is it possible to edit more than one string at a time? ====<br />
: No. For on-line translations you can only edit one string at a time. Each project/language administrator has the power to enable off-line translations, but that needs to be coordinated and controlled; currently we lack the man-power (read administrators) to guarantee that workflow.<br />
<br />
==== Can we use translation memories? ====<br />
: Yes.<br />
<br />
==== Can I translate off-line? ====<br />
: Depends. Initially, Pootle's ability to import PO files is not enabled, and it will be up to each administrator (language/project) to decide if it will be allowed, who will have said ability and set up the appropriate workflow.<br />
<br />
==== How do I see/test/check my translations in action? ====<br />
: There are several methods to do that. See [[Translation_Team/Testing]] for the details.<br />
<br />
==== I am translating for a deployment of OLPC XO laptops. What version should I translate? ====<br />
:As of this writing (Feb. 2010) you are most likely looking at deploying the 0.84 versions of Fructose / Glucose as the details of deploying the very latest version of Sugar on the XO have not yet been fully worked out (at least to a level that is stable enough for a live deployment), although there is ongoing work on that. Version 0.84 Fructose / Glucose strings will not be changing and the string freeze for those was a long time ago, so they are a stable target.<br />
<br />
==== I do not know English well enough to translate from it to my language. Can I get the original messages in any other language ====<br />
: Pootle can show you the translations in an intermediate language while you translate. In order to see that, select the alternate language from your options page (once you have logged in)<br />
<br />
==== How do I jump directly to the untranslated strings? ====<br />
: From the project page of your language (eg: Fructose for Spanish), click on the ''Show Editing Function'', and for each file, you will get a link called ''View untranslated'' which would take you directly to the untranslated strings.<br />
<br />
==== How do I integrate translations into a software release/build? ====<br />
:A language administrator must perform the Commit to VCS action through the Pootle user interface, it is on the Translate tab of Pootle for those users like admins that have the commit PO file privilege. Pootle is directly connected up to the git software repository (git). The language admin's action in Pootle triggers a commit in the software repository; the PO file for that language can be found in the /po directory of the git project's source code tree and after the commit of the PO file, you can see the evidence in the git commit log and in the date stamp of the PO file in the source tree.<br />
<br />
==== Why are strings that were translated in Pootle not showing up in the releases/language packs? ====<br />
:Suggested strings will not appear in the committed PO file and will not be shown to users. Translations marked as "fuzzy" will be committed, but will not be built into activities or language packs; for these strings, as well as ones that have not been translated at all, users will see the English version. There are no functional consequences of partially completed PO files, but as you can imagine, it is not a pretty or desirable result to have mixed language UI strings.<br />
<br />
:For suggested strings to be incorporated in the translation, they must be accepted. Accepting or rejecting suggestions is done by language admins (or other localizers that may be granted the review privilege in a given language). It is generally part of the review process, which should take place before any commit, to clear up any pending suggestions.<br />
<br />
==== How can I translate Pootle itself into my language? ====<br />
: Especially when working with less technical translators, having Pootle operate in their native language can be helpful. While Pootle supports many languages, some of the language targets for Sugar do not yet have Pootle translations. Previously Pootle used the "live" translations from the Pootle project in the Sugar Labs Pootle server, but this is no longer the case. All translations of Pootle should now be done at http://pootle.locamotion.org/projects/pootle/ - if your language is not listed there, contact the Pootle developers on the translate-pootle mailing list and it can be added. Once the translation is substantially complete, contact us and the translated strings can be copied over to the Sugar Labs Pootle. In general, however, if your translation team is able to use Pootle in English or another supported language, it is better to concentrate on translating Fructose/Glucose/etc. first.<br />
<br />
=== Trouble-shooting ===<br />
<br />
==== I can't translate! (or) I only get the "Suggest" button and not the "Submit" button ====<br />
: Several possibilities:<br />
:# Pootle account &mdash; by default, anonymous users aren't allowed to translate, so you need to register first.<br />
:# Pootle language &mdash; in order to to have 'access' to a given project you need to have a language in your user options that is associated to the project<br />
:# Pootle project &mdash; you must have the project in your list of projects in your user options in order to be considered as a non-anonymous translator<br />
:# Language+Project rights &mdash; although projects are relatively open (suffices to be registered to be able to translate) those rights are specified by the administrator. If all of the above are satisfied please ask your language administrator(s) or ask in the [http://lists.laptop.org/listinfo/localization mailing list].<br />
<br />
=== Administrative ===<br />
<br />
==== How do I add a project to be translated ? ====<br />
: If you are using the GIT services on git.sugarlabs.org, just file a ticket at http://dev.sugarlabs.org under the component localization, mentioning the name of the GIT repository. If your project is hosted somewhere else, please file a ticket detailing how to access your project's version control setup, and we'll try to figure out a way how to best integrate your project's translation related files.<br />
<br />
==== How do I start a translation team for my language ?====<br />
: File a ticket at http://dev.sugarlabs.org with your name, email address, Pootle username (if you have already registered), language name and language code. We will setup the relevant accounts and permissions for you. You should file the ticket under the component localization.<br />
<br />
==== Do you have any document/guide for a language coordinator ?====<br />
: The OpenOffice.org people have an excellent guide about Pootle - you can read it online at http://wiki.services.openoffice.org/wiki/Pootle_User_Guide#Pootle_Userguide_for_Translation_Leads<br />
<br />
=== Ask a question ===<br />
<br />
Have a question that is not answered above? Add it below, subscribe and send an email to '''<tt>[mailto:localization@lists.laptop.org localization@lists.laptop.org]</tt>''', or try the <tt>irc://irc.freenode.net#olpc-pootle</tt> [[IRC]] [http://webchat.freenode.net/?randomnick=1&channels=olpc-pootle&prompt=1 channel].<br />
<br />
:<b>Faster navigation</b><br />
:*I would thank a way to go directly to the "need to translated" parts. In this moment I need to "travel" (clicking and clicking) trough all the "translated" parts until I reach the "not translated". I know: easy to say... hard to do. Just letting you know (for the records). Javier Rodriguez, Lima. Peru 3 March 2008.<br />
:::This '''is''' possible with Pootle (although in the past it has sometimes failed due to timeouts for very large projects like Etoys). From a project translation page (e.g. the Spanish [https://dev.laptop.org/translate/es/terminology/ terminology] page), click on [https://dev.laptop.org/translate/es/terminology/index.html?editing=1 Mostrar Funciones de Edición] (Show Editing Functions) and then you will have an option to [https://dev.laptop.org/translate/es/terminology/translate.html?fuzzy=1&editing=1&blank=1 Ver No Traducidas] (Show Untranslated) which takes you directly to the parts that have not been translated (or have fuzzy translations). You can use the Regresar/Saltar buttons (Back/Skip) as well as the others next to those to go to the next untranslated item without having to page through parts that are translated. Note that if you use direct navigation to edit another entry, you will lose the extra restrictions embedded in the URL (translate.html?fuzzy=1&editing=1&blank=1) and the buttons will now just back/skip to the immediately preceding/following entries, whether translated or not. To recover the restriction, go back and re-click the Show Untranslated link or just add &fuzzy=1&blank=1 to the current URL (or just reload the page if those are already in the URL). --[[User:Dupuy|@alex]] 00:05, 18 April 2008 (EDT)<br />
<br />
<br />
<br />
<noinclude><br />
See the Community [[Sugar Labs/FAQ|FAQ]] list for more information.<br />
[[Category:Translation]]<br />
</noinclude><br />
<br />
[[Category:FAQ]]</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Translation_Team/FAQ&diff=48971Translation Team/FAQ2010-02-26T19:38:02Z<p>Dupuy: /* General */ FAQ from cjl mailing list response, plus others from me</p>
<hr />
<div><noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}<br />
{{TeamHeader|Translation Team}}<br />
Welcome to the [[Translation Team]] FAQ! The aim of this page is to provide an up to date list of common questions that we get about the Translation Team. This page contains many frequently-asked questions along with some answers.<br />
We encourage you to answer questions and keep these pages organized.<br />
</noinclude><br />
: To ask the [[Translation Team]] a question, please '''[[Talk:Translation Team/FAQ|post questions here]]'''. <br />
<br />
=== General ===<br />
==== How do I find the Sugarlabs pootle projects? ====<br />
: See http://translate.sugarlabs.org.<br />
<br />
==== I have a question that is not answered here - how do I contact you? ====<br />
: You can find us on IRC at irc://irc.freenode.net#olpc-pootle. We also have a mailing list to discuss localisation related stuff. You can subscribe to the list by visiting http://lists.laptop.org/listinfo/localization. You can also [[#ask a question]].<br />
<br />
:If you face a problem that is affecting the way in which you (or others) would normally work, please mail [mailto:translate@rt.laptop.org translate@rt.laptop.org], stating the problems you are facing. The request will get logged in our Request Tracker installation.<br />
<br />
:You should use translate@rt.laptop.org for things like<br />
:* Forgotten passwords<br />
:* Error messages in Pootle<br />
:* Pootle being unresponsive<br />
<br />
:Requests like addition of new languages, addition of new projects, etc, follow the old workflow, and they should be done via Trac at dev.laptop.org.<br />
<br />
:The [http://www.translate.org.za Pootle developers] also have a mailing list for Pootle discussion - you can subscribe and or search the archives at http://lists.sourceforge.net/lists/listinfo/translate-pootle - however please post your questions to the SugarLabs/OLPC localization list above, as they may not be relevant to the larger Pootle community.<br />
<br />
==== Things that you should initially try to resolve your problems ====<br />
<br />
:* Log out, and log in again, with the language choice at log in time being set to "Default"<br />
:* Avoiding searching or uploading for large files (e.g. Etoys). If you need to upload/merge a large file, mail translate@rt.laptop.org<br />
<br />
==== Where do I find a list of language teams and their administrators? ==== <br />
: A current list of language teams, along with their administrators (if any) is available at [[olpc:Pootle#Sign-up]].<br />
<br />
==== There are so many projects. Which one do I start off with? ====<br />
: It depends on the decision of the language team you are a part of. We recommend that you translate at least Glucose, Fructose (and Terminology, to ensure consistency) before moving on to the other projects.<br />
<br />
==== I don't understand the nomenclature of the projects. Could you explain it to me? ====<br />
: Here's a table for your reference:<br />
<br />
{| {{table}}<br />
| align="center" style="background:#f0f0f0;"|'''Project Name'''<br />
| align="center" style="background:#f0f0f0;"|'''Description'''<br />
| align="center" style="background:#f0f0f0;"|'''String Frozen'''<br />
|-<br />
| Etoys||The entire Etoys package (excluding the example projects)||No<br />
|-<br />
| Fructose||A set of core activities which follow the Sugarlabs release schedule. This is the bleeding edge, development version, which will be stabilized every six months||No<br />
|-<br />
| Fructose 0.84||A set of core activities which follow the Sugarlabs release schedule. This is the 0.84 release||Yes<br />
|-<br />
| Fructose 0.82||A set of core activities which follow the Sugarlabs release schedule. This is the 0.82 release||Yes<br />
|-<br />
| Glucose||The core Sugar libraries. This is the bleeding edge, development version, which will be stabilized every six months||No<br />
|-<br />
| Glucose 0.84||The core Sugar libraries. This is the 0.84 release ||Yes<br />
|-<br />
| Glucose 0.82||The core Sugar libraries. This is the 0.82 release ||Yes<br />
|-<br />
| Honey||Non fructose activities (do not follow any regular schedule)||No<br />
|-<br />
| Terminology||A set of common terms and phrases which occur in Sugar, useful for maintaining consistency and for defining a standard.||Yes<br />
|-<br />
| OLPC Content||Strings related to OLPC PR materials||Yes<br />
|-<br />
| OLPC Software||Packages specifically for the XO Sugar - GNOME desktop switching||Yes<br />
|-<br />
| <br />
|}<br />
<br />
You can also refer to [[Translation_Team/Pootle_Projects | this page]] for more details.<br />
<br />
==== What do you mean by "string frozen"? ====<br />
:First and most important is that "string freeze" is a restriction on developers and not translators. String freeze means developers need to stop changing UI strings so that translators can do their final work prior to<br />
release, in other words, string freeze is a start signal for translators to perform their final reviews and commits of PO files, not a stop signal, even the release date itself is not a stop signal for localization.<br />
<br />
:Second is that even after a release is made and declared final and stable, localizers can complete their work and a deployment team can make a customization stick for a deployment that includes the post-release localization work, so you will not "miss the boat" for providing a localized UI environment for your deployment if work on lang-pap is not complete by the next release date. This is part of the beauty of separating the code (release) from the strings (PO/MO files).<br />
<br />
==== Is it possible to edit more than one string at a time? ====<br />
: No. For on-line translations you can only edit one string at a time. Each project/language administrator has the power to enable off-line translations, but that needs to be coordinated and controlled; currently we lack the man-power (read administrators) to guarantee that workflow.<br />
<br />
==== Can we use translation memories? ====<br />
: Yes.<br />
<br />
==== Can I translate off-line? ====<br />
: Depends. Initially, Pootle's ability to import PO files is not enabled, and it will be up to each administrator (language/project) to decide if it will be allowed, who will have said ability and set up the appropriate workflow.<br />
<br />
==== How do I see/test/check my translations in action? ====<br />
: There are several methods to do that. See [[Translation_Team/Testing]] for the details.<br />
<br />
==== I am translating for a deployment of OLPC XO laptops. What version should I translate? ====<br />
:As of this writing (Feb. 2010) you are most likely looking at deploying the 0.84 versions of Fructose / Glucose as the details of deploying the very latest version of Sugar on the XO have not yet been fully worked out (at least to a level that is stable enough for a live deployment), although there is ongoing work on that. Version 0.84 Fructose / Glucose strings will not be changing and the string freeze for those was a long time ago, so they are a stable target.<br />
<br />
==== I do not know English well enough to translate from it to my language. Can I get the original messages in any other language ====<br />
: Pootle can show you the translations in an intermediate language while you translate. In order to see that, select the alternate language from your options page (once you have logged in)<br />
<br />
==== How do I jump directly to the untranslated strings? ====<br />
: From the project page of your language (eg: Fructose for Spanish), click on the ''Show Editing Function'', and for each file, you will get a link called ''View untranslated'' which would take you directly to the untranslated strings.<br />
<br />
==== How do I integrate translations into a software release/build? ====<br />
:A language administrator must perform the Commit to VCS action through the Pootle user interface, it is on the Translate tab of Pootle for those users like admins that have the commit PO file privilege. Pootle is directly connected up to the git software repository (git). The language admin's action in Pootle triggers a commit in the software repository; the PO file for that language can be found in the /po directory of the git project's source code tree and after the commit of the PO file, you can see the evidence in the git commit log and in the date stamp of the PO file in the source tree.<br />
<br />
==== Why are strings that were translated in Pootle not showing up in the releases/language packs? ====<br />
:Suggested strings will not appear in the committed PO file and will not be shown to users. Translations marked as "fuzzy" will be committed, but will not be built into activities or language packs; for these strings, as well as ones that have not been translated at all, users will see the English version. There are no functional consequences of partially completed PO files, but as you can imagine, it is not a pretty or desirable result to have mixed language UI strings.<br />
<br />
:For suggested strings to be incorporated in the translation, they must be accepted. Accepting or rejecting suggestions is done by language admins (or other localizers that may be granted the review privilege in a given language). It is generally part of the review process, which should take place before any commit, to clear up any pending suggestions.<br />
<br />
==== How can I translate Pootle itself into my language? ====<br />
: Especially when working with less technical translators, having Pootle operate in their native language can be helpful. While Pootle supports many languages, some of the language targets for Sugar do not yet have Pootle translations. Previously Pootle used the "live" translations from the Pootle project in the Sugar Labs Pootle server, but this is no longer the case. All translations of Pootle should now be done at http://pootle.locamotion.org/projects/pootle/ - if your language is not listed there, contact the Pootle developers on the translate-pootle mailing list and it can be added. Once the translation is substantially complete, contact us and the translated strings can be copied over to the Sugar Labs Pootle. In general, however, if your translation team is able to use Pootle in English or another supported language, it is better to concentrate on translating Fructose/Glucose/etc. first.<br />
<br />
=== Trouble-shooting ===<br />
<br />
==== I can't translate! (or) I only get the "Suggest" button and not the "Submit" button ====<br />
: Several possibilities:<br />
:# Pootle account &mdash; by default, anonymous users aren't allowed to translate, so you need to register first.<br />
:# Pootle language &mdash; in order to to have 'access' to a given project you need to have a language in your user options that is associated to the project<br />
:# Pootle project &mdash; you must have the project in your list of projects in your user options in order to be considered as a non-anonymous translator<br />
:# Language+Project rights &mdash; although projects are relatively open (suffices to be registered to be able to translate) those rights are specified by the administrator. If all of the above are satisfied please ask your language administrator(s) or ask in the [http://lists.laptop.org/listinfo/localization mailing list].<br />
<br />
=== Administrative ===<br />
<br />
==== How do I add a project to be translated ? ====<br />
: If you are using the GIT services on git.sugarlabs.org, just file a ticket at http://dev.sugarlabs.org under the component localization, mentioning the name of the GIT repository. If your project is hosted somewhere else, please file a ticket detailing how to access your project's version control setup, and we'll try to figure out a way how to best integrate your project's translation related files.<br />
<br />
==== How do I start a translation team for my language ?====<br />
: File a ticket at http://dev.sugarlabs.org with your name, email address, Pootle username (if you have already registered), language name and language code. We will setup the relevant accounts and permissions for you. You should file the ticket under the component localization.<br />
<br />
==== Do you have any document/guide for a language coordinator ?====<br />
: The OpenOffice.org people have an excellent guide about Pootle - you can read it online at http://wiki.services.openoffice.org/wiki/Pootle_User_Guide#Pootle_Userguide_for_Translation_Leads<br />
<br />
=== Ask a question ===<br />
<br />
Have a question that is not answered above? Add it below, subscribe and send an email to '''<tt>[mailto:localization@lists.laptop.org localization@lists.laptop.org]</tt>''', or try the <tt>irc://irc.freenode.net#olpc-pootle</tt> [[IRC]] [http://webchat.freenode.net/?randomnick=1&channels=olpc-pootle&prompt=1 channel].<br />
<br />
:<b>Faster navigation</b><br />
:*I would thank a way to go directly to the "need to translated" parts. In this moment I need to "travel" (clicking and clicking) trough all the "translated" parts until I reach the "not translated". I know: easy to say... hard to do. Just letting you know (for the records). Javier Rodriguez, Lima. Peru 3 March 2008.<br />
:::This '''is''' possible with Pootle (although in the past it has sometimes failed due to timeouts for very large projects like Etoys). From a project translation page (e.g. the Spanish [https://dev.laptop.org/translate/es/terminology/ terminology] page), click on [https://dev.laptop.org/translate/es/terminology/index.html?editing=1 Mostrar Funciones de Edición] (Show Editing Functions) and then you will have an option to [https://dev.laptop.org/translate/es/terminology/translate.html?fuzzy=1&editing=1&blank=1 Ver No Traducidas] (Show Untranslated) which takes you directly to the parts that have not been translated (or have fuzzy translations). You can use the Regresar/Saltar buttons (Back/Skip) as well as the others next to those to go to the next untranslated item without having to page through parts that are translated. Note that if you use direct navigation to edit another entry, you will lose the extra restrictions embedded in the URL (translate.html?fuzzy=1&editing=1&blank=1) and the buttons will now just back/skip to the immediately preceding/following entries, whether translated or not. To recover the restriction, go back and re-click the Show Untranslated link or just add &fuzzy=1&blank=1 to the current URL (or just reload the page if those are already in the URL). --[[User:Dupuy|@alex]] 00:05, 18 April 2008 (EDT)<br />
<br />
<br />
<br />
<noinclude><br />
See the Community [[Sugar Labs/FAQ|FAQ]] list for more information.<br />
[[Category:Translation]]<br />
</noinclude><br />
<br />
[[Category:FAQ]]</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Translation_Team/Language_Setup&diff=43948Translation Team/Language Setup2010-02-11T18:14:17Z<p>Dupuy: further note on arabic</p>
<hr />
<div>Information needed to properly set up a language in Pootle:<br />
<br />
*Language Code [http://www.loc.gov/standards/iso639-2/php/code_list.php (ISO 639-1 or ISO 639-2)]<br />
*Number of plurals<br />
*Plural Equation<br />
*Special Characters<br />
* Language Administrator<br />
:It is very useful to set-up the first language administrator at the time the language is set up. This can be done by providing the Pootle username of the person to be made language administrator. This means they should register on Pootle, even before their language is set up, and then add their language after it is set up. <br />
<br />
This information should be included in a message to the Localization list requesting that the language be established on the Pootle server. It is preferred that the request is also filed as a ticket on the [http://bugs.sugarlabs.org/ Sugar Labs bug tracker] with the component set to "localization"<br />
<br />
== Language Plurals ==<br />
<br />
More information on plurals can be found at this page:<br />
<br />
http://translate.sourceforge.net/wiki/l10n/pluralforms<br />
<br />
A developer may use a single output string that is modified by a number. <br />
<br />
Example: "There are '''n''' incorrect answers". <br />
<br />
The Pootle interface is capable of providing the correct substitution of words based on the Number of Plurals and the Plural Equation.<br />
<br />
:As an example English has two plural forms <br />
<br />
Number of Plurals:<br />
<br />
:nplurals=2; <br />
<br />
The equation for deciding whether or not to use a plural form is the Plural Equation:<br />
<br />
:plural=(n != 1)<br />
<br />
In English, you use the plural form as long as the number is not 1<br />
<br />
*There are 0 incorrect answers<br />
*There is 1 incorrect answer<br />
*There are 2 incorrect answers<br />
<br />
<br />
Another common plural equation is:<br />
<br />
:plural=(n > 1)<br />
<br />
<br />
Some languages have very complex plural forms.<br />
<br />
Arabic:<br />
<br />
:nplurals=6<br />
<br />
:plural= n==0 ? 0 : n==1 ? 1 : n==2 ? 2 : n%100>=3 && n%100<=10 ? 3 : n%100>=11 && n%100<=99 ? 4 : 5; <br />
<br />
::''note that this is more complex than necessary as ''"&& n%100<=99"'' could be omitted without effect (this is due to conversion from CLDR format which uses "in 11..99")''<br />
<br />
Russian:<br />
<br />
:nplurals=3<br />
<br />
:plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10< =4 && (n%100<10 or n%100>=20) ? 1 : 2) <br />
<br />
== Special Characters ==<br />
<br />
Some languages require additional characters to be properly represented. Here is a useful resource for identifying special characters.<br />
<br />
http://www.eki.ee/letter/</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Translation_Team/Language_Setup&diff=43947Translation Team/Language Setup2010-02-11T17:59:41Z<p>Dupuy: add note on extraneous complexity of arabic plural equation</p>
<hr />
<div>Information needed to properly set up a language in Pootle:<br />
<br />
*Language Code [http://www.loc.gov/standards/iso639-2/php/code_list.php (ISO 639-1 or ISO 639-2)]<br />
*Number of plurals<br />
*Plural Equation<br />
*Special Characters<br />
* Language Administrator<br />
:It is very useful to set-up the first language administrator at the time the language is set up. This can be done by providing the Pootle username of the person to be made language administrator. This means they should register on Pootle, even before their language is set up, and then add their language after it is set up. <br />
<br />
This information should be included in a message to the Localization list requesting that the language be established on the Pootle server. It is preferred that the request is also filed as a ticket on the [http://bugs.sugarlabs.org/ Sugar Labs bug tracker] with the component set to "localization"<br />
<br />
== Language Plurals ==<br />
<br />
More information on plurals can be found at this page:<br />
<br />
http://translate.sourceforge.net/wiki/l10n/pluralforms<br />
<br />
A developer may use a single output string that is modified by a number. <br />
<br />
Example: "There are '''n''' incorrect answers". <br />
<br />
The Pootle interface is capable of providing the correct substitution of words based on the Number of Plurals and the Plural Equation.<br />
<br />
:As an example English has two plural forms <br />
<br />
Number of Plurals:<br />
<br />
:nplurals=2; <br />
<br />
The equation for deciding whether or not to use a plural form is the Plural Equation:<br />
<br />
:plural=(n != 1)<br />
<br />
In English, you use the plural form as long as the number is not 1<br />
<br />
*There are 0 incorrect answers<br />
*There is 1 incorrect answer<br />
*There are 2 incorrect answers<br />
<br />
<br />
Another common plural equation is:<br />
<br />
plural=(n > 1)<br />
<br />
<br />
Some languages have very complex plural forms.<br />
<br />
Arabic:<br />
<br />
nplurals=6<br />
<br />
plural= n==0 ? 0 : n==1 ? 1 : n==2 ? 2 : n%100>=3 && n%100<=10 ? 3 : n%100>=11 && n%100<=99 ? 4 : 5; <br />
<br />
:''note that this is more complex than necessary as ''"&& n%100<=99"'' could be omitted without effect)''<br />
<br />
Russian:<br />
<br />
nplurals=3<br />
<br />
plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10< =4 && (n%100<10 or n%100>=20) ? 1 : 2) <br />
<br />
== Special Characters ==<br />
<br />
Some languages require additional characters to be properly represented. Here is a useful resource for identifying special characters.<br />
<br />
http://www.eki.ee/letter/</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Developers&diff=18074Template:Developers2008-06-13T19:53:23Z<p>Dupuy: use dir="rtl" for lang-ar,lang-he</p>
<hr />
<div><noinclude>{{Translations}}</noinclude><br />
<div {{#switch: {{{trans|{{#titleparts:{{PAGENAME}}|1|2}} }}}|lang-ar|lang-he=dir="rtl" }} style="background:#BB0077; color:white;">&nbsp;&nbsp;{{#ifexist:Template:Developers/{{{trans|{{#titleparts:{{PAGENAME}}|1|2}} }}}<br />
|{{Template:Developers/{{{trans|{{#titleparts:{{PAGENAME}}|1|2}} }}} }}|For Developers}}</div><br />
[[Category:Developers]]</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=User:Dupuy&diff=5868User:Dupuy2008-06-09T15:29:53Z<p>Dupuy: New page: See my [http://wiki.laptop.org/go/User:Dupuy laptop.org wiki user page].</p>
<hr />
<div>See my [http://wiki.laptop.org/go/User:Dupuy laptop.org wiki user page].</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Talk:Welcome_to_the_Sugar_Labs_wiki&diff=5867Talk:Welcome to the Sugar Labs wiki2008-06-09T15:28:07Z<p>Dupuy: </p>
<hr />
<div>This site is a wiki. It can and may be edited by anyone. Please edit responsibly. We hope that people can contribute their knowledge to the site. Sugar labs hopes to expand and explore with the Sugar UI and OS.<br />
<br />
== News Updates ==<br />
<br />
I know this is just the beginning, but I think a lot of other people might be as curious as I to know what is happening here on a more regular basis. I also know that most people are used to using email mailing lists for this sort of thing. However, since I maintain a general disdain for email, I thought it might not be too audacious to suggest a News page for the wiki here.<br />
<br />
It would be nice to know more about where things are going and follow discussions in HTML. It might also be nice to have regular updates on what Walter and other luminaries are thinking about the direction of this whole thing. I am quite excited about the direction this is taking (although it scared me quite a bit until this site appeared), but the general lack of information makes one uncomfortable. Thus, I am making this request.<br />
<br />
[[User:LuYu|LuYu]] 18:55, 20 May 2008 (UTC)<br />
:See [http://lists.lo-res.org/pipermail/its.an.education.project/2008-May/000539.html Walter's message] from two days ago to the its.an.education.project mailing list. This wiki didn't exist more than about a week ago, but you can read the list archive via HTML [http://lists.lo-res.org/pipermail/its.an.education.project/ here]. [[User:Cjl|Cjl]] 23:17, 20 May 2008 (UTC)<br />
<br />
== Wiki Theme ==<br />
<br />
Can I get a copy of this mediawiki theme anywhere? I love it. Will Sugar Labs release it to the public?<br />
: We are happy, that you like our Shikiwiki-theme: You can download it [http://www.olpcaustria.org/mediawiki/index.php/Shiki_Wiki here]. --[[User:Helga|Helga]] 15:12, 24 May 2008 (UTC)<br />
<br />
== ParserFunctions needs to be installed ==<br />
<br />
Although the templates for translations have been copied over from laptop.org, they do not work correctly, since they depend on the [http://meta.wikimedia.org/wiki/ParserFunctions MediaWiki extension '''ParserFunctions'''], which is apparently not installed/enabled for the SugarLabs wiki. The symptom of this is stuff with <nowiki>{{#if:</nowiki> in the displayed text (e.g. in the translation box on this main welcome page. This needs to be enabled by an administrator, and may even require installing software on the server.<br />
<br />
You can see that no extensions have been installed on this MediaWiki instance by looking at [[Special:Version]] and comparing it to [http://wiki.laptop.org/go/Special:Version version] at laptop.org. [[User:Dupuy|Dupuy]] 15:22, 9 June 2008 (UTC)</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Talk:Welcome_to_the_Sugar_Labs_wiki&diff=5866Talk:Welcome to the Sugar Labs wiki2008-06-09T15:22:37Z<p>Dupuy: /* ParserFunctions needs to be installed */ new section</p>
<hr />
<div>This site is a wiki. It can and may be edited by anyone. Please edit responsibly. We hope that people can contribute their knowledge to the site. Sugar labs hopes to expand and explore with the Sugar UI and OS.<br />
<br />
== News Updates ==<br />
<br />
I know this is just the beginning, but I think a lot of other people might be as curious as I to know what is happening here on a more regular basis. I also know that most people are used to using email mailing lists for this sort of thing. However, since I maintain a general disdain for email, I thought it might not be too audacious to suggest a News page for the wiki here.<br />
<br />
It would be nice to know more about where things are going and follow discussions in HTML. It might also be nice to have regular updates on what Walter and other luminaries are thinking about the direction of this whole thing. I am quite excited about the direction this is taking (although it scared me quite a bit until this site appeared), but the general lack of information makes one uncomfortable. Thus, I am making this request.<br />
<br />
[[User:LuYu|LuYu]] 18:55, 20 May 2008 (UTC)<br />
:See [http://lists.lo-res.org/pipermail/its.an.education.project/2008-May/000539.html Walter's message] from two days ago to the its.an.education.project mailing list. This wiki didn't exist more than about a week ago, but you can read the list archive via HTML [http://lists.lo-res.org/pipermail/its.an.education.project/ here]. [[User:Cjl|Cjl]] 23:17, 20 May 2008 (UTC)<br />
<br />
== Wiki Theme ==<br />
<br />
Can I get a copy of this mediawiki theme anywhere? I love it. Will Sugar Labs release it to the public?<br />
: We are happy, that you like our Shikiwiki-theme: You can download it [http://www.olpcaustria.org/mediawiki/index.php/Shiki_Wiki here]. --[[User:Helga|Helga]] 15:12, 24 May 2008 (UTC)<br />
<br />
== ParserFunctions needs to be installed ==<br />
<br />
Although the templates for translations have been copied over from laptop.org, they do not work correctly, since they depend on the [http://meta.wikimedia.org/wiki/ParserFunctions WikiMedia extension '''ParserFunctions'''], which is apparently not installed/enabled for the SugarLabs wiki. The symptom of this is stuff with <nowiki>{{#if:</nowiki> in the displayed text (e.g. in the translation box on this main welcome page. This needs to be enabled by an administrator, and may even require installing software on the server. [[User:Dupuy|Dupuy]] 15:22, 9 June 2008 (UTC)</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Translationlist&diff=6855Template:Translationlist2008-06-07T07:56:07Z<p>Dupuy: force non-link bold for original if translated==ORIGINAL</p>
<hr />
<div>{{#ifeq:{{{translated}}}|ORIGINAL|'''{{langname-{{{origlang|en}}}}}'''|[[{{{source|{{#if:{{NAMESPACEE}}|{{NAMESPACEE}}:{{BASEPAGENAMEE}}|{{BASEPAGENAMEE}}}}}}}|{{langname-{{{origlang|en<br />
}}}}}]]}} {{#if:{{{1|}}}| {{!}} {{translationlist/item| source = {{{source|{{#if:{{NAMESPACEE}}|{{NAMESPACEE}}:{{BASEPAGENAMEE}}|{{BASEPAGENAMEE}}}}}}} | lang = {{{1}}} | translated = {{{translated}}} }} }} {{#if:{{{2|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{2}}} | translated = {{{translated}}} }} }} {{#if:{{{3|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{3}}} | translated = {{{translated}}} }} }} {{#if:{{{4|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{4}}} | translated = {{{translated}}} }} }} {{#if:{{{5|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{5}}} | translated = {{{translated}}} }} }} {{#if:{{{6|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{6}}} | translated = {{{translated}}} }} }} {{#if:{{{7|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{7}}} | translated = {{{translated}}} }} }} {{#if:{{{8|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{8}}} | translated = {{{translated}}} }} }} {{#if:{{{9|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{9}}} | translated = {{{translated}}} }} }} {{#if:{{{10|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{10}}} | translated = {{{translated}}} }} }} {{#if:{{{11|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{11}}} | translated = {{{translated}}} }} }} {{#if:{{{12|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{12}}} | translated = {{{translated}}} }} }} {{#if:{{{13|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{13}}} | translated = {{{translated}}} }} }} {{#if:{{{14|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{14}}} | translated = {{{translated}}} }} }} {{#if:{{{15|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{15}}} | translated = {{{translated}}} }} }} {{#if:{{{16|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{16}}} | translated = {{{translated}}} }} }} {{#if:{{{17|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{17}}} | translated = {{{translated}}} }} }} {{#if:{{{18|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{18}}} | translated = {{{translated}}} }} }} {{#if:{{{19|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{19}}} | translated = {{{translated}}} }} }} {{#if:{{{20|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{20}}} | translated = {{{translated}}} }} }} {{#if:{{{21|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{21}}} | translated = {{{translated}}} }} }}</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Translations/instructions&diff=6722Template:Translations/instructions2008-06-07T07:50:04Z<p>Dupuy: add translated={{{translated}}} pass-through to instructions for /translations "template"</p>
<hr />
<div><small>Please copy/paste "<nowiki>{{</nowiki>Translationlist {{!}} <i>xx</i> {{!}} origlang=en {{!}} translated={{{translated}}}<nowiki>}}</nowiki>" (where ''xx'' is [[ISO 639]] language code for your translation) to {{{{NAMESPACE}}:{{PAGENAME}}/translations}}</small></div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Translations&diff=15354Template:Translations2008-06-07T07:47:09Z<p>Dupuy: pass translated=ORIGINAL to PAGENAME/translationes "template"</p>
<hr />
<div><div style="border-top:1px solid #888888; border-bottom:1px solid #888888; margin:0px;"><br />
<table width="100%" cellpadding="0" cellspacing="0" style="background-color:#d0e6f9; color:grey"><br />
<tr><br />
<td>&nbsp;&nbsp;{{{1|{{#ifexist: {{NAMESPACE}}:{{PAGENAME}}/translations |{{{{NAMESPACE}}:{{PAGENAME}}/translations|translated=ORIGINAL}}|{{translations/instructions}} }}}}}</td><br />
<td align="right" style="font-size:80%">[[Translating/HowTo|HowTo]]&nbsp;'''[ID#&nbsp;{{REVISIONID}}]'''&nbsp;{{#if:{{{1|}}}||&nbsp;<span class="plainlinks">[{{fullurl:{{NAMESPACE}}:{{PAGENAME}}/translations|action=edit}} <tt>'''+/-'''</tt>]&nbsp;&nbsp;</span>}}</td></tr></table><br />
</div><includeonly>[[Category:Translated Pages]]</includeonly><br />
<noinclude><!--<br />
<br />
The reason why there's an HTML TABLE (instead of a wiki table) was because when a sub-page containing '|' characters was included, they were interpreted / parsed as table cell parameters, resulting in the first 'translated page' lost... or interpreted as invalid cell parameters.<br />
<br />
Switching to an html table solved the problem.<br />
<br />
-->[[Category:Template]]<br />
<br />
The intent of this template is to mimic the inverse of the [[Template:Translation]] (which is geared towards the ''translated'' page) by having a template to be placed in the ''original'' pages while preserving the capability to navigate all the translations.<br />
<br />
'''NOTE:''' When [[translating]] (or updating a translated page) you '''MUST''' update the ''<tt>version</tt>'' number of the [[Template:Translation|<tt><nowiki>{{Translation ... version = xxxxx ... }}</nowiki></tt>]]&mdash;with the value reported on the far right: '''<tt>[ID# {{REVISIONID}}]</tt>''' by this template in the ''<tt>source</tt>'' page. This will allow exact comparisons between the current version and the version originally translated or last updated.<br />
<br />
== Usage ==<br />
<br />
If no argument is provided, the sub-page <tt>currentPage/translations</tt> will be included. This page should use the {{tl|Translationlist}} template to create a list of available translations. For instance, putting <nowiki>{{Translationlist|es|pt|origlang=en}}</nowiki> will result in a list like:<br />
<br />
english | español | português<br />
<br />
== Not recommended usage ==<br />
<br />
If an argument is provided, it should be a fully set of wiki links with their display. Unfortunately, '|' is used as parameter delimeter and thus needs to be escaped. A solution is to use &amp;#124; &#124; or some other (discrete) separator (ie: , - /)<br />
<br />
<nowiki>{{Translations <br />
| [[One Laptop per Child|english]] &amp;#124; [[Una Laptop por Chico|español]] - [[Um Laptop para cada Criança|português]] / [[One Laptop per Child zh|中文]]}}</nowiki><br />
<br />
{{Translations <br />
| [[One Laptop per Child|english]] &#124; [[Una Laptop por Chico|español]] - [[Um Laptop para cada Criança|português]] / [[One Laptop per Child/lang-zh|中文]]}}<br />
<br />
</noinclude></div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Translationlist/item&diff=5715Template:Translationlist/item2008-06-07T07:26:13Z<p>Dupuy: mark translated language in list as non-link bold</p>
<hr />
<div>{{#ifexist:{{{source}}}/lang-{{{lang}}}|<br />
{{#ifeq:{{{lang}}}|{{{translated}}}|<br />
{{#ifexist:Template:langname-{{{lang}}}|'''{{langname-{{{lang}}}}}|{{#language:{{{lang}}}}}}}'''|<br />
[[{{{source}}}/lang-{{{lang}}}{{!}}{{#ifexist:Template:langname-{{{lang}}}|<br />
{{langname-{{{lang}}}}}|{{#language:{{{lang}}}}}}}]]}}|<br />
<small>{{ Translationlist/item/instructions|lang={{{lang}}}|source={{{source}}} }}</small><br />
}}</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Translationlist&diff=16310Template:Translationlist2008-06-07T07:14:17Z<p>Dupuy: pass translated language to Template:Translationlist/item</p>
<hr />
<div>[[{{{source|{{#if:{{NAMESPACEE}}|{{NAMESPACEE}}:{{BASEPAGENAMEE}}|{{BASEPAGENAMEE}}}}}}}|{{langname-{{{origlang|en<br />
}}}}}]] {{#if:{{{1|}}}| {{!}} {{translationlist/item| source = {{{source|{{#if:{{NAMESPACEE}}|{{NAMESPACEE}}:{{BASEPAGENAMEE}}|{{BASEPAGENAMEE}}}}}}} | lang = {{{1}}} | translated = {{{translated}}} }} }} {{#if:{{{2|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{2}}} | translated = {{{translated}}} }} }} {{#if:{{{3|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{3}}} | translated = {{{translated}}} }} }} {{#if:{{{4|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{4}}} | translated = {{{translated}}} }} }} {{#if:{{{5|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{5}}} | translated = {{{translated}}} }} }} {{#if:{{{6|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{6}}} | translated = {{{translated}}} }} }} {{#if:{{{7|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{7}}} | translated = {{{translated}}} }} }} {{#if:{{{8|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{8}}} | translated = {{{translated}}} }} }} {{#if:{{{9|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{9}}} | translated = {{{translated}}} }} }} {{#if:{{{10|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{10}}} | translated = {{{translated}}} }} }} {{#if:{{{11|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{11}}} | translated = {{{translated}}} }} }} {{#if:{{{12|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{12}}} | translated = {{{translated}}} }} }} {{#if:{{{13|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{13}}} | translated = {{{translated}}} }} }} {{#if:{{{14|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{14}}} | translated = {{{translated}}} }} }} {{#if:{{{15|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{15}}} | translated = {{{translated}}} }} }} {{#if:{{{16|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{16}}} | translated = {{{translated}}} }} }} {{#if:{{{17|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{17}}} | translated = {{{translated}}} }} }} {{#if:{{{18|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{18}}} | translated = {{{translated}}} }} }} {{#if:{{{19|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{19}}} | translated = {{{translated}}} }} }} {{#if:{{{20|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{20}}} | translated = {{{translated}}} }} }} {{#if:{{{21|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{21}}} | translated = {{{translated}}} }} }}</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Translation&diff=6724Template:Translation2008-06-07T07:00:34Z<p>Dupuy: pass translated language to {{{PAGENAME}}}/translations "template"</p>
<hr />
<div><div style="border-top:1px solid #888888; border-bottom:1px solid #888888; margin:0px;"><br />
{| width="100%" cellpadding="0" cellspacing="0" style="background-color:#d0e6f9; color:grey"<br />
|-<br />
| <!-- width=75% --> align=left | &nbsp;&nbsp;<font size="1">{{:Template:Translation/translation of/lang-{{{lang}}}}} '''[[{{{source}}}|{{{source_display|{{{source}}}}}}]]'''</font><br />
| <!-- width=25% --> align=right | <font size="1">'''<span class="plainlinks">[{{fullurl:{{{source}}}|oldid={{{version}}}}} {{{version_display|{{:Template:Translation/original/lang-{{{lang}}}}}}}}]</span>'''</font>&nbsp;&nbsp;<br />
|-<br />
| align=left | &nbsp;&nbsp;{{:{{{source}}}/translations|translated={{{lang}}}}} <small class="plainlinks"> &nbsp; [{{fullurl:{{{source}}}/translations|action=edit}} +/-] </small><br />
| align=right | <font size="1">'''<span class="plainlinks">[{{fullurl:{{{source}}}|diff=current&amp;oldid={{{version}}}}} {{{diff_display|{{:Template:Translation/changes/lang-{{{lang}}}}}}}}]</span>'''</font>&nbsp;&nbsp;<br />
|-<br />
|}<br />
</div><includeonly>{{#ifeq: {{{status|xx}}} | {{translation/wanted/lang-{{{lang}}}}} | {{Translation/no translation/lang-{{{lang}}} | source = {{{source}}} }} [[Category:{{#ifexist:Template:Translation/wanted/lang-{{{lang}}}|{{translation/wanted/lang-{{{lang}}}}}|Translations wanted/lang-{{{lang}}} }}]] {{ {{#if:{{NAMESPACE}}||:}}{{{source}}} }} | {{#ifeq:{{{status|}}} | {{translation/incomplete/lang-{{{lang}}}}} | {{#ifexist:Template:translation/translation-incomplete/lang-{{{lang}}}|{{translation/translation-incomplete/lang-{{{lang}}}}}|{{translation/translation-incomplete/lang-en}} }}[[Category:Ongoing translations/lang-{{{lang}}}]] | [[Category:Translations lang-{{{lang}}}]]}} }}</includeonly><noinclude><br />
This template (in conjunction with [[Template:Translations]]&mdash;note the plural&mdash;and the <tt>source/translations</tt> page) are used to better keep track of the [[:Category:Translated Pages]] and the [[translating]] effort to lower the language barrier of the project.<font size="-1"><br />
{| align="right" style="color:white;"<br />
|-<br />
| style="background:#0093d0;" | raw || style="background:#76aac4;" | light || style="background:#3b9fca;" | mid<br />
|-<br />
| style="background:#76aac4;" | #76aac4 || style="background:#3b9fca;" | #3b9fca || style="background:#0093d0;" | #0093d0<br />
|- style="color:black;"<br />
| style="background:#3b9fca;" | #3b9fca || style="background:#0093d0;" | #0093d0 || style="background:#76aac4;" | #76aac4<br />
|}</font><br />
<br />
NOTE: The (blue) color scheme is based on the 'arrow' used for the ''Community'' in the [http://www.laptop.org laptop.org] site. A sample of colors used or thought about can be seen on the right, with further explorations found in the [[Sandbox#Translation & multilingual boxes|Sandbox]]. Comments about them are welcome.<br />
<br />
== Usage ==<br />
<br />
<nowiki>{{</nowiki> Translation<br />
| lang = &lt;-- 2/3 character language-code of the translation&mdash;ie: <tt>en, es, ...</tt> --&gt;<br />
| source = &lt;-- Source page name&mdash;ie: "The OLPC Wiki" (sans quotes) --&gt;<br />
| version = &lt;-- Version ID# of the edition being translated or last updated --&gt;<br />
| ''source_display'' = &lt;-- OPTIONAL - display string to the source link above<br />
default = value of ''source'' --&gt;<br />
| ''version_display'' = &lt;-- OPTIONAL - display string for the translated ''version'' link<br />
default = "original" --&gt;<br />
| ''diff_display'' = &lt;-- OPTIONAL - display string for the ''differences'' to current link<br />
default = "diff" --&gt;<br />
<nowiki>}}</nowiki><br />
<br />
; NOTE : the ''version'' parameter is the number displayed in the ''source'' page in the <tt>[ID# xxxxx]</tt> of the language-navigation blue bar. Keeping this number updated to the LAST version you 'translated' or 'updated' will ease updating the page when following the <tt>diff</tt> link in your page, as it will show those changes in the original from your last update.<br />
<br />
== Samples ==<br />
<br />
<nowiki>{{</nowiki> Translation | lang = es | source = The OLPC Wiki | version = 30534 <nowiki>}}</nowiki><br />
{{ Translation | lang = es | source = The OLPC Wiki | version = 30534 }}<br />
<nowiki>{{</nowiki> Translation | lang = es | source = The OLPC Wiki | version = 30534 <br />
| source_display = original <br />
| version_display = versión traducida <br />
| diff_display = últimos cambios <nowiki>}}</nowiki><br />
{{ Translation | lang = es | source = The OLPC Wiki | version = 30534 <br />
| source_display = original | version_display = versión traducida | diff_display = últimos cambios }}<br />
<br />
[[Category:Language support]]<br />
[[Category:Languages (international)]]<br />
[[Category:Template]]<br />
</noinclude></div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Developers&diff=18073Template:Developers2008-06-06T17:57:24Z<p>Dupuy: drop leading line-break</p>
<hr />
<div><noinclude>{{Translations}}</noinclude><br />
<div style="background:#BB0077; color:white;">&nbsp;&nbsp;{{#ifexist:Template:Developers/{{{trans|{{#titleparts:{{PAGENAME}}|1|2}} }}}<br />
|{{Template:Developers/{{{trans|{{#titleparts:{{PAGENAME}}|1|2}} }}} }}|For Developers}}</div><br />
[[Category:Developers]]</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Developers&diff=18072Template:Developers2008-06-06T17:56:27Z<p>Dupuy: autodetect language (or use trans=lang-xx) and use translated text if present</p>
<hr />
<div><noinclude>{{Translations}}</noinclude><br />
<div style="background:#BB0077; color:white;">&nbsp;&nbsp;{{#ifexist:Template:Developers/{{{trans|{{#titleparts:{{PAGENAME}}|1|2}} }}}|<br />
{{Template:Developers/{{{trans|{{#titleparts:{{PAGENAME}}|1|2}} }}} }}|For Developers}}</div><br />
[[Category:Developers]]</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Development_Team/Manual/lang-ko&diff=5358Development Team/Manual/lang-ko2008-06-06T17:49:46Z<p>Dupuy: testing updated Template:Developers with autodetecting localization</p>
<hr />
<div>{{Translation | lang = ko | source = Developers manual | version = 93961}}<br />
{{Developers}}<br />
<br />
<div style="margin: 20; padding-left: 30; padding: 10; border: black thin solid; background-color: #e0ffe0">XO용 활동에 대한 작업과 다른 OLPC용 코드에 대한 빠른 소개입니다. 자유롭게 설명서를 추가하고 갱신하십시오. 이것은 완성품이 아닙니다.</div><br />
<br />
이 설명서는 현재의 프로젝트에 참여하거나 또는 여러분 자신의 프로젝트를 새로 시작하는데 필요한 답변들을 제공하려고 합니다. 비록 이것은 주로 소프트웨어 개발 측면에 중점을 두고 있지만, OLPC는 아울러 [[Participate|다른 분야의 참가]]를 이끌어내는 것에도 매우 관심이 있습니다.<br />
<br />
== 개요 ==<br />
{{anchor|Overview}}<br />
* [[Developers/Setup|개발자/구축]]<br />
** 어떠한 접근법이 가장 적합할 것인지에 관한 토론과 아울러 [[Sugar|슈가]] 개발 환경의 구축 방법을 서술합니다.<br />
* [[Developers/Stack|개발자/스택]]<br />
** 프로그래밍 환경을 형성하기 위하 결합된 하드웨어, 운영체제, 서비스, 라이브러리 및 활동의 조합인 OLPC [[Sugar|슈가]] 환경의 "운영 스택"을 기술합니다.<br />
* [[Developers/Issues|개발자/쟁점]]<br />
** OLPC 프로젝트에 종사하기 위하여 요구되는, 특히 대상 하드웨어 및 개발 환경에서 도출되는 특별한 고려 사항들을 기술합니다.<br />
* [[Developers/Projects|개발자/프로젝트]]<br />
** 이미 존재하거나 혹은 새로 시작할 특정 프로젝트를 선택하는 방법과 선택 후에 프로젝트 종사를 시작하는 방법을 제안합니다.<br />
* [[Developers/Communication|개발자/의사소통]]<br />
** 문제 발생시 도움을 얻는 방법과 프로젝트별 의사소통 통로를 구축하는 방법을 비롯하여 프로젝트에서 사용되는 다양한 지원 및 의사소통 통로를 설명합니다.<br />
* [[Developers/Documentation|개발자/문서자료]]<br />
** 프로젝트에서 사용할 수 있는 문서자료의 다양한 출처를 수집합니다. 코드의 문서화가 더 잘 되도록 돕는 것은 언제나 환영되는 공헌입니다.<br />
* [[Developers/FAQ|개발자/FAQ]]<br />
** 개발자가 슈가 플랫폼에서 작업할 때 생기는 공통적인 물음에 대한 답변을 수집하여 회답합니다.<br />
<br />
== 배포 일정 ==<br />
{{anchor|Release Schedule}}<br />
2008년 1사분기 동안은 매달 업데이트하는 것으로 예정되어 있습니다. 그 다음에는 석달 간격 업데이트 주기가 적용되고, 최종적으로는 여섯달의 업데이트 주기가 적용될 것입니다. 또한 시간이 허용될 때, 각 활동 개발자들이 각자의 개발 주기를 유지할 수 있는 작성 환경으로 옮겨갈 것입니다.<br />
<br />
== 관련 문서와 설명서 ==<br />
{{anchor|Related docs and manuals}}<br />
* [[Simplified users guide|간이 사용자 설명서]]<br />
* [https://www6.software.ibm.com/developerworks/education/l-sugarpy/l-sugarpy-pdf.pdf OLPC 노트북용 응용프로그램 개발] (IBM의 Tim Jones)<br />
<br />
<br />
[[Category:Developers/lang-ko]]<br />
[[Category:Software development/lang-ko]]</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Development_Team/Manual/translations&diff=5438Development Team/Manual/translations2008-06-06T17:39:03Z<p>Dupuy: japanese translation was never started, omitting</p>
<hr />
<div>{{Translationlist | ko | origlang=en }}</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Development_Team/Manual/translations&diff=5437Development Team/Manual/translations2008-06-06T17:37:19Z<p>Dupuy: Use Template:translationlist</p>
<hr />
<div>{{Translationlist | ja | ko | origlang=en }}</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Human_Interface_Guidelines/translations&diff=16658Human Interface Guidelines/translations2008-04-03T18:24:54Z<p>Dupuy: Use Template:translationlist</p>
<hr />
<div>{{translationlist | es | ja | ko | ne | pt | origlang=en | source=OLPC Human Interface Guidelines}}</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Translationlist&diff=16309Template:Translationlist2008-04-03T17:42:57Z<p>Dupuy: use source parameter to deal with relocated pages</p>
<hr />
<div>[[{{{source|{{#if:{{NAMESPACEE}}|{{NAMESPACEE}}:{{BASEPAGENAMEE}}|{{BASEPAGENAMEE}}}}}}}|{{langname-{{{origlang|en<br />
}}}}}]] {{#if:{{{1|}}}| {{!}} {{translationlist/item| source = {{{source|{{#if:{{NAMESPACEE}}|{{NAMESPACEE}}:{{BASEPAGENAMEE}}|{{BASEPAGENAMEE}}}}}}} | lang = {{{1}}} }} }} {{#if:{{{2|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{2}}} }} }} {{#if:{{{3|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{3}}} }} }} {{#if:{{{4|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{4}}} }} }} {{#if:{{{5|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{5}}} }} }} {{#if:{{{6|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{6}}} }} }} {{#if:{{{7|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{7}}} }} }} {{#if:{{{8|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{8}}} }} }} {{#if:{{{9|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{9}}} }} }} {{#if:{{{10|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{10}}} }} }} {{#if:{{{11|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{11}}} }} }} {{#if:{{{12|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{12}}} }} }} {{#if:{{{13|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{13}}} }} }} {{#if:{{{14|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{14}}} }} }} {{#if:{{{15|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{15}}} }} }} {{#if:{{{16|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{16}}} }} }} {{#if:{{{17|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{17}}} }} }} {{#if:{{{18|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{18}}} }} }} {{#if:{{{19|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{19}}} }} }} {{#if:{{{20|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{20}}} }} }} {{#if:{{{21|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{{source|{{NAMESPACEE}}:{{BASEPAGENAMEE}}}}} | lang = {{{21}}} }} }}</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Translationlist&diff=16308Template:Translationlist2008-04-03T17:38:31Z<p>Dupuy: </p>
<hr />
<div>[[{{{source|{{#if:{{NAMESPACEE}}|{{NAMESPACEE}}:{{BASEPAGENAMEE}}|{{BASEPAGENAMEE}}}}}}}|{{langname-{{{origlang|en<br />
}}}}}]] {{#if:{{{1|}}}| {{!}} {{translationlist/item| source = {{#if:{{NAMESPACEE}}|{{NAMESPACEE}}:{{BASEPAGENAMEE}}|{{BASEPAGENAMEE}}}} | lang = {{{1}}} }} }} {{#if:{{{2|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{2}}} }} }} {{#if:{{{3|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{3}}} }} }} {{#if:{{{4|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{4}}} }} }} {{#if:{{{5|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{5}}} }} }} {{#if:{{{6|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{6}}} }} }} {{#if:{{{7|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{7}}} }} }} {{#if:{{{8|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{8}}} }} }} {{#if:{{{9|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{9}}} }} }} {{#if:{{{10|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{10}}} }} }} {{#if:{{{11|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{11}}} }} }} {{#if:{{{12|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{12}}} }} }} {{#if:{{{13|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{13}}} }} }} {{#if:{{{14|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{14}}} }} }} {{#if:{{{15|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{15}}} }} }} {{#if:{{{16|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{16}}} }} }} {{#if:{{{17|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{17}}} }} }} {{#if:{{{18|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{18}}} }} }} {{#if:{{{19|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{19}}} }} }} {{#if:{{{20|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{20}}} }} }} {{#if:{{{21|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{21}}} }} }}</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Translationlist&diff=16307Template:Translationlist2008-04-03T17:37:38Z<p>Dupuy: </p>
<hr />
<div>[[{{{source|{{#if:{{NAMESPACEE}}|{{NAMESPACEE}}:{{BASEPAGENAMEE}}|{{BASEPAGENAMEE}}}}|{{langname-{{{origlang|en<br />
}}}}}}}}]] {{#if:{{{1|}}}| {{!}} {{translationlist/item| source = {{#if:{{NAMESPACEE}}|{{NAMESPACEE}}:{{BASEPAGENAMEE}}|{{BASEPAGENAMEE}}}} | lang = {{{1}}} }} }} {{#if:{{{2|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{2}}} }} }} {{#if:{{{3|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{3}}} }} }} {{#if:{{{4|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{4}}} }} }} {{#if:{{{5|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{5}}} }} }} {{#if:{{{6|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{6}}} }} }} {{#if:{{{7|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{7}}} }} }} {{#if:{{{8|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{8}}} }} }} {{#if:{{{9|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{9}}} }} }} {{#if:{{{10|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{10}}} }} }} {{#if:{{{11|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{11}}} }} }} {{#if:{{{12|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{12}}} }} }} {{#if:{{{13|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{13}}} }} }} {{#if:{{{14|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{14}}} }} }} {{#if:{{{15|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{15}}} }} }} {{#if:{{{16|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{16}}} }} }} {{#if:{{{17|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{17}}} }} }} {{#if:{{{18|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{18}}} }} }} {{#if:{{{19|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{19}}} }} }} {{#if:{{{20|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{20}}} }} }} {{#if:{{{21|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{21}}} }} }}</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Langname-zh-TW&diff=6762Template:Langname-zh-TW2008-03-28T09:05:29Z<p>Dupuy: really "Traditional Chinese" now</p>
<hr />
<div>繁體中文</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Human_Interface_Guidelines/The_Laptop_Experience/Global_Search/translations&diff=16287Human Interface Guidelines/The Laptop Experience/Global Search/translations2008-03-28T08:57:51Z<p>Dupuy: use translationlist template</p>
<hr />
<div>{{translationlist | es | ko | origlang=en}}</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Translationlist&diff=16306Template:Translationlist2008-03-28T08:17:31Z<p>Dupuy: try to get a better line break when wrapping</p>
<hr />
<div>[[{{#if:{{NAMESPACEE}}|{{NAMESPACEE}}:{{BASEPAGENAMEE}}|{{BASEPAGENAMEE}}}}|{{langname-{{{origlang|en<br />
}}}}}]] {{#if:{{{1|}}}| {{!}} {{translationlist/item| source = {{#if:{{NAMESPACEE}}|{{NAMESPACEE}}:{{BASEPAGENAMEE}}|{{BASEPAGENAMEE}}}} | lang = {{{1}}} }} }} {{#if:{{{2|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{2}}} }} }} {{#if:{{{3|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{3}}} }} }} {{#if:{{{4|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{4}}} }} }} {{#if:{{{5|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{5}}} }} }} {{#if:{{{6|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{6}}} }} }} {{#if:{{{7|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{7}}} }} }} {{#if:{{{8|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{8}}} }} }} {{#if:{{{9|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{9}}} }} }} {{#if:{{{10|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{10}}} }} }} {{#if:{{{11|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{11}}} }} }} {{#if:{{{12|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{12}}} }} }} {{#if:{{{13|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{13}}} }} }} {{#if:{{{14|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{14}}} }} }} {{#if:{{{15|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{15}}} }} }} {{#if:{{{16|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{16}}} }} }} {{#if:{{{17|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{17}}} }} }} {{#if:{{{18|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{18}}} }} }} {{#if:{{{19|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{19}}} }} }} {{#if:{{{20|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{20}}} }} }} {{#if:{{{21|}}}|<br />
{{!}}&nbsp;{{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{21}}} }} }}</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Translationlist&diff=16305Template:Translationlist2008-03-28T08:07:40Z<p>Dupuy: there are already 20 different language versions of The OLPC Wiki page</p>
<hr />
<div>[[{{#if:{{NAMESPACEE}}|{{NAMESPACEE}}:{{BASEPAGENAMEE}}|{{BASEPAGENAMEE}}}}|{{langname-{{{origlang|en<br />
}}}}}]] {{#if:{{{1|}}}| {{!}} {{translationlist/item| source = {{#if:{{NAMESPACEE}}|{{NAMESPACEE}}:{{BASEPAGENAMEE}}|{{BASEPAGENAMEE}}}} | lang = {{{1}}} }} }} {{#if:{{{2|}}}| {{!}} {{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{2}}} }} }} {{#if:{{{3|}}}| {{!}} {{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{3}}} }} }} {{#if:{{{4|}}}| {{!}} {{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{4}}} }} }} {{#if:{{{5|}}}| {{!}} {{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{5}}} }} }} {{#if:{{{6|}}}| {{!}} {{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{6}}} }} }} {{#if:{{{7|}}}| {{!}} {{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{7}}} }} }} {{#if:{{{8|}}}| {{!}} {{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{8}}} }} }} {{#if:{{{9|}}}| {{!}} {{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{9}}} }} }} {{#if:{{{10|}}}| {{!}} {{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{10}}} }} }} {{#if:{{{11|}}}| {{!}} {{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{11}}} }} }} {{#if:{{{12|}}}| {{!}} {{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{12}}} }} }} {{#if:{{{13|}}}| {{!}} {{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{13}}} }} }} {{#if:{{{14|}}}| {{!}} {{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{14}}} }} }} {{#if:{{{15|}}}| {{!}} {{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{15}}} }} }} {{#if:{{{16|}}}| {{!}} {{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{16}}} }} }} {{#if:{{{17|}}}| {{!}} {{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{17}}} }} }} {{#if:{{{18|}}}| {{!}} {{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{18}}} }} }} {{#if:{{{19|}}}| {{!}} {{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{19}}} }} }} {{#if:{{{20|}}}| {{!}} {{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{20}}} }} }} {{#if:{{{21|}}}| {{!}} {{translationlist/item| source = {{NAMESPACEE}}:{{BASEPAGENAMEE}} | lang = {{{21}}} }} }}</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Langname-tr&diff=6758Template:Langname-tr2008-03-28T07:55:43Z<p>Dupuy: New page: türkçe</p>
<hr />
<div>türkçe</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Langname-rw&diff=6756Template:Langname-rw2008-03-28T07:34:42Z<p>Dupuy: New page: kinyarwanda</p>
<hr />
<div>kinyarwanda</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Langname-ro&diff=6752Template:Langname-ro2008-03-28T07:34:22Z<p>Dupuy: New page: română</p>
<hr />
<div>română</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Langname-ar&diff=6728Template:Langname-ar2008-03-28T07:29:28Z<p>Dupuy: move comment to discussion</p>
<hr />
<div>عربي</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Langname-ht&diff=6736Template:Langname-ht2008-03-28T07:18:11Z<p>Dupuy: note that mediawiki gets the accent wrong on kreyòl</p>
<hr />
<div>kreyòl ayisyen</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Langname-bg&diff=6730Template:Langname-bg2008-03-28T07:07:03Z<p>Dupuy: lowercase name</p>
<hr />
<div>български</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Langname-ko&diff=6742Template:Langname-ko2008-03-28T06:42:32Z<p>Dupuy: just use {{#language:ko}} - see talk</p>
<hr />
<div>{{#language:ko}}</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Langname-zh&diff=6760Template:Langname-zh2008-03-28T06:10:50Z<p>Dupuy: just use {{#language:zh}}</p>
<hr />
<div>{{#language:zh}}</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Langname-ja&diff=6740Template:Langname-ja2008-03-28T06:10:15Z<p>Dupuy: just use {{#language:ja}}</p>
<hr />
<div>{{#language:ja}}</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Langname-ne&diff=6746Template:Langname-ne2008-03-28T06:09:34Z<p>Dupuy: just use {{#language:ne}}</p>
<hr />
<div>{{#language:ne}}</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Translations/instructions&diff=15831Template:Translations/instructions2008-03-28T05:12:23Z<p>Dupuy: remove es, ko from instructions</p>
<hr />
<div><small>Please copy/paste "<nowiki>{{</nowiki>Translationlist {{!}} <i>xx</i> {{!}} origlang=en<nowiki>}}</nowiki>" (where ''xx'' is [[ISO 639]] language code for your translation) to {{{{NAMESPACE}}:{{PAGENAME}}/translations}}</small></div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Translationlist/item&diff=5714Template:Translationlist/item2008-03-28T03:22:46Z<p>Dupuy: use {{langname-{{{lang}}}}} in preference to {{#language:{{{lang}}}}} if it exists</p>
<hr />
<div>{{#ifexist:{{{source}}}/lang-{{{lang}}}|<br />
[[{{{source}}}/lang-{{{lang}}}{{!}}{{#ifexist:Template:langname-{{{lang}}}|<br />
{{langname-{{{lang}}}}}|{{#language:{{{lang}}}}}}}]]|<br />
<small>{{ Translationlist/item/instructions|lang={{{lang}}}|source={{{source}}} }}</small><br />
}}</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Translationlist/item&diff=5713Template:Translationlist/item2008-03-28T03:21:14Z<p>Dupuy: use Template:langname-{{{lang}}} in preference to {{#language:{{{lang}}}}} if it exists</p>
<hr />
<div>{{#ifexist:{{{source}}}/lang-{{{lang}}}|<br />
[[{{{source}}}/lang-{{{lang}}}{{!}}{{#ifexist:Template:langname-{{{lang}}}|<br />
Template:langname-{{{lang}}}|{{#language:{{{lang}}}}}}}]]|<br />
<small>{{ Translationlist/item/instructions|lang={{{lang}}}|source={{{source}}} }}</small><br />
}}</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Design_Team/Designs/Journal&diff=19431Design Team/Designs/Journal2008-03-01T23:52:37Z<p>Dupuy: /* 03 */ typo</p>
<hr />
<div>__NOTOC__<br />
<br />
====01====<br />
back | [[#02 | next]]<br />
[[Image:Journal-01.jpeg | thumb | center | 640px | <br />
<br />
The new Journal captures a child's interactions with their laptop and with others, offering both activity- and object-centric views. The activity-centric view, shown here, provides a friendly browsable interface into the activities a child has participated in, and the actions they've taken. This makes it possible to distinguish between writing a story vs. reading one, and among objects a child creates or modifies vs. those they download, receive from a friend or copy from an external device, etc. This view also makes possible the logging of actions and events with no associated object, such as joining a group, making a friend, or changing global settings.<br />
]]<br />
<br />
<br />
====02====<br />
[[#01 | back]] | [[#03 | next]]<br />
[[Image:Journal-02.jpeg | thumb | center | 640px | <br />
<br />
Each action may result in (or take effect on) one or more objects. The child may expand each entry to see more detail about a particular action; thumbnails are offered where available to make browsing through a day's events quick and effective.<br />
]]<br />
<br />
<br />
====03====<br />
[[#02 | back]] | [[#04 | next]]<br />
[[Image:Journal-03.jpeg | thumb | center | 640px | <br />
<br />
The object-centric view, on the other hand, retains a very similar form to that of the previous Journal. It offers a structured list of all the objects stored on the system, and provides a means to sort them based on various criteria.<br />
]]<br />
<br />
====04====<br />
[[#03 | back]] | [[#05 | next]]<br />
[[Image:Journal-04.jpeg | thumb | center | 640px | <br />
<br />
The icons in both views are actionable: A single click will start or resume an object or activity, and each also has a standard palette providing a basic description and a number of actions that may be taken upon it.<br />
]]<br />
<br />
====05====<br />
[[#04 | back]] | [[#06 | next]]<br />
[[Image:Journal-05.jpeg | thumb | center | 640px | <br />
<br />
Clicking directly on the title of a given object will reveal an entry field, allowing the child to rename items without navigating to the detail view for the entry.<br />
]]<br />
<br />
====06====<br />
[[#05 | back]] | [[#07 | next]]<br />
[[Image:Journal-06.jpeg | thumb | center | 640px | <br />
<br />
The checkboxes to the left of each entry select objects in the list. When a selection is made, a contextual toolbar appears offering a number of actions to take upon the selected items, including copy, tag, and erase. When activated, the button above the checkbox column will reveal only the selected items, providing a clear view of the objects the child will act upon.<br />
]]<br />
<br />
====07====<br />
[[#06 | back]] | [[#08 | next]]<br />
[[Image:Journal-07.jpeg | thumb | center | 640px | <br />
<br />
The star button will filter the list of objects, showing only the child's favorites. Constricting the list in this manner can make navigation much easier when the overall number of objects in the Journal gets large.<br />
]]<br />
<br />
====08====<br />
[[#07 | back]] | [[#09 | next]]<br />
[[Image:Journal-08.jpeg | thumb | center | 640px | <br />
<br />
To further aid in scalability, the Journal has a new scrolling interaction. Smooth pixel-by-pixel scrolling will allow the child to navigate easily through several buffered pages of objects before and after their current location in time. When they scroll beyond the buffer, an overlay will appear to indicate their location in time as they move the scrollbar. Once they reach a point they are interested in, the buffer will be refilled at the new location.<br />
]]<br />
<br />
====09====<br />
[[#08 | back]] | [[#10 | next]]<br />
[[Image:Journal-09.jpeg | thumb | center | 640px | <br />
<br />
The palette for the object-centric section offers two views: list and thumbnail.<br />
]]<br />
<br />
====10====<br />
[[#09 | back]] | [[#11 | next]]<br />
[[Image:Journal-10.jpeg | thumb | center | 640px | <br />
<br />
The thumbnail view makes searching through images and videos much more engaging and efficient. Over time, many activities will take advantage of the thumbnail capability to provide visual browsing for additional types of objects.<br />
]]<br />
<br />
====11====<br />
[[#10 | back]] | [[#12 | next]]<br />
[[Image:Journal-11.jpeg | thumb | center | 640px | <br />
<br />
When a search or filter turns up no results this will be clearly indicated. A button will allow the child to clear their search and try again.<br />
]]<br />
<br />
====12====<br />
[[#11 | back]] | next<br />
[[Image:Journal-12.jpeg | thumb | center | 640px | <br />
<br />
By clicking on a detail button from any view of the Journal the child will enter a page containing a larger thumbnail, object details such as size and format, and fields for entering a description and tags. By selecting the date popup for a given object, the child can navigate to its previous versions.<br />
]]<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
&nbsp;</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Translation/original/lang-ko&diff=15523Template:Translation/original/lang-ko2008-02-29T06:39:31Z<p>Dupuy: google is insane, reverting (changed translation of 'Translation of' instead</p>
<hr />
<div>원문</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Translation/translation_of/lang-ko&diff=15527Template:Translation/translation of/lang-ko2008-02-29T06:37:47Z<p>Dupuy: This is "source translation" or "translation origin" which works better with English page name following</p>
<hr />
<div>번역근원</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Template:Translation/original/lang-ko&diff=15522Template:Translation/original/lang-ko2008-02-29T06:27:01Z<p>Dupuy: 원문 is "All rights reserved" - not sure why reverted to this incorrect text, using Google</p>
<hr />
<div>원래</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Translation_Team/ISO_639&diff=5755Translation Team/ISO 6392008-02-29T05:16:56Z<p>Dupuy: </p>
<hr />
<div>{{stub}}<br />
<br />
The subvariant used by OLPC is '''[http://en.wikipedia.org/wiki/ISO_639-1 ISO 639-1]''' (See [http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes List of ISO 639-1 codes]).<br />
<br />
{| border="1"<br />
|- style="background:lightgray"<br />
! style="background:green" | 639-1 !! 639-2 !! 639-3 !! Language !! !! Native name !! Comments<br />
|-<br />
| style="background:lightgreen" | am || amh || amh || [[Amharic language|Amharic]] || [http://en.wikipedia.org/wiki/Amharic_language W] || {{#language:am}} || [[OLPC Ethiopia|Ethiopia]]<br />
|-<br />
| style="background:lightgreen" | ar || ara || ara + 30 || [[Arabic language|Arabic]] || [http://en.wikipedia.org/wiki/Arabic_language W] || {{#language:ar}} || Standard Arabic is [arb]&mdash;[[OLPC Libya|Libya]]<br />
|-<br />
| style="background:lightgreen" | en || eng || eng || [[English language|English]] || [http://en.wikipedia.org/wiki/English_language W] || English || [[OLPC Nigeria|Nigeria]], [[OLPC Rwanda|Rwanda]] & [[OLPC USA|USA]]<br />
|-<br />
| style="background:lightgreen" | es || spa || spa || [[Spanish language|Spanish]] || [http://en.wikipedia.org/wiki/Spanish_language W] || español; castellano || [[OLPC Argentina|Argentina]], [[OLPC Peru|Perú]] & [[OLPC Uruguay|Uruguay]]<br />
|-<br />
| | ''fa'' || ''per/fas'' || prs || [[Dari language|Dari (Persian)]] || [http://en.wikipedia.org/wiki/Dari_%28Persian%29 W] || دری, || Dari only has 639-3 code&mdash;[[OLPC Afghanistan|Afghanistan]]<br />
|-<br />
| style="background:lightgreen" | fr || fre/fra || fra || [[French language|French]] || [http://en.wikipedia.org/wiki/French_language W] || français; langue française || [[OLPC Haiti|Haiti]] & [[OLPC Rwanda|Rwanda]]<br />
|-<br />
| style="background:lightgreen" | ha || hau || hau || [[Hausa language|Hausa]] || [http://en.wikipedia.org/wiki/Hausa_language W] || {{#language:ha}} || [[OLPC Nigeria|Nigeria]]<br />
|-<br />
| | ht || hat || hat || [[Haitian Creole language|Haitian Creole]] || [http://en.wikipedia.org/wiki/Haitian_Creole_language W] || {{#language:ht}} || [[OLPC Haiti|Haiti]]<br />
|-<br />
| style="background:lightgreen" | ig || ibo || ibo || [[Igbo language|Igbo]] || [http://en.wikipedia.org/wiki/Igbo_language W] || Igbo || [[OLPC Nigeria|Nigeria]]<br />
|-<br />
| | kh || khm || khm + 1 || [[Khmer language|Khmer]] || [http://en.wikipedia.org/wiki/Khmer_language W] || ភាសាខ្មែរ || [[OLPC Cambodia|Cambodia]]<br />
|-<br />
| | mn || mon || mon+2 || [[Mongolian language|Mongolian]] || [http://en.wikipedia.org/wiki/Mongolian_language W] || {{#language:mn}} || [[OLPC Mongolia|Mongolia]]<br />
|-<br />
| style="background:lightgreen" | ne || nep || nep || [[Nepali language|Nepali]] || [http://en.wikipedia.org/wiki/Nepali_language W] || {{#language:ne}} || [[OLPC Nepal|Nepal]]<br />
|-<br />
| | ps || pus || pus + 3 || [[Pashto language|Pashto]] || [http://en.wikipedia.org/wiki/Pashto_language W] || {{#language:ps}} || [[OLPC Afghanistan|Afghanistan]]<br />
|-<br />
| style="background:lightgreen" | pt || por || por || [[Portuguese language|Portuguese]] || [http://en.wikipedia.org/wiki/Portuguese_language W] || Português || [[OLPC Brazil|Brasil]]<br />
|-<br />
| style="background:lightgreen" | ro || rum/ron || ron || [[Romanian language|Romanian]] || [http://en.wikipedia.org/wiki/Romanian_language W] || română || [[OLPC Romania|Romania]]<br />
|-<br />
| style="background:lightgreen" | ru || rus || rus || [[Russian language|Russian]] || [http://en.wikipedia.org/wiki/Russian_language W] || русский язык || [[OLPC Russia|Russia]]<br />
|-<br />
| style="background:lightgreen" | rw || kin || kin || [[Kinyarwanda language|Kinyarwanda]] || [http://en.wikipedia.org/wiki/Kinyarwanda_language W] || Kinyarwanda || [[OLPC Rwanda|Rwanda]]<br />
|-<br />
| style="background:lightgreen" | th || tha || tha || [[Thai language|Thai]] || [http://en.wikipedia.org/wiki/Thai_language W] || ไทย || [[OLPC Thailand|Thailand]]<br />
|-<br />
| style="background:lightgreen" | ur || urd || urd || [[Urdu language|Urdu]] || [http://en.wikipedia.org/wiki/Urdu W] || {{#language:ur}} || [[OLPC Pakistan|Pakistan]]<br />
|-<br />
| style="background:lightgreen" | yo || yor || yor || [[Yoruba language|Yoruba]] || [http://en.wikipedia.org/wiki/Yoruba_language W] || Yorùbá || [[OLPC Nigeria|Nigeria]]<br />
|- style="background:lightgray"<br />
| colspan=7 style="font-size:80%" | Most relevant [http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1 codes] for the '''current green countries:'''<br>{{Status green countries}}<br>and other '''[[G1G1]] targets:''' [[OLPC Afghanistan|Afghanistan]], [[OLPC Cambodia|Cambodia]], [[OLPC Haiti|Haiti]], [[OLPC Mongolia|Mongolia]], <br />
|}<br />
<br />
== ISO 639 variations ==<br />
<br />
[[ISO-639]] is a standard for specifying languages by the use of a code. Several formats exist:<br />
* '''[http://en.wikipedia.org/wiki/ISO_639-1 ISO 639-1]'''&mdash;2002 Codes for the representation of names of languages -- Part 1: Alpha-2 code '''[http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes List of ISO 639-1 codes]'''<br />
* [http://en.wikipedia.org/wiki/ISO_639-2 ISO 639-2]&mdash;1998 Codes for the representation of names of languages -- Part 2: Alpha-3 code [http://en.wikipedia.org/wiki/List_of_ISO_639-2_codes List of ISO 639-2 codes]<br />
* [http://en.wikipedia.org/wiki/ISO_639-3 ISO 639-3]&mdash;2007 Codes for the representation of names of languages -- Part 3: Alpha-3 code for comprehensive coverage of languages [http://en.wikipedia.org/wiki/List_of_ISO_639-3_codes List of ISO 639-3 codes]<br />
* [http://en.wikipedia.org/wiki/ISO_639-4 ISO/CD 639-4]&mdash;2007? Codes for the representation of names of languages -- Part 4: Implementation guidelines and general principles for language coding<br />
* [http://en.wikipedia.org/wiki/ISO_639-5 ISO/DIS 639-5]&mdash;2007? Codes for the representation of names of languages -- Part 5: Alpha-3 code for language families and groups<br />
* ISO/CD 639-6&mdash;2007? Codes for the representation of names of languages -- Part 6: Alpha-4 representation for comprehensive coverage of language variation<br />
<br />
[[Category:Language support]]<br />
[[Category:Languages (international)]]<br />
[[Category:Localization]]</div>Dupuyhttps://wiki.sugarlabs.org/index.php?title=Translation_Team/ISO_639&diff=5754Translation Team/ISO 6392008-02-27T22:38:38Z<p>Dupuy: add G1G1 languages</p>
<hr />
<div>{{stub}}<br />
<br />
The subvariant used by OLPC is '''[http://en.wikipedia.org/wiki/ISO_639-1 ISO 639-1]''' (See [http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes List of ISO 639-1 codes]).<br />
<br />
{| border="1"<br />
|- style="background:lightgray"<br />
! style="background:green" | 639-1 !! 639-2 !! 639-3 !! Language !! !! Native name !! Comments<br />
|-<br />
| style="background:lightgreen" | am || amh || amh || [[Amharic language|Amharic]] || [http://en.wikipedia.org/wiki/Amharic_language W] || {{#language:am}} || [[OLPC Ethiopia|Ethiopia]]<br />
|-<br />
| style="background:lightgreen" | ar || ara || ara + 30 || [[Arabic language|Arabic]] || [http://en.wikipedia.org/wiki/Arabic_language W] || {{#language:ar}} || Standard Arabic is [arb]&mdash;[[OLPC Libya|Libya]]<br />
|-<br />
| style="background:lightgreen" | en || eng || eng || [[English language|English]] || [http://en.wikipedia.org/wiki/English_language W] || English || [[OLPC Nigeria|Nigeria]], [[OLPC Rwanda|Rwanda]] & [[OLPC USA|USA]]<br />
|-<br />
| style="background:lightgreen" | es || spa || spa || [[Spanish language|Spanish]] || [http://en.wikipedia.org/wiki/Spanish_language W] || español; castellano || [[OLPC Argentina|Argentina]], [[OLPC Peru|Perú]] & [[OLPC Uruguay|Uruguay]]<br />
|-<br />
| | ''fa'' || ''per/fas'' || prs || [[Dari language|Dari]] || [http://en.wikipedia.org/wiki/Dari_%28Persian%29 W] || دری, || Dari only has 639-3 code&mdash;[[OLPC Afghanistan|Afghanistan]]<br />
|-<br />
| style="background:lightgreen" | fr || fre/fra || fra || [[French language|French]] || [http://en.wikipedia.org/wiki/French_language W] || français; langue française || [[OLPC Haiti|Haiti]] & [[OLPC Rwanda|Rwanda]]<br />
|-<br />
| style="background:lightgreen" | ha || hau || hau || [[Hausa language|Hausa]] || [http://en.wikipedia.org/wiki/Hausa_language W] || {{#language:ha}} || [[OLPC Nigeria|Nigeria]]<br />
|-<br />
| | ht || hat || hat || [[Haitian Creole language|Haitian Creole]] || [http://en.wikipedia.org/wiki/Haitian_Creole_language W] || {{#language:ht}} || [[OLPC Haiti|Haiti]]<br />
|-<br />
| style="background:lightgreen" | ig || ibo || ibo || [[Igbo language|Igbo]] || [http://en.wikipedia.org/wiki/Igbo_language W] || Igbo || [[OLPC Nigeria|Nigeria]]<br />
|-<br />
| | kh || khm || khm + 1 || [[Khmer language|Khmer]] || [http://en.wikipedia.org/wiki/Khmer_language W] || ភាសាខ្មែរ || [[OLPC Cambodia|Cambodia]]<br />
|-<br />
| | mn || mon || mon+2 || [[Mongolian language|Mongolian]] || [http://en.wikipedia.org/wiki/Mongolian_language W] || {{#language:mn}} || [[OLPC Mongolia|Mongolia]]<br />
|-<br />
| style="background:lightgreen" | ne || nep || nep || [[Nepali language|Nepali]] || [http://en.wikipedia.org/wiki/Nepali_language W] || {{#language:ne}} || [[OLPC Nepal|Nepal]]<br />
|-<br />
| | ps || pus || pus + 3 || [[Pashto language|Pashto]] || [http://en.wikipedia.org/wiki/Pashto_language W] || {{#language:ps}} || [[OLPC Afghanistan|Afghanistan]]<br />
|-<br />
| style="background:lightgreen" | pt || por || por || [[Portuguese language|Portuguese]] || [http://en.wikipedia.org/wiki/Portuguese_language W] || Português || [[OLPC Brazil|Brasil]]<br />
|-<br />
| style="background:lightgreen" | ro || rum/ron || ron || [[Romanian language|Romanian]] || [http://en.wikipedia.org/wiki/Romanian_language W] || română || [[OLPC Romania|Romania]]<br />
|-<br />
| style="background:lightgreen" | ru || rus || rus || [[Russian language|Russian]] || [http://en.wikipedia.org/wiki/Russian_language W] || русский язык || [[OLPC Russia|Russia]]<br />
|-<br />
| style="background:lightgreen" | rw || kin || kin || [[Kinyarwanda language|Kinyarwanda]] || [http://en.wikipedia.org/wiki/Kinyarwanda_language W] || Kinyarwanda || [[OLPC Rwanda|Rwanda]]<br />
|-<br />
| style="background:lightgreen" | th || tha || tha || [[Thai language|Thai]] || [http://en.wikipedia.org/wiki/Thai_language W] || ไทย || [[OLPC Thailand|Thailand]]<br />
|-<br />
| style="background:lightgreen" | ur || urd || urd || [[Urdu language|Urdu]] || [http://en.wikipedia.org/wiki/Urdu W] || {{#language:ur}} || [[OLPC Pakistan|Pakistan]]<br />
|-<br />
| style="background:lightgreen" | yo || yor || yor || [[Yoruba language|Yoruba]] || [http://en.wikipedia.org/wiki/Yoruba_language W] || Yorùbá || [[OLPC Nigeria|Nigeria]]<br />
|- style="background:lightgray"<br />
| colspan=7 style="font-size:80%" | Most relevant [http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1 codes] for the '''current green countries:'''<br>{{Status green countries}}<br>and other '''[[G1G1]] targets:''' [[OLPC Afghanistan|Afghanistan]], [[OLPC Cambodia|Cambodia]], [[OLPC Haiti|Haiti]], [[OLPC Mongolia|Mongolia]], <br />
|}<br />
<br />
== ISO 639 variations ==<br />
<br />
[[ISO-639]] is a standard for specifying languages by the use of a code. Several formats exist:<br />
* '''[http://en.wikipedia.org/wiki/ISO_639-1 ISO 639-1]'''&mdash;2002 Codes for the representation of names of languages -- Part 1: Alpha-2 code '''[http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes List of ISO 639-1 codes]'''<br />
* [http://en.wikipedia.org/wiki/ISO_639-2 ISO 639-2]&mdash;1998 Codes for the representation of names of languages -- Part 2: Alpha-3 code [http://en.wikipedia.org/wiki/List_of_ISO_639-2_codes List of ISO 639-2 codes]<br />
* [http://en.wikipedia.org/wiki/ISO_639-3 ISO 639-3]&mdash;2007 Codes for the representation of names of languages -- Part 3: Alpha-3 code for comprehensive coverage of languages [http://en.wikipedia.org/wiki/List_of_ISO_639-3_codes List of ISO 639-3 codes]<br />
* [http://en.wikipedia.org/wiki/ISO_639-4 ISO/CD 639-4]&mdash;2007? Codes for the representation of names of languages -- Part 4: Implementation guidelines and general principles for language coding<br />
* [http://en.wikipedia.org/wiki/ISO_639-5 ISO/DIS 639-5]&mdash;2007? Codes for the representation of names of languages -- Part 5: Alpha-3 code for language families and groups<br />
* ISO/CD 639-6&mdash;2007? Codes for the representation of names of languages -- Part 6: Alpha-4 representation for comprehensive coverage of language variation<br />
<br />
[[Category:Language support]]<br />
[[Category:Languages (international)]]<br />
[[Category:Localization]]</div>Dupuy