Difference between revisions of "GoogleCodeIn2012/Virtaal"
| (5 intermediate revisions by 2 users not shown) | |||
| Line 8: | Line 8: | ||
;Task:It would be especially desirable if the Sugarized version of Virtaal could be enhanced so that it's existing capability to read and write PO and MO files could be leveraged to use the PO or MO files present in the local source code to allow "bootstrapping" of L10n on a Sugar Environment. | ;Task:It would be especially desirable if the Sugarized version of Virtaal could be enhanced so that it's existing capability to read and write PO and MO files could be leveraged to use the PO or MO files present in the local source code to allow "bootstrapping" of L10n on a Sugar Environment. | ||
| + | There are additional enhancements that might include a method for "upstreaming" those local translations to be shared with the Sugar Community (after review and posting to the Pootle server). However for the purposes of this task, the goal is to get Virtaal running cleanly on Sugar. | ||
| + | |||
| + | Deliverables: | ||
| + | |||
| + | 1) An .xo bundle (based on a code repository hosted on Sugar Labs Gitorious instance (http://git.sugarlabs.org) | ||
| + | |||
| + | 2) The activity should be submitted to ASLO. | ||
| + | |||
| + | 3) In addition to the typical Sugar features (e.g. journal, collaboration, etc.) the activity should have the ability to discover and localize Sugar Activities and source code present on the same Sugar instance. This may need to be limited to those languages for which glibc locales are present on the platform. | ||
| + | |||
| + | ==References for Sugarizing== | ||
Further details about what it means to "Sugarize" a program can be learned by reading this page. | Further details about what it means to "Sugarize" a program can be learned by reading this page. | ||
| Line 13: | Line 24: | ||
http://wiki.sugarlabs.org/go/Development_Team/Low-level_Activity_API | http://wiki.sugarlabs.org/go/Development_Team/Low-level_Activity_API | ||
| + | One possible approach would be to use the template described here: | ||
| + | |||
| + | http://lists.sugarlabs.org/archive/dextrose/2012-September/001942.html | ||
| − | + | Another approach is described at the links below. | |
| + | *Instructions and history: http://people.sugarlabs.org/Tgillard/sugarize/wiki-sugarize.txt | ||
| + | *Files: http://people.sugarlabs.org/Tgillard/sugarize/ | ||
;Contacts:cjl --at-- sugarlabs.org and walter --at-- sugarlabs.org | ;Contacts:cjl --at-- sugarlabs.org and walter --at-- sugarlabs.org | ||
| − | + | :Freenode IRC #sugar : cjl and walterbender | |
[[Category: GCI2012]] | [[Category: GCI2012]] | ||
Latest revision as of 08:24, 24 December 2012
- Background
- Virtaal is an excellent PO file editor developed by the same team that publishes the Pootle transltion server we use for Sugar localization (L10n).
http://translate.sourceforge.net/wiki/virtaal/index
It is written in Python and should be readily ported to run as a Sugar Activity.
- Task
- It would be especially desirable if the Sugarized version of Virtaal could be enhanced so that it's existing capability to read and write PO and MO files could be leveraged to use the PO or MO files present in the local source code to allow "bootstrapping" of L10n on a Sugar Environment.
There are additional enhancements that might include a method for "upstreaming" those local translations to be shared with the Sugar Community (after review and posting to the Pootle server). However for the purposes of this task, the goal is to get Virtaal running cleanly on Sugar.
Deliverables:
1) An .xo bundle (based on a code repository hosted on Sugar Labs Gitorious instance (http://git.sugarlabs.org)
2) The activity should be submitted to ASLO.
3) In addition to the typical Sugar features (e.g. journal, collaboration, etc.) the activity should have the ability to discover and localize Sugar Activities and source code present on the same Sugar instance. This may need to be limited to those languages for which glibc locales are present on the platform.
References for Sugarizing
Further details about what it means to "Sugarize" a program can be learned by reading this page.
http://wiki.sugarlabs.org/go/Development_Team/Low-level_Activity_API
One possible approach would be to use the template described here:
http://lists.sugarlabs.org/archive/dextrose/2012-September/001942.html
Another approach is described at the links below.
- Instructions and history: http://people.sugarlabs.org/Tgillard/sugarize/wiki-sugarize.txt
- Files: http://people.sugarlabs.org/Tgillard/sugarize/
- Contacts
- cjl --at-- sugarlabs.org and walter --at-- sugarlabs.org
- Freenode IRC #sugar : cjl and walterbender