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 the [http://projects.gnome.org/gconf/ GConf configuration system]. The GConf key is ''/schemas/desktop/sugar/i18n/langpackdir'' which is unset by default. | 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 the [http://projects.gnome.org/gconf/ GConf configuration system]. The GConf key is ''/schemas/desktop/sugar/i18n/langpackdir'' which is unset by default. |