Hi Victor,

you're right, both solutions will help resolve the situation. Assuming there is an access to the .po files on the server. Some of our translators don't have the necessary knowledge to be able to use ssh and fix .po files directly using the command line. Yet, they are able to work on the translation and do it efficiently and well. Generating .po files would help in just such specific cases. It would be a useful feature, but we can probably get by without it. It's just that the problem won't be able to be solved directly by the person who caused it, but by someone else who can do it directly on the server.

Bye for now

Michal

po 30. 5. 2022 v 21:32 odesílatel Victor Grousset/tuxayo <victor@tuxayo.net> napsal:

On 22-05-25 15:01, Mike D. wrote:
> If we manage to break some translation and thus the
> interface, we would need a hot fix option. Would there be any way to
> arrange on-demand .po generation of a specific Koha version and
> language? For example, some button in Pootle that only the Language
> Manager would have the right to use? It would help us a lot in crisis
> moments, especially before a new release.

For the hotfix cases, would it work to add in your workflow a step to
manually fix the .po file with a text editor or Poedit after downloading it?
Or to rollback to the previously deployed .po files until the next day?

Cheers,

--
Victor Grousset/tuxayo