Changes

Jump to navigation Jump to search
Line 23: Line 23:     
 
=== Glucose (and related versioned projects) ===
+
=== [http://translate.sugarlabs.org/projects/glucose/ Glucose] (and related versioned projects) ===
 
 
 
This is the most current (development) version of Glucose.  It will eventually be frozen and numbered like the versions below.
 
This is the most current (development) version of Glucose.  It will eventually be frozen and numbered like the versions below.
   −
==== Glucose 0.92 ====
+
==== [http://translate.sugarlabs.org/projects/glucose96/ Glucose 0.96] ====
   −
Previous stable release of the Glucose project.  Released April 2011.  See 0.92 timeline [[0.92/Roadmap | here]]. This is used in the OLPC 11.x.x builds.
+
Current stable release of the Glucose project.  Released September 2011.  See 0.96 timeline [[0.96/Roadmap | here]]. This is used in the OLPC 12.1.x builds.
   −
==== Glucose 0.84 ====
+
As this is the version currently being packaged and distributed in various ways (OLPC builds, SOAS, Linus distro packages, etc.), this is a good place to start, the strings in this project largely overlap with Glucose (the development version) and finishing one of these two projects will result in many strings that can be easily transferred to the other.
   −
Prior stable release of the Glucose project.  Released April 2009.  See 0.84 timeline [[0.84/Roadmap | here]]. This is used in the OLPC 10.x.x builds.
+
==== [http://translate.sugarlabs.org/projects/glucose94/ Glucose 0.94] ====
+
Previous stable release of the Glucose project.  Released September 2011.  See 0.94 timeline [[0.94/Roadmap | here]]. This is used in the OLPC 11.3.x builds.
==== Glucose 0.82 ====
+
 
 +
=== [http://translate.sugarlabs.org/projects/fructose/ Fructose] (and related versioned projects) ===
 +
 
 +
This is the most current (development) version of Fructose. Fructose contains a number of activities that are considered core to the use of the Sugar UI as a learning tool.
   −
An early stable release of the Glucose project. Released August 2008. See 0.82 timeline [[0.82/Roadmap | here]].  These files are being phased out as newer builds are strongly recommended.
+
== [http://translate.sugarlabs.org/projects/honey Honey] ==
   −
=== Fructose (and related versioned projects) ===
+
Honey is the name given to the collection of independently developed Sugar Activities.  These offer many different functions, but all of them are essentially optional, although they are collectively an important part of the Sugar learning environment.
   −
This is the most current (development) version of Fructose. Fructose contains a number of activities that are considered core to the use of the Sugar UI as a learning tool.
+
== [http://translate.sugarlabs.org/projects/honey2 Honey2] ==
   −
==== Fructose 0.84 ====
+
Honey2 contains additional Honey activities.
   −
Previous stable release of the Fructose project. Released April 2009. See 0.84 timeline [[0.84/Roadmap | here]].
+
== [http://translate.sugarlabs.org/projects/dextrose Dextrose] ==
  −
==== Fructose 0.82 ====
     −
An early stable release of the Fructose project.  Released August 2008.  See 0.82 timeline [[0.82/Roadmap | here]]These files are being phased out as newer builds are strongly recommended.
+
These are strings that are added in Activity Central's Dextrose release of the modified Glucose project.  Completion of the corresponding Glucose project is also required for full Dextrose L10n.   
   −
== Honey ==
+
== [http://translate.sugarlabs.org/projects/sweets/ Sweets Distribution] ==
   −
Honey is the name given to the collection of independently developed Sugar ActivitiesThese offer many different functions, but all of them are essentially optional, although they are collectively an important part of the Sugar learning environment.
+
PO files related to SweetsYou will probably want the latest Glucose and Dextrose completed first.
   −
== Etoys ==
+
== [http://translate.sugarlabs.org/projects/etoys_new/ Etoys] ==
    
This is a rather large project.  [http://wiki.laptop.org/go/Etoys eToys] is a tool for learning programming concepts.
 
This is a rather large project.  [http://wiki.laptop.org/go/Etoys eToys] is a tool for learning programming concepts.
   −
== OLPC Software ==
+
== [http://translate.sugarlabs.org/projects/olpc_software/ OLPC Software] ==
    
These are strings related to switching between the Sugar GUI desktop and the GNOME GUI desktop.  Do not mistake this as being the only project needed to run an XO laptop.  Glucose and Fructose are essential for any XO laptop deployment.
 
These are strings related to switching between the Sugar GUI desktop and the GNOME GUI desktop.  Do not mistake this as being the only project needed to run an XO laptop.  Glucose and Fructose are essential for any XO laptop deployment.
Line 68: Line 69:     
These are strings related to an OLPC effort to develop some multi-language PR materials.  This is definitely optional for XO laptop function.
 
These are strings related to an OLPC effort to develop some multi-language PR materials.  This is definitely optional for XO laptop function.
 +
 +
== Upstream POT templates ==
 +
 +
 +
=== [http://translate.sugarlabs.org/projects/AbiWord/ AbiWord] ===
 +
 +
The Sugar word processor activity "Write" is a derivative of AbiWord.  Contributions to L10n of the upstream project are a nice "thank you" for their work.  AbiWord is also included in the GNOME boot on OLPC builds, so work on their strings will directly benefit XO users of more recent dual-boot builds.
 +
 +
http://abisource.com/contribute/translate/
 +
 +
In general, localization should be done on the development branch PO file as the AbiWord Team does not necessarily update the stable PO file versions.  In addition, the stable version is typically a subset fo the development version strings, os they are easily "backported".
 +
 +
We now host copies of the AbiWord PO files on our local Pootle server for the convenience of both teams of locaizers.
 +
 +
http://translate.sugarlabs.org/projects/upstream_POT/
 +
 +
Committing these files involves submitting them to the AbiWord dev list for action by their developers.  At this point, we do not have a direct "Commit to CVS" link from Pootle established.
 +
 +
=== 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:
 +
http://git.savannah.gnu.org/gitweb/?p=gnash.git;a=tree;f=po
 +
 +
Mail completed PO files 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
 +
 +
== Upstream L10n tracking ==
 +
 +
See [[Translation_Team/Upstream_localization]]
    
==Content Projects (locally hosted) ==
 
==Content Projects (locally hosted) ==
Line 96: Line 136:     
If your language is not present on that server, please write to help at scratch.mit.edu and request that it be established.  They will need language code, number of plurals and the plural equation to set it up, ask on the Localization lsit if you need information on those for your language.
 
If your language is not present on that server, please write to help at scratch.mit.edu and request that it be established.  They will need language code, number of plurals and the plural equation to set it up, ask on the Localization lsit if you need information on those for your language.
  −
=== AbiWord ===
  −
  −
The Sugar word processor activity "Write" is a derivative of AbiWord.  Contributions to L10n of the upstream project are a nice "thank you" for their work.  AbiWord is also included in the GNOME boot on OLPC builds, so work on their strings will directly benefit XO users of more recent dual-boot builds.
  −
  −
http://abisource.com/contribute/translate/
  −
  −
In general, localization should be done on the development branch PO file as the AbiWord Team does not necessarily update the stable PO file versions.  In addition, the stable version is typically a subset fo the development version strings, os they are easily "backported".
  −
  −
We now host copies of the AbiWord PO files on our local Pootle server for the convenience of both teams of locaizers.
  −
  −
http://translate.sugarlabs.org/projects/upstream_POT/
  −
  −
Committing these files involves submitting them to the AbiWord dev list for action by their developers.  At this point, we do not have a direct "Commit to CVS" link from Pootle established.
      
=== GCompris ===
 
=== GCompris ===

Navigation menu