Diff for "FeatureChecklist/Translations"

Not logged in - Log In / Register

Differences between revisions 3 and 4
Revision 3 as of 2010-07-30 11:51:21
Size: 604
Comment:
Revision 4 as of 2010-07-30 13:36:31
Size: 2603
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
 * Partial .po exports
 * Full .po exports for one language in a projecct
 * Full .po exports for all languages in a project
 * Export of changes relative to upstream
 * Exports for a project release series or source package (collectively, per language, or as individual translation files).
 * Export of gettext (.po) format and generation of MO files, as well as a custom gettext-based XPI compatibility format. Import of gettext as well as Mozilla XPI.
 * Full-featured gettext support in the GNU, Gnome, and KDE dialects: plural forms, message contexts, source references, comments, and flags.
Line 9: Line 10:
 * Automatic suggestions  * Automatic suggestions from other projects and packages
 * Automatic suggestions from other languages
Line 12: Line 14:
 * Permission policies
 * Translator mode
 * Reviewer mode
 * Separate permissions for the "translate" and "review" activities.
 * Configurable permission models.
 * Organizational structures for translation and review: translation groups and translation teams.
 * Translation UI for the "translate" and "review" activities.
Line 17: Line 20:
 * Automatic suggestions
 * .pot file comments display
 * Automatic .pot file generation
 * Display of template comments
 * If you use intltool: commit a change to your code (in Launchpad or some other repository) and see your new translatable strings automatically show up in the Launchpad translation UI.
  * Translate in a web UI or, given the right permissions, do them in your favourite editor and upload them. Or commit them to your bzr branch and have them imported from there.
  * Let Launchpad commit additional translations made in the web UI back to your bzr branch--or another bzr branch of your choice.
 * Automatic translation credits.
 * Separate translation of multiple release series, with automatic sharing for identical strings.
 * Personal "dashboard" to guide translators and reviewers to where their effort is needed most.
 * Translation statistics: untranslated messages, translated messages, messages changed compared to upstream, translated messages that weren't translated upstream.
 * Prioritized template listings.
 * Show contributions by specific users, and how they are used.
 * Filtered translation views for untranslated messages; messages with new suggestions; and messages that have been changed compared to upstream.
 * Automatic checking of format strings.
 * Detection of conflicts between translations in uploaded files and concurrent changes in the web UI.
 * Summarized overviews for your preferred language(s).
 * Automatic translation imports from package builds.
 * Language packs.

Translations

  • Export of changes relative to upstream
  • Exports for a project release series or source package (collectively, per language, or as individual translation files).
  • Export of gettext (.po) format and generation of MO files, as well as a custom gettext-based XPI compatibility format. Import of gettext as well as Mozilla XPI.
  • Full-featured gettext support in the GNU, Gnome, and KDE dialects: plural forms, message contexts, source references, comments, and flags.
  • Manual .pot uploads
  • Continuous template (.pot) and translation file (.po) imports from specified Bazaar branches
  • Continuous translation file (.po) exports to a Bazaar branch
  • Automatic suggestions from other projects and packages
  • Automatic suggestions from other languages
  • Translation groups
    • Translation teams
  • Separate permissions for the "translate" and "review" activities.
  • Configurable permission models.
  • Organizational structures for translation and review: translation groups and translation teams.
  • Translation UI for the "translate" and "review" activities.
  • Translation guidelines
  • Plural forms
  • Display of template comments
  • If you use intltool: commit a change to your code (in Launchpad or some other repository) and see your new translatable strings automatically show up in the Launchpad translation UI.
    • Translate in a web UI or, given the right permissions, do them in your favourite editor and upload them. Or commit them to your bzr branch and have them imported from there.
    • Let Launchpad commit additional translations made in the web UI back to your bzr branch--or another bzr branch of your choice.
  • Automatic translation credits.
  • Separate translation of multiple release series, with automatic sharing for identical strings.
  • Personal "dashboard" to guide translators and reviewers to where their effort is needed most.
  • Translation statistics: untranslated messages, translated messages, messages changed compared to upstream, translated messages that weren't translated upstream.
  • Prioritized template listings.
  • Show contributions by specific users, and how they are used.
  • Filtered translation views for untranslated messages; messages with new suggestions; and messages that have been changed compared to upstream.
  • Automatic checking of format strings.
  • Detection of conflicts between translations in uploaded files and concurrent changes in the web UI.
  • Summarized overviews for your preferred language(s).
  • Automatic translation imports from package builds.
  • Language packs.

FeatureChecklist/Translations (last edited 2010-09-17 13:16:26 by matthew.revell)