Changes

Jump to navigation Jump to search
11 bytes removed ,  12:45, 31 March 2010
m
Line 23: Line 23:     
=== Update an activity translation independently of the Sugar release process ===
 
=== Update an activity translation independently of the Sugar release process ===
In general the translation process is tightly coupled with the release workflow. In order to get the latest translations for a particular activity, deployments need to either wait for the activity maintainer to make a new release, or use the language pack mechanism, which is distribution specific, and an ugly hack at its best. The [[Features/Enhanced_Gettext | Enhanced Gettext Feature]] adds an extra search path for translation files for Sugar activities. This allows deployments to add and update activity translations independently of the release process. The alternate search path can be configured using [http://projects.gnome.org/gconf/ GConf configuration system].  
+
In general the translation process is tightly coupled with the release workflow. In order to get the latest translations for a particular activity, deployments need either to wait for the activity maintainer to provide a new release or to use the language-pack mechanism, which is distribution specific (and at its best an ugly hack). The [[Features/Enhanced_Gettext | Enhanced Gettext Feature]] adds an extra search path for the translation files of Sugar activities. This allows deployments to add and update activity translations independently of the release process. The alternate search path can be configured using [http://projects.gnome.org/gconf/ GConf configuration system].  
   −
With this Feature life should become a lot easier for deployments who rely on a small translator team to accomplish the job which often find it more difficult to keep up with the Sugar release cycle. Furthermore, we hope to take the burden from activity maintainers to make new releases to incorporate newer translations with this enhancement.
+
With this feature it should be easier for deployments who rely on a small translator team to accomplish their job since they no longer need to keep pace with the Sugar release cycle. Furthermore, we hope to alleviate activity maintainers from the burden of making a new release whenever a new translation becomes available.
    
=== A message is displayed when an activity fails to start ===
 
=== A message is displayed when an activity fails to start ===

Navigation menu