Translation Team/Upstream localization - Revision history

Cjl: /* Scratch */

2011-08-01T18:33:54Z

Scratch

← Older revision		Revision as of 14:33, 1 August 2011
Line 51:		Line 51:

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

Cjl: /* OLPC Software project */

2011-08-01T18:31:34Z

OLPC Software project

← Older revision		Revision as of 14:31, 1 August 2011
Line 9:		Line 9:
	===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

Cjl at 18:26, 1 August 2011

2011-08-01T18:26:20Z

← Older revision		Revision as of 14:26, 1 August 2011
Line 1:		Line 1:
	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.

Cjl at 06:00, 20 July 2011

2011-07-20T06:00:03Z

@@ Line 49: / Line 49: @@
 http://translationproject.org/html/welcome.html
 ===Scratch===
@@ Line 239: / Line 135: @@
 http://gitorious.org/batti/batti/trees/master/po
 +++++++++++++++++++++++

Cjl: /* GNASH */

2011-07-17T12:48:37Z

GNASH

← Older revision		Revision as of 08:48, 17 July 2011
Line 254:		Line 254:
	http://git.savannah.gnu.org/gitweb/?p=gnash.git;a=tree;f=po		http://git.savannah.gnu.org/gitweb/?p=gnash.git;a=tree;f=po

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

Cjl: /* GNOME Tracking Ticket in Pootle */

2011-07-17T12:46:54Z

GNOME Tracking Ticket in Pootle

← Older revision		Revision as of 08:46, 17 July 2011
Line 36:		Line 36:
	===GNOME Tracking Ticket in Pootle===		===GNOME Tracking Ticket in Pootle===

	There are specific GNOME modules and ~~pavckages~~ that are pulled into OLPC builds. The ~~GNOMR~~ upstream has kindly provided us ~~wit ha~~ "release set" that allows us to track these ~~sepcific~~ packages on their upstream L10n server.		There are specific GNOME modules and packages that are pulled into OLPC builds. The GNOME upstream has kindly provided us with a "release set" that allows us to track these specific packages on their upstream L10n server.

	http://l10n.gnome.org/releases/olpc/		http://l10n.gnome.org/releases/olpc/

Cjl: /* GNOME Tracking Tickets in Pootle */

2011-07-17T12:46:00Z

GNOME Tracking Tickets in Pootle

Show changes

Cjl: /* Gnash */

2011-06-29T12:40:05Z

Gnash

← Older revision		Revision as of 08:40, 29 June 2011
Line 376:		Line 376:
	+++++++++++++++++++++++		+++++++++++++++++++++++

	===~~Gnash~~===		===GNASH===

			We now host a local copy of the GNASH PO files, but when they are completed, they need to be sent to the gnash-dev list to be committed.

			Our local copies are in this project:
			http://translate.sugarlabs.org/projects/upstream_POT/

			If you don't see this project (or a GNASH PO file in it) for your language, just ask on the localization list and it will be created. If you are a language admin, you can "Update from templates" if you already have this project.

	PO / POT files found here:		PO / POT files found here:

Cjl at 12:25, 29 June 2011

2011-06-29T12:25:37Z

← Older revision		Revision as of 08:25, 29 June 2011
Line 1:		Line 1:
	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) 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.

	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.

Cjl at 12:25, 29 June 2011

2011-06-29T12:25:13Z

← Older revision		Revision as of 08:25, 29 June 2011
Line 1:		Line 1:
	~~This page~~ is ~~under development [[~~User~~:Cjl\|Cjl]] 15:01~~, ~~22 April 2011~~ (~~EDT~~)		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.

	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.

	==Hosted Projects==		== 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.		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.
Line 179:		Line 179:

	===Translation Project Tracking Tickets in Pootle===		===Translation Project Tracking Tickets in Pootle===
			The Translation Project hosts localization for a number of free and open source software (FOSS) packages, including some that are used in making Sugar and OLPC software releases. In some cases. it is necessary to first fill out a form specifically giving up your inherent copyright (disclaiming) to the strings you contribute to assure that they can be shared freely anywhere in the world (local copyright laws differ, making this necessary).

			http://translationproject.org/html/welcome.html

	====aspell====		====aspell====