Hi,
Pootle seems to be very slow, unresponsive or even not available today.
This is very unfortunate now that we are busy translating 4.4.
Cheers,
Leif Lodahl
The Danish Team
Hi,
Pootle seems to be very slow, unresponsive or even not available today.
This is very unfortunate now that we are busy translating 4.4.
Cheers,
Leif Lodahl
The Danish Team
Hi Leif,
Hi,
Pootle seems to be very slow, unresponsive or even not available today.
This is very unfortunate now that we are busy translating 4.4.
I do not experience that, for me it's running normally at the moment.
May be it becomes a bit slow when people download or upload large files.
Are you translating on Pootle or out of it?
Cheers
Sophie
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.
Cheers,
Leif
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