How to manage GUI and documentation translation for the same project

[Mark Shuttleworth]

rangzen wrote:

>is there an easy way to manage GUI and documentation translation for
>the same project ?
>Cause if i put everything in the same pot,po and mo file, when i will
>use the application, it will load the translation for GUI AND
>documentation instead of just the GUI.
>And it can be a huge doc :)
>Do i have to create an other project with "-doc" especially for the
>documentation ?
>Is there a special way to manage that in rosetta ?
>
Rosetta can support multiple PO templates for a single "product series".

A "product series" is a series of releases, like "Gimp 2.2" which can
have releases 2.2.0, 2.2.1, 2.2.2 etc. Rosetta does not track the
specific pofiles for the releases, just the "current working potemplates
and pofiles" for the whole series. The idea is that you can keep
translating after any particular release, and those translations will
make it into the next release.

So, in Launchpad, you should have registered your product.

Then, you register a "series", for the current working series. You can
have a series called "main" for the trunk or HEAD or whatever you call
the unstable-line-of-development. And you can have a series for each of
the stable branches of the product. But most people just start with a
single series.

Next, you can attach one, two or more PO templates to a series. In your
case, you would have "foo" and "foo-doc" as your PO template names.
People can then translate those separately. You should update the PO
templates regularly, so that users are translating the latest strings.
This is especially true when you freeze the strings and documentation.

Make sense?

Mark