What do you want in your translation summary page?
mark at canonical.com
Sun Apr 23 12:00:53 BST 2006
Robert Schumann wrote:
>> Wordlists! I'm used to do translations in other fields too and
>> wordlists are a "must have" if there is more than one translator. It
>> is the only way to agree on words and synonyms and it saves a lot of
>> time and discussions about how to translate specific terms,
>> especially for people who jump on the running train.
> I'm a fairly inexperienced translator, and I've been scared to jump in
> to translations precisely because of all the issues mentioned in the
> last week or so i.e. there doesn't seem to be an easy way for group
> admins to approve my translations, sometimes I can't translate a
> sentence because I'm unsure of the conventional translation of just
> one word, and so on.
> Regarding wordlists: I procured an electronic dictionary of IT terms
> from another project, and parsed it into wiki format; it is now
> available at
> Unfortunately it doesn't have many open source-related words. We also
> have our own dictionary at
> https://wiki.ubuntu.com/AfrikaansTranslators/VertalerWoordeboek, but I
> don't think many of the active translators use or contribute to it.
> I think the wiki is the ideal place for such wordlists because of the
> unrestricted format. You can also include information about, for
> example, how to approach the translation of iso-3166-2
> (geocodes, which include place names in other languages) which you
> couldn't do in a strict Rosetta-based wordlist. It is also easy to
> find and interlink words in a wiki - to impose a structure.
In Rosetta, we should not try and build a wordlist or glossary, we
should instead add the ability to link TO a wordlist or glossary
somewhere on the web. I will add a specification for that functionality
to Blueprint for Rosetta.
> In summary, I'd like to endorse (not necessarily related to the
> summary page):
> * a way to see which packages have upstream translations and what
> should be done in that case (mentioned by mdke in posting
I think this is already displayed if you have filled out the correct
packaging information. This is a little tricky, I'll explain it here in
Upstream translations are connected to a Product Series for that
upstream. This lets us have translations on-the-go for Foo 1.2 and Foo
1.4, at the same time, because 1.2 and 1.4 are "series" and we store the
templates for them separately. You need to make sure that Launchpad
knows which source package in Ubuntu is related to each of Foo 1.2 and
Foo 1.4. It might be that there is a foo1.2 package and a foo1.4
package, in which case they need to be connected to their respective
product series. Or it might be that there is just a foo package, in
which case you need to determine which upstream version it relates to
and connect it to the appropriate series.
Make sense? To do the connecting, go to the page for the productseries.
It probably lives at:
Look for the link on the left that says "Link to Ubuntu package" and
then do what comes naturally.
> * all the ideas about finding out who created a particular (broken)
> string and searching for strings from one person.
> * recently translated (*not* recently imported) strings displayed on
> the summary page, so you can see where activity is
> * high priority packages to translate, as determined by the team
> leader or rosetta admins?
> * popcon rating (or other indication of significance) of any
> particular package. I'd prefer to translate something that is going
> to be used, rather than a niche application that is only for use in
> Outer FarOffLand....
Yes, I have a spec for this in the pipeline too. Look for
RosettaTranslationPriorities or something like that to show up in
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rosetta-users