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


2014-12-04 19:56 GMT+01:00 Leif Lodahl <leiflodahl@gmail.com>:

Hi Sophie,
I'm translating on line.

A view like this:

https://translations.documentfoundation.org/da/libo_ui/translate/dbaccess/#filter=suggestions
is normally opening in a few seconds. Now I either get an error or the AJAX
is loading for several minutes without any result.


Right now that query loads in 4 to 5 seconds again – on my computer.

Sometimes Pootle is extremely slow, and other times it is okay. I wish the
different parts of Pootle were more separate so an upload or another job
that is tough for Pootle did not affect other parts of Pootle, so that
those of us that work on translations using the web interface were not
disturbed too much. But I guess (or hope) the developers of Pootle must be
aware of that problem and are working on a solution.

Do we have any influence on it? Could the tough Pootle operations be set to
low priority and the web interface to high priority, for instance?



Cheers,
Leif


Skål
Jesper

-- 
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.