Thanks for opening that request against Lokalize to plug into Weblate's existing API. A workflow that uses Weblate to remove the need to deal with git/svn to encourage contributions from non-Computer Science types while still allowing for those who have used Lokalize to continue using Lokalize is the best way forward I feel.

I think that switching to Weblate would cause more harm than good due to:

1. slower performance
2. hit-and-run" translators

(Not bridged to Matrix equivalent rooms)
Plasma Bigscreen: https://t.me/plasma_bigscreen
Plasma Mobile: https://t.me/plasmamobile

The problem was not with tools (again). One more tool just makes the current life harder. Just look at this thread. All the problems can be solved with better team management.

In T11070#238067, @dkazakov wrote:

In T11070#237887, @slavekb wrote:

Weblate allows to download the MO file directly from the web interface. The user does not need any other tool to get the MO file.
Likewise, Weblate allows to upload a PO file if the user wants to use some offline translation tool.

Hi, @slavekb!

Perhaps you know, does Weblate supports some kind of "locking" a translation file by the maintainer of the project? Such locking would really help people like @yurchor to do bulk-translations offline.

I mean, we could make a policy that "a translator can ask to lock a specific file for not more than N days(?)" to do the translations offline safely and push them into SVN/Git. And the rest of the time the files would be available for translations by other people through web-interface.

Do you have an alternative then to the current problem of reducing barrier to contribute @ppeter ? Forgive my ignorance, but it's possible for Weblate and Git PR's to co-exist so I don't see why it wouldn't be possible for Weblate and SVN to co-exist to appease both sides.

If KDE can't provide a test Weblate server, I can front one on my own dime. A server on Linode that meets the 2 core + 2 GB recommended specs goes for $20/month.

I also translate LibreOffice and the translation Pootle instance is really laggy. (Huge project, diffrent versions as well as docs, plus many languages).

Moved to voting taskboard as it's been a week since lydia's comments concerning voting starting on Aug 15th and there have been no updates to the task. I'd rather not have this miss out on voting so I've moved it over. If anyone wants to make edits please do so, but make sure it gets moved back to the ready for voting label.

These are hard to maintain and makes it difficult to ensure consistency, etc etc (I've written my opinion on the mailing list several times).

Thanks @ngraham for catching my miss about seeing there's already a task.