Hi all, First let me thank Mechtilde for the tremendous job she is doing!
I still remember the day (OpenRheinRuhr 2018?) when I complained about the broken translation process and she instantly took over. Since then a lot of things have been accomplished. Now we are able to create language templates from source code, import them into Pootle, update the translations, export them back to SDF and commit them. In parallel we have "recruited" a handful of translators (Amharic, Kabyle, Oromo, Estonian, Latvian) so we hope to release AOO 4.2.0 with these new localizations [1]. To be clear, the plan is to automate the translation process on the Pootle server, so that once a week (?) the most recent translations are exported and committed to Git. But all this is done in our spare time and we all have a personal life, so please be patient (or join the team)! (Sorry for this being a bit Off Topic now...) Regards, Matthias [1] https://home.apache.org/~mseidel/AOO-builds/AOO-420-L10n/ Am 16.02.20 um 08:28 schrieb Mechtilde: > Hello Pedro > > Am 16.02.20 um 07:49 schrieb Pedro Albuquerque: >> Hi, >> >> Sorry for a small change of topic, but speaking of new builds, I believe it >> would be great if the 'building instructions' for SDF files were also made >> available in a simple way to follow. Maybe included with the rest of the >> process. > This is the recent page, where I start to document the recent process: > https://wiki.openoffice.org/wiki/Translation_from_4.2 > >> Like Pedro Lino said, we (me and him) are trying to test the updated >> translations and it would be of great help if we knew how to create the SDFs. > In short you have to use po2oo from the translate-toolkit > http://docs.translatehouse.org/projects/translate-toolkit/en/latest/commands/oo2po.html?highlight=po2oo > (part of some linux distributions) > > to improve the documentation of the translation process help is > appreciated. We can discuss it at > https://wiki.openoffice.org/w/index.php?title=Talk:Translation_from_4.2&action=edit&redlink=1 > >> Mechtilde, that page link you sent some time ago is exactly where I found the >> gsicheck broken link, so it doesn't help much. > The gsicheck is only available in the code of AOO. So you need a build > environment to run the gsicheck. The link I mentioned is only for the > help part with the possible options. > > If someone can help to isolate the code of gsicheck to have a standalone > tool, help is appreciated. >> Patricia, I have a machine in those circumstances and, so far, the only thing >> I did was the default cygwin installation. I'm very interested in following >> your 'manual', should it be available. >> >> Regards, >> Pedro Albuquerque > Kind regards
smime.p7s
Description: S/MIME Cryptographic Signature
