1,157
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + + + − ==Hosted Projects==+ + − ++++++++++++++++++++++++ − OLPC Software project Line 15:
Line 17: + + Line 31:
Line 35: + + Line 122:
Line 128: − ++++++++++++++++++++++++ + + + + − https://wiki.mozilla.org/L10n:Home_Page + + + + + + Line 146:
Line 161: − ++++++++++++++++++++++++ + − ==Unhosted projects==+ − ++++++++++++++++++++++++ + + + + + + + + − ++++++++++++++++++++++++ − ===Audacity===+ Line 172:
Line 196: −
Translation Team/Upstream localization (view source)
Revision as of 15:01, 22 April 2011
, 15:01, 22 April 2011no edit summary
This page is under development [[User:Cjl|Cjl]] 22:44, 14 April 2011 (EDT)
This page is under development [[User:Cjl|Cjl]] 15:01, 22 April 2011 (EDT)
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.
==Hosted Projects==
These projects have formal localization projects with a hosting server and typically a language team that acts as the gatekeeper for new L10n. It is necessary to learn about their L10n process and possibly join their language team to contribute.
===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.
olpc-switch-desktop.po
olpc-switch-desktop.po
http://translate.sugarlabs.org/projects/olpc_software/
http://translate.sugarlabs.org/projects/olpc_software/
===GNOME modules===
===GNOME modules===
Recent OLPC builds are dual boot in Sugar and GNOME UIs. We inherit the GNOME L10n bits from the upstream, so in order to have a fully localized XO laptop, it is critical to make sure that the L10n of the GNOME modules we pull into our build process are complete.
Learn about the GNOME translation process
Learn about the GNOME translation process
===Tracking Tickets in Pootle===
===Tracking Tickets in Pootle===
These are specific GNOME modules tha are pulled into OLPC builds. Please work on these first when you go to work on upstream L10n. There are dummy PO files in the Pootle Upstream L10n project that are not meant to be translated literally, but instead serve the purpose of acting as :tracking tickets" to record the status of the upstream L10n effort.
====gnome-desktop====
====gnome-desktop====
http://l10n.gnome.org/module/xdg-user-dirs-gtk/
http://l10n.gnome.org/module/xdg-user-dirs-gtk/
====Scratch====
This is not hosted by GNOME, but this PO serves the same "tracking ticket" function as the others.
tracking-scratch.po
http://translate.scratch.mit.edu/projects/scratch/
===Firefox localization===
===Firefox localization===
Firefox is the default browser on the GNOME boot of an OLPC build.
Learn about the Firefox translation process
https://wiki.mozilla.org/L10n:Home_Page
Find your team
Find your team
https://wiki.mozilla.org/L10n:Localizability/Web
https://wiki.mozilla.org/L10n:Localizability/Web
==Unhosted projects==
These projects have less formal localization projects. They typically employ a general L10n mailing list (or sometimes a language team specific list) and completed PO files are posted to the lists for review and commit. In other cases, the completed PO is posted as an attachment to a ticket in their bug tracker. It is necessary to learn about their L10n process and possibly join their language team to contribute.
In some cases, we may decide to host a copy of the upstream POT file locally, but this is only for the convenience of allowing our localizers to work in a familiar tool (Pootle) and to allow us to track completion status. To get the translated PO file submitted, it is still necessary to work though the upstream's process.
===Inkscape===
===Inkscape===
Learn about the Inkscape translation process
http://wiki.inkscape.org/wiki/index.php/Translation_information
http://wiki.inkscape.org/wiki/index.php/Translation_information
http://wiki.inkscape.org/wiki/index.php/Translation_information#User_interface
http://wiki.inkscape.org/wiki/index.php/Translation_information#User_interface
Inkscape's translator mailing list
https://lists.sourceforge.net/lists/listinfo/inkscape-translator
Location of the committed PO files in Inkscape's bazaar repository web interface.
http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head:/po/
http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head:/po/
===Audacity===
Learn about the Audacity translation process
http://audacity.sourceforge.net/community/translation
http://audacity.sourceforge.net/community/translation
Post PO files to
Post PO files to
http://sourceforge.net/mailarchive/forum.php?forum_name=audacity-translation
http://sourceforge.net/mailarchive/forum.php?forum_name=audacity-translation
Subscribe to the audacity-translation mailing list, zip up the translated .po file(s) and attach to a message to the list. A member of Audacity Team will then commit the file to SVN for future Audacity release (or for the web site) and will send a message back to say this has been done.
Subscribe to the audacity-translation mailing list, zip up the translated .po file(s) and attach to a message to the list. A member of Audacity Team will then commit the file to SVN for future Audacity release (or for the web site) and will send a message back to say this has been done.