1,157
edits
Changes
Translation Team/Upstream localization (view source)
Revision as of 14:33, 1 August 2011
, 14:33, 1 August 2011→Scratch
It is important to understand that the Sugar user Interface is only part of what a user sees when using Sugar (say on an XO laptop or SOAS). It is important that a large number of upstream projects get localized to have a fully translated user experience. As one small example, when opening a PDF in Browse (web-activity) theree is a string that appears "Loading..." that comes from the evince document viewer. The only way to make that string appear in your native language is to contribute to the localization of evince in the upstream.
It is important to understand that the Sugar user Interface is only part of what a user sees when using Sugar (say on an XO laptop or SOAS). It is important that a large number of upstream projects get localized to have a fully translated user experience. As one small example, when opening a PDF in Browse (web-activity) there is a string that appears "Loading..." that comes from the evince document viewer. The only way to make that string appear in your native language is to contribute to the localization of evince in the upstream.
Sugar Labs and OLPC benefit greatly from work done upstream (Fedora, GNOME, etc.). These upstream projects typically host their own localization and in order for us to get the greatest benefit from these projects, it is important that we check on and contribute to their localization of the modules and languages of interest to Sugar Labs / OLPC. The benefits of making these upstream contributions flow directly back to Sugar Labs / OLPC as we get our L10n bits for these packages from the upstream.
Sugar Labs and OLPC benefit greatly from work done upstream (Fedora, GNOME, etc.). These upstream projects typically host their own localization and in order for us to get the greatest benefit from these projects, it is important that we check on and contribute to their localization of the modules and languages of interest to Sugar Labs / OLPC. The benefits of making these upstream contributions flow directly back to Sugar Labs / OLPC as we get our L10n bits for these packages from the upstream.
===OLPC Software project===
===OLPC Software project===
While this is hosted locally it is listed on this page again to emphasis that these are the strings involved in switching from the Sugar UI to the GNOME UI in recent OLPC builds.
While this is hosted locally it is listed on this page again to emphasize that these are the strings involved in switching from the Sugar UI to the GNOME UI in recent OLPC builds.
olpc-switch-desktop.po
olpc-switch-desktop.po
http://translationproject.org/html/welcome.html
http://translationproject.org/html/welcome.html
===Scratch===
===Scratch===
This is not hosted by GNOME, but this PO serves the same "tracking ticket" function as the others.
This is hosted by the Scratch team on their own Pootle server, but this PO serves the same "tracking ticket" function as the others.
tracking-scratch.po
tracking-scratch.po
http://gitorious.org/batti/batti/trees/master/po
http://gitorious.org/batti/batti/trees/master/po
+++++++++++++++++++++++
+++++++++++++++++++++++