Hello Andrea, Am 26.11.18 um 00:54 schrieb Andrea Pescetti: > 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?
I could use gsicheck use successfully. I found the it language has some problems with the help files. I have to look deeper in it and I will fix it by hand. It seems to be some problems with closing tags. As I understand working with *.po files (gettext or pootle) changing the place of a string will fuzzy it. But it is easy to correct it in Pootle. You can select there for such fuzzy strings and say "yes, this translation is right " with one click. >> 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, After the trunk branch is now fixed and builable I will commit my *.sdf files there. And then put them back to pootle for the next round of translations when I have shell access. > >> @ 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 opened the Jira ticked today > 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. I started there: https://wiki.openoffice.org/wiki/Translation_from_4.2 > > Regards, > Andrea. > Kind regards -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows ## Debian Developer ## Loook, tbsync, libreoffice-canzeley-client ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
signature.asc
Description: OpenPGP digital signature
