Today is "DocumentationStringFreeze". We have finished the work with
the desktop guide for 17.04 and passed the remaining last strings to the
translators, who now have two weeks time to finalize the translations
(due March 30).
and in a couple of hours it will be updated with translations up to
Our new docs team member Chris Perry has done most of the work this
cycle. Doug and I have reviewed quite a few contributions, and it has
been a pleasure to mentor Chris on the nuts and bolts of the processes.
Chris has taken ownership of the tasks he took on, and has done an
excellent job in improving some parts of the desktop guide. Thanks for
being with us, Chris!
On 2017-03-30 18:55, Aputsiak Niels Janussen wrote:
> I'd like to know how these teams go about translating "ubuntu-docs".
> Do you use Launchpad for the translation process, and if so, how do
> you keep track of suggestions, terminology and so on.
The Swedish team has mostly used the Launchpad interface. As was
recently discussed in another thread, it does have its shortcomings
(doesn't handle fuzzy translations), but one advantage is that you can
submit suggestions, and somebody else can review and approve.
Another method is to download the PO file, edit it using e.g. Lokalize
(as Hannie mentioned) or Poedit, let someone else review the modified
file, and upload it when approved.
Achieving a consistent terminology is one of the challenges with
translating ubuntu-docs. Basically you need to have the development
version of Ubuntu available and follow the instructions to see which
terms are used in the various applications. I don't know of an easy way
to handle that. Collaborating within the translators team is important.
> I've considered moving the Danish translation process out of
> Launchpad to another system, say Pootle, but worry that
> synchronisation issues will make it a mess.
I agree with Doug, and would advise against using some other online
translation service. In the end the PO file must be uploaded to LP anyway.