Changes

Jump to navigation Jump to search
no edit summary
Line 36: Line 36:  
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.
 
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.
   −
=== Fructose (and related versioned projects) ===
+
=== [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.
 
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.
   −
== Honey ==
+
== [http://translate.sugarlabs.org/projects/honey Honey] ==
    
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.
 
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.
   −
== Honey2 ==
+
== [http://translate.sugarlabs.org/projects/honey2 Honey2] ==
    
Honey2 contains additional Honey activities.   
 
Honey2 contains additional Honey activities.   
   −
== Dextrose ==
+
== [http://translate.sugarlabs.org/projects/dextrose Dextrose] ==
    
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.   
 
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.   
   −
== Sweets Distribution ==
+
== [http://translate.sugarlabs.org/projects/sweets/ Sweets Distribution] ==
    
PO files related to Sweets.
 
PO files related to Sweets.
   −
== 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 ==
+
== [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 73: Line 73:       −
=== AbiWord ===
+
=== [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.
 
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.
Line 87: Line 87:  
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.
 
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===
+
=== 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.
 
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.

Navigation menu