Hi Rimas
Thank you for fixing it. I have downloaded the file lo-build-pt_BR.po
for offline translation.
However I noticed a string count difference between Pootle online and
offline transalation:
The file I downloaded has 784 strings
The pootle interface for lo-build-pt_BR.po has 549 strings.
I was expecting the same string count. I am concerned to upload my
offline translated file if this is going to break something in the build.
Thank you and Merry Christmas
Olivier
Em 22-12-2010 15:53, Rimas Kudelis escreveu:
2010.12.22 18:32, Olivier Hallot rašė:
Hello from sunny and hot Rio de Janeiro... :-)
Each time I try to download the po file for offline download I get a
"file not
found" error...
http://translations.documentfoundation.org/pt_BR/libo33/lo-build-pt_BR.po/downlo
ad/
Can we fix this?
Thanks in advance.
This happens because of a conflict with Breton language. I've fixed it
for now, but can't guarantee that it won't happen again.
I plan to update Pootle and Translate Toolkit to latest versions
whenever I find out how TT was installed on the server, hopefully this
problem will go away then...
Meanwhile, sorry for inconvenience! Hope you can bear with it for now.
Rimas
--
Olivier Hallot
Founder, Steering Commitee Member - The Document Foundation
Translation Leader for Brazilian Portuguese
--
Unsubscribe instructions: E-mail to l10n+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/l10n/
*** All posts to this list are publicly archived for eternity ***
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.