In T11070#237886, @dkazakov wrote:

Well, I'm not a translator. I just tried the first commercial tool google suggested me and it supported compilation. I don't know if weblate supports that (perhaps it does). I just wanted to add a requirement to the list. I believe, compilation of .mo files is almost a mandatory feature for the user. Installing gettext and compiling translation files on non-linux systems is not an acceptable solution.

In T11070#230950, @ltoscano wrote:

We have a tool to update the POT files in the master branch, where about updating the PO, we want Weblate to take care of it – simply because we have decided that Weblate should be authoritative for PO files.

I understand that, but here it's different and no tool (including Weblate) should be the authoriative for PO files: the bare repository (now SVN, let's see in the future) should be the source.

In T11070#230948, @ltoscano wrote:

I agree it's useful when you don't have tooling for it, but as I said, this (update POs with newer POTs) should happen and will continue to happen outside weblate (or any other such tool).

In T11070#230929, @ltoscano wrote:

As I mentioned – POT files are updated externally and are pushed into the GIT, as the unique place to which they belong.

Weblate then automatically takes care of updating PO files according to templates. There probably does not give much reason for this step to be solved by each team individually / manually. Therefore, it seems like a good idea when this is done automatically in Weblate.

Just for the record: our current automation already does it (for the last 15+ years).

In T11070#230929, @ltoscano wrote:

In T11070#230928, @slavekb wrote:

In T11070#230898, @ltoscano wrote:

In T11070#230894, @slavekb wrote:

If you find it useful, I can mention the experience of using Weblate for a project that is very similar to the scope of translations – Trinity Desktop Environment – see TDE Weblate.

It's a tool people are very aware of, and probably one of the best candidate. That said, it's not just "install and it magically integrates in the existing infrastructure". Which again, does *not* mean it won't
be implemented.

Yes, of course, it doesn't solve integration by waving a magic wand – it takes effort. However, it can be beneficial for process automation.

For example, for TDE:

PO file management is now the sole responsibility of TDE Weblate. Outside TDE Weblate is an automated update of POT files that are pushed into TDE Gitea. Thanks to the webhook, an update is triggered in the TDE Weblate. And TDE Weblate will update each PO file, which is pushed back into TDE Gitea.

This is the easy part, but I'm not sure I want to delegate to tool the full handling of the templates and translations. The source should be external, and the tool just use that, but not being the reference place. This also because some teams may decide to opt out from the web tool, and because we still need to perform low level operations on the translations if needed.

In T11070#230898, @ltoscano wrote:

In T11070#230894, @slavekb wrote:

If you find it useful, I can mention the experience of using Weblate for a project that is very similar to the scope of translations – Trinity Desktop Environment – see TDE Weblate.

It's a tool people are very aware of, and probably one of the best candidate. That said, it's not just "install and it magically integrates in the existing infrastructure". Which again, does *not* mean it won't
be implemented.

And having a better tool doesn't guarantee it either. BUT. It enables people who want to put in the work to be able to do the work without a huge overhead.

If you find it useful, I can mention the experience of using Weblate for a project that is very similar to the scope of translations – Trinity Desktop Environment – see TDE Weblate.