Hi Victor,

Of course we have access to the servers. The way it works now (daily generation of .po files) it works great. It's all about roles and responsibilities in the team. The people who are in charge of translation are often librarians who work with Koha on a daily basis and know the library processes as well. They are therefore in the best position to produce a translation they will understand. They and other librarians. What they don't know are servers, ssh and .po files. So if they need to change something, they have to ask another person to do it. This can reduce efficiency and even a trivial fix can take many times the amount of time. Generating .po files on demand would help us solve this problem. This is just a suggestion to think about. If it doesn't make sense to others, we are happy with the status quo and will deal with it somehow.

Thank you.

Michal

st 1. 6. 2022 v 4:13 odesílatel Victor/tuxayo <victor@tuxayo.net> napsal:

On 22-05-30 21:42, Mike D. wrote:
> 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.

Doesn't your normal workflow already requires access to the server?
Like when it's generated everyday you have a way to apply it immediately
on the server without waiting for the monthly release.

--
Victor/tuxayo