Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index

Hi Christian,

On 2013.12.12. 13:56, Christian Lohmaier wrote:
Yes, 4.2.0 was the first time I did update the projects in pootle, and
I personally think it was not a huge desaster. There were two
stumbling stones:
1) update_against_templates aborting because of added/renamed files
2) lots of changes in help that only affect metadata (the xml-tag
attributes), not the actual translations

And one issue remained, there are more files in the database, than
actually needed, obsoleted files were not cleaned up (e.g. android/ folder).

Now what happened in December is a completely different story, esp.
that kk project did end up having Greek translation is still a
mystery, but not related to any updates.

And Greek has Kazakh fuzzies, as Dimitris reported yesterday: "Why in
the file of Greek sc/source/ui/src, I see so many Cyrillics with work
needed?  Was there a mistake?"
When I maintaned Pootle, I was also scared about possible database
corruption, and since 2.5.0 we are experiencing mysterious server
errors, e.g. when changing permissions on folders. TDF pays a monthly
fee to Pootle devs for maintenance. I don't know, if you have worked
with them, Christian. (I sent you a mail about Pootle 2.5.1 and/or
Django update a few days ago.)


To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.