launchpad-translators team mailing list archive
Mailing list archive
Re: Prioritize translation types by tags
I have made this suggestion recently, but a README file for each
project would be good, so that the project developer(s) can provide
general advice about translating a particular project.
Also, related to Yinghua's comment, how about a project specific
dictionary. For example in the project which I develop, the word
"layout" has a very specific meaning - it refers to the layout of
clips and effects in the multitrack editing window which can be saved
and reloaded. Therefore, the same word should be used each time for
"layout" so as not to confuse end users. The developers could create a
list of such terms as a project dictionary, and the translators then
decide on an equivalent word or phrase in their own language. Then
such keywords could be highlighted in bold in the English translation,
and when they are moused over, the translation of that keyword could
be shown as a tooltip.
On Tue, Apr 20, 2010 at 11:13 PM, Yinghua Wang <wantinghard@xxxxxxxxx> wrote:
> I agree with Anders. Translators should be able to leave
> more information more than marking strings fuzzy. Besides reasons
> above, inexperienced translators can make translations as suggestions and
> denote uncertain words or phrase. It helps reviewing a lot, as reviewers
> needn't go through every word to find improper expressions. Sometimes I
> just wonder why some strings are not adopted, literally them are fine. The
> previous translator can give a reason for this.
> My English is not very good. Hope you all can understand.
> Contact me with w-y-h8@xxxxxxx if Google is down.
> I hope that never happens...
> Mailing list: https://launchpad.net/~launchpad-translators
> Post to : launchpad-translators@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~launchpad-translators
> More help : https://help.launchpad.net/ListHelp