On Thu, Dec 19, 2013 at 6:54 PM, Christian Lohmaier
<lohmaier+ooofuture@googlemail.com> wrote:
Hi *,
Is it right that so far only those teams, who are using
offline-translation (i.e. those who update po files from local
computer to pootle server) have been affected by the "translations
from other language" problem?
Or did projects using only pootle experience this?
In chatting with one of the pootle devs on irc, the suspected cause is
some bug in the threading/multiprocessing that is done in the
webserver's process.
In other words: Updating from the commandline should be safe.
ciao
Christian
--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted
Hi,
For Kazakh language I mostly use Pootle, but sometimes I do upload
single PO files or entire zipped directory
Regards
--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted
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.