98
edits
Changes
Features/Enhanced Gettext (view source)
Revision as of 13:14, 3 January 2010
, 13:14, 3 January 2010Created page with '<noinclude>{{TOCright}} Category:Feature Page Incomplete Enhanced Gettext </noinclude> == Summary == ''Enhanced Gettext adds an extra search path for tr…'
<noinclude>{{TOCright}}
[[Category:Feature Page Incomplete]]
[[Category:Feature|Enhanced Gettext]]
</noinclude>
== Summary ==
''Enhanced Gettext adds an extra search path for translation files for Sugar activities. This would allow deployments to add and update activity translations independently of the release process.''
== Owner ==
''This should link to your home wiki page so we know who you are''
* Name: [[User:SayaminduDasgupta| Sayamindu Dasgupta]]
* Email: sayamindu at gmail dot com
== Current status ==
* Targeted release: 0.88
* Last updated: Jan 3, 2010
* Percentage of completion: 10%
== Detailed Description ==
Currently 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 make a new release, or use the language pack mechanism, which is distribution specific, and an ugly hack at its best. This feature would add a sugar.gettext module, which, if used by activities, will search an alternative path (configurable via GConf) for translations before looking into the activity directory (where the translations present in the original release bundle exist.
== Benefit to Sugar ==
* Life becomes a lot easier for deployments who rely on a small translator team to accomplish the job (smaller translation teams find it more difficult to keep up with the Sugar release cycle)
* Activity maintainers do not have to worry about making new releases to incorporate newer translations.
* See thread starting from http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg10663.html
== Scope ==
* A sugar.gettext module needs to be created in sugar-toolkit (or sugar-base ??)
* Activity authors need to do ''import sugar.gettext'' instead of ''import gettext'' (it may make sense to keep the import sugar.gettext in a try: block to retain backward compatibility)
==UI Design==
N/A
== How To Test ==
{{:{{PAGENAME}}/Testing}}
== User Experience ==
N/A
== Dependencies ==
None
== Contingency Plan ==
None necessary, revert to previous release behaviour.
== Documentation ==
* See thread starting from http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg10663.html
== Release Notes ==
The sugar.gettext module extends the standard Python gettext support to allow for updated translations to exist outside the activity directory. This enables deployments to add and update translations later, without depending on the release process. To take advantage of this, Activity developers should use the ''sugar.gettext'' module instead of the standard ''gettext''.
== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page. -->
[[Category:Feature Page Incomplete]]
[[Category:Feature|Enhanced Gettext]]
</noinclude>
== Summary ==
''Enhanced Gettext adds an extra search path for translation files for Sugar activities. This would allow deployments to add and update activity translations independently of the release process.''
== Owner ==
''This should link to your home wiki page so we know who you are''
* Name: [[User:SayaminduDasgupta| Sayamindu Dasgupta]]
* Email: sayamindu at gmail dot com
== Current status ==
* Targeted release: 0.88
* Last updated: Jan 3, 2010
* Percentage of completion: 10%
== Detailed Description ==
Currently 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 make a new release, or use the language pack mechanism, which is distribution specific, and an ugly hack at its best. This feature would add a sugar.gettext module, which, if used by activities, will search an alternative path (configurable via GConf) for translations before looking into the activity directory (where the translations present in the original release bundle exist.
== Benefit to Sugar ==
* Life becomes a lot easier for deployments who rely on a small translator team to accomplish the job (smaller translation teams find it more difficult to keep up with the Sugar release cycle)
* Activity maintainers do not have to worry about making new releases to incorporate newer translations.
* See thread starting from http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg10663.html
== Scope ==
* A sugar.gettext module needs to be created in sugar-toolkit (or sugar-base ??)
* Activity authors need to do ''import sugar.gettext'' instead of ''import gettext'' (it may make sense to keep the import sugar.gettext in a try: block to retain backward compatibility)
==UI Design==
N/A
== How To Test ==
{{:{{PAGENAME}}/Testing}}
== User Experience ==
N/A
== Dependencies ==
None
== Contingency Plan ==
None necessary, revert to previous release behaviour.
== Documentation ==
* See thread starting from http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg10663.html
== Release Notes ==
The sugar.gettext module extends the standard Python gettext support to allow for updated translations to exist outside the activity directory. This enables deployments to add and update translations later, without depending on the release process. To take advantage of this, Activity developers should use the ''sugar.gettext'' module instead of the standard ''gettext''.
== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page. -->