On 25/11/2018 Mechtilde wrote:> now I'm able to create sdf files based
on the source code and the files
in Pootle.
(changing subject since I'm not commenting on the build issue, but on
the other information).
This is good news! Have you experienced/fixed the two issues I had
found, meaning that you can go through gsicheck successfully and that
you found a way to move strings to their new place?
So I think we need a branch whre we can work for the next release like 4.2.
We should just use trunk. We branch only for "stabilization", i.e.,
close to a release. But the real active development happens on trunk.
@ Jim: Can you gererate a 4.2 branch up to r 184789. Then I can put the
new sdf files. I did it manually for 6 Languages.
I will do it then for all Languages in Pootle.
Just ask Infra to get shell access to translate.apache.org (this is done
by opening a JIRA ticket; Pootle is not an OpenOffice-specific service,
so Infra manages it completely). I admit I haven't tried that way since
I only exported Italian and a couple other test languages back at the time.
After then I can create new *.po files to import in Pootle.
This will be an especially important step. We haven't imported strings
into Pootle for a long time. If all the workflow up to and including
this step can be fixed, we will be able to engage translators and
preserve their work.
I will also publish the documentation after migration of the wiki.
The "old" https://wiki.openoffice.org is free for editing at any time
until you see a prominent notice on all pages. Don't worry, content
published before we put the notice will all be migrated.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
