Translation Team/Upstream localization

This page is under development 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 http://translate.sugarlabs.org/projects/olpc_software/

+++++++++++++++++++++++

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 http://live.gnome.org/TranslationProject/

Create an account on the GNOME "Damned Lies" server and login

http://l10n.gnome.org/login/

Look to see if there is already a Translation Team for your language.

GNOME Translation Teams http://l10n.gnome.org/teams/

+++++++++++++++++++++++

Tracking Tickets in Pootle

These are specific GNOME modules that 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

tracking-gnome-desktop.pot

http://l10n.gnome.org/module/gnome-desktop/

gnome-panel

tracking-gnome-panel.pot

http://l10n.gnome.org/module/gnome-panel/

gnome-session

tracking-gnome-session.pot

http://l10n.gnome.org/module/gnome-session/

gnome-terminal

tracking-gnome-terminal.pot

http://l10n.gnome.org/module/gnome-terminal/

libbonobo

tracking-libbonobo.pot

http://l10n.gnome.org/module/libbonobo/

libbonoboui

tracking-libbonoboui.pot

http://l10n.gnome.org/module/libbonoboui/

libgdata

tracking-libgdata.pot

http://l10n.gnome.org/module/libgdata/

libgnome

tracking-libgnome.pot

http://l10n.gnome.org/module/libgnome/

libgnome-keyring

tracking-libgnome-keyring.pot

http://l10n.gnome.org/module/libgnome-keyring/

libgnomeui

tracking-libgnomeui.pot

http://l10n.gnome.org/module/libgnomeui/

libgsf

tracking-libgsf.pot

http://l10n.gnome.org/module/libgsf/

libwnck

tracking-libwnck.pot

http://l10n.gnome.org/module/libwnck/

metacity

tracking-metacity.pot

http://l10n.gnome.org/module/metacity/

nautilus

tracking-nautilus.pot

http://l10n.gnome.org/module/nautilus/

PolicyKit-gnome

tracking-PolicyKit-gnome.pot

http://l10n.gnome.org/module/PolicyKit-gnome/

notification-daemon

tracking-notification-daemon.pot

http://l10n.gnome.org/module/notification-daemon/

empathy

tracking-empathy.pot

http://l10n.gnome.org/module/empathy/

gnumeric

tracking-gnumeric.pot

http://l10n.gnome.org/module/gnumeric/

evince

tracking-evince.pot

http://l10n.gnome.org/module/evince/

eog

tracking-eog.pot

http://l10n.gnome.org/module/eog/

gimp

tracking-gimp.pot

http://l10n.gnome.org/module/gimp/

totem

tracking-totem.pot

http://l10n.gnome.org/module/totem/

totem-pl-parser

tracking-totem-pl-parser.pot

http://l10n.gnome.org/module/totem-pl-parser/

file-roller

tracking-file-roller.pot

http://l10n.gnome.org/module/file-roller/

gedit

tracking-gedit.pot

http://l10n.gnome.org/module/gedit/

NetworkManager-gnome

tracking-NetworkManager-gnome.pot

http://l10n.gnome.org/module/NetworkManager/

xdg-user-dirs-gtk

tracking-xdg-user-dirs-gtk.pot

http://l10n.gnome.org/module/xdg-user-dirs-gtk/

zenity

tracking-zenity.pot

http://l10n.gnome.org/module/zenity/

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 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

https://wiki.mozilla.org/Category:L10n_Teams

Verbatim, the Mozilla Pootle server https://localize.mozilla.org/

L10n on Mercurial https://developer.mozilla.org/En/L10n_on_Mercurial

https://developer.mozilla.org/en/Localization_prerequisites

Creating a Language Pack https://developer.mozilla.org/en/Creating_a_Language_Pack

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

Learn about the Inkscape translation process

http://wiki.inkscape.org/wiki/index.php/Translation_information

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/

Audacity

Learn about the Audacity translation process

http://audacity.sourceforge.net/community/translation

Check current status here: http://code.google.com/p/audacity/source/browse/audacity-src/trunk#trunk%2Flocale

Post PO files to 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.

+++++++++++++++++++++++

Batti

http://gtk-apps.org/content/show.php/batti?content=132291&PHPSESSID=xpfyvhcukye

http://code.google.com/p/batti-gtk/

http://www.transifex.net/projects/p/batti/

https://www.transifex.net/projects/p/batti/r/all-resources/

http://gitorious.org/batti/batti/trees/master/po

+++++++++++++++++++++++

Gnash

PO / POT files found here: http://git.savannah.gnu.org/gitweb/?p=gnash.git;a=tree;f=po

Mail to the gnash-dev list http://lists.gnu.org/mailman/listinfo/gnash-dev

Report errors to bug-gnash@gnu http://lists.gnu.org/mailman/listinfo/bug-gnash

+++++++++++++++++++++++