Re: [libreoffice-l10n] Testing current pootle translation

2012-02-24 Thread Andras Timar
Hi, 2012/2/24 Jon Lachmann : >> Pre-release along with language packs are good way to see thetranslation >> result. However, it is kind of late to see the translationerror in that >> build. Problems are often caught after final releasebecause of the time to >> see if translations are well being sh

Re: [libreoffice-l10n] Testing current pootle translation

2012-02-24 Thread Olivier Hallot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 If it makes technical sense and adds value to the project, you will be surprised to see the swarm of amateur developers eager to make the move... Em 24-02-2012 16:30, khagaroth escreveu: > But converting the whole thing to gettext > would probably be

Re: [libreoffice-l10n] Testing current pootle translation

2012-02-24 Thread khagaroth
Of course the best option would be if LO switched to pure gettext so that we could simply put updated MO files to the language folder and immediately see the changes. But converting the whole thing to gettext would probably be a pretty big (and tedious and uninteresting) undertaking. -- Unsubscri

[libreoffice-l10n] [ANNOUNCE] Branch libreoffice-3-5-1 created

2012-02-24 Thread Petr Mladek
Hi all, there have been created the libreoffice-3-5-1 branch. It will be used for fine tuning of the 3.5.1 release. It was created before the tag for 3.5.1-rc1 to avoid race condition in the automatically generated bugzilla comments. It was created already on Wednesday evening. I did not announc

Re: [libreoffice-l10n] Testing current pootle translation

2012-02-24 Thread Jon Lachmann
> Pre-release along with language packs are good way to see thetranslation > result. However, it is kind of late to see the translationerror in that > build. Problems are often caught after final releasebecause of the time to > see if translations are well being short. I think we should have night

Re: [libreoffice-l10n] Testing current pootle translation

2012-02-24 Thread Cheng-Chia Tseng
Pre-release along with language packs are good way to see the translation result. However, it is kind of late to see the translation error in that build. Problems are often caught after final release because of the time to see if translations are well being short. By the way, Key-ID language build

Re: [libreoffice-l10n] Testing current pootle translation

2012-02-24 Thread Jon Lachmann
Hi andras, Would it be possible to implement an easier procedure to test new translations? Maybe integrating them into nightly builds or similar? It is very hard to know exactly where in the program a specific phrase will be shown, and what other phrases will be along it to create a good total r

[libreoffice-l10n] Presenter screen vs Presenter console

2012-02-24 Thread Sérgio Marques
Hi there, I was wondering. Isn´t Presenter Screen the same extension as Presenter Console? If so, why strings in poottle/source code don´t get updated? This could lead to discrepancies in translations. -- Sérgio Marques -- Unsubscribe instructions: E-mail to l10n+h...@global.libreoffice.org P

Re: [libreoffice-l10n] Testing current pootle translation

2012-02-24 Thread Andras Timar
Hello Jon, 2012/2/24 Jon Lachmann : > Hello! > > How can i download and test the latest > translation from the pootle server in libreoffice? > You need to build LibreOffice from the source code. It is not (yet) possible to snap-in translations from Pootle to an existing LibreOffice install. For

[libreoffice-l10n] Testing current pootle translation

2012-02-24 Thread Jon Lachmann
Hello! How can i download and test the latest translation from the pootle server in libreoffice? Best regards! -- Unsubscribe instructions: E-mail to l10n+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http: