More about this activity

The user selects an available target language and an installed activity. The user sees each string in sequence and can provide a new string, edit the current translation, or accept it as is. Once all of the strings have been shown, the user sees 'done'. At this point, the activity should be closed.

The translated file will be written to the po directory in the target activity.

Support

Support for this activity is provided by the developer at

Developer Comments

Version 1 is the first draft of this activity. For testing, it writes a copy of the original po file as po.orig. This can be used to check the results of the localization. It needs to write a compiled mo file to be useful. If a po file is not available for the selected activity, it needs to use the pot file as source.

What do you think?

Please log in to submit a review

Please do not post bug reports in reviews. We do not make your email address available to activity developers and they may need to contact you to help resolve your issue.

See the support section to find out where to get assistance for this activity.

Review Guidelines

Detailed Review

Release Notes

Version 2 — July 3, 2016 — 316 KB

This release compiles the edited po file. It is capable of end-end translation. A user can select a target language and an activity. Each string to be translated is presented one-by-one. The user can edit or accept the existing translation. When completed, the screen says 'done'. The activity can be closed.

The user can then change the Sugar locale (language control panel) to the target language and start the targeted activity. The translations given by the user should be visible.