rosetta-unifying-translations

Differences between revisions 1 and 4 (spanning 3 versions)
Revision 1 as of 2007-05-29 10:07:14
Size: 851
Editor: 200-127-67-94
Comment: Started.
Revision 4 as of 2008-08-06 16:14:34
Size: 2628
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
 * '''Drafter''': [wiki:MartinAlbisetti Martin Albisetti]  * '''Drafter''': [[MartinAlbisetti|Martin Albisetti]]
Line 13: Line 13:
Packages in Ubuntu should be consistent in every aspect possible. The decentralized nature of Rosetta allows more to be translated, but it makes it very hard to keep common terms consistent across packages (and sometimes in the same package).
It's a frequent practice for translation groups to have [[https://wiki.ubuntu.com/UbuntuSpanishTranslators|a list preferred translations]] for a specific word, and it would would make sense to have these available in Rosetta, and automatically presented when the word comes up.
This would make any random user passing by and translating a few strings much more productive and better quality, and would solve many problems between variations of the language in different countries.
Line 16: Line 19:
 * John is new to the Ubuntu community, lands on Rosetta and decides to translate a few strings. Suggestions for specific words will guide him and give him more confidence.
 * Matt is a regular translator but doesn't remember how he translated a specific term a few months ago, suggestions would serve as a reminder (gnome/kde menus are a good example, not everyone knows what "Preferences" translates into on the actual menu).
 * A new package is imported and has many inconsistencies, suggestions would make reviewing it much easier.

Line 17: Line 25:

 * An interface per language should be created for the translation team to add preferred translations (word in english > word in language)
 * Rights management should be the same as translations (open, moderated and restricted)
Line 20: Line 31:
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like: === UI Changes ===
Line 22: Line 33:
=== UI Changes ===

 * A list of preferred terms should appear on the row that contain words specified in the list (or maybe on the page?)
Line 27: Line 36:

 * How to prevent abuse/misuse (think adding "a" to the list)

== Related Bugs/Blueprints ==
[[https://bugs.launchpad.net/rosetta/+bug/44/|Translations should be searchable]]

[[https://blueprints.launchpad.net/rosetta/+spec/translate-specific-string/|Translate Specific String]]

Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.

Summary

Create a list of preferred translations for specific words per language to make it easier to have consistency among packages in translations.

Rationale

Packages in Ubuntu should be consistent in every aspect possible. The decentralized nature of Rosetta allows more to be translated, but it makes it very hard to keep common terms consistent across packages (and sometimes in the same package). It's a frequent practice for translation groups to have a list preferred translations for a specific word, and it would would make sense to have these available in Rosetta, and automatically presented when the word comes up. This would make any random user passing by and translating a few strings much more productive and better quality, and would solve many problems between variations of the language in different countries.

Use Cases

  • John is new to the Ubuntu community, lands on Rosetta and decides to translate a few strings. Suggestions for specific words will guide him and give him more confidence.
  • Matt is a regular translator but doesn't remember how he translated a specific term a few months ago, suggestions would serve as a reminder (gnome/kde menus are a good example, not everyone knows what "Preferences" translates into on the actual menu).
  • A new package is imported and has many inconsistencies, suggestions would make reviewing it much easier.

Design

  • An interface per language should be created for the translation team to add preferred translations (word in english > word in language)

  • Rights management should be the same as translations (open, moderated and restricted)

Implementation

UI Changes

  • A list of preferred terms should appear on the row that contain words specified in the list (or maybe on the page?)

Outstanding Issues

  • How to prevent abuse/misuse (think adding "a" to the list)

Translations should be searchable

Translate Specific String

BoF agenda and discussion


CategorySpec

rosetta-unifying-translations (last edited 2008-08-06 16:14:34 by localhost)