Hi Bernardo, you've described exactly the procedure we use. Today I was chatting on IRC with Cait and we were unable to find out how often the .po files are generated. For Koha 21.11, which I am now actively translating, the generation occurred on Friday 6/5 and today 9/5. Does this mean that the script does this every day? Or is the frequency different? We have a script that downloads .po files from Pootle (for example https://translate.koha-community.org/export/21.11/cs/) and replaces the files on our Koha server disk. For this to work well though, we need to know how often the files in /export/version/cs change. Ideally this would be once a day. That would be perfect. Thank you Michal po 9. 5. 2022 v 19:07 odesílatel Bernardo Gonzalez Kriegel < bgkriegel@gmail.com> napsal:

Hi Michal,

we are working on how to efficiently fix (hotfix) translations on

...

production servers with Koha. Generating .po files on package release seems slow to us. For active languages, would it be possible to generate .po files more frequently, e.g. daily? This would help us a lot.

one possible workflow would be to translate on the translation server, and then download the updated translation files to replace the ones that come in the packages.

For example, for version 20.05 and CS language, the files can be downloaded from https://translate.koha-community.org/export/20.05/cs/ and used to replace the ones at /usr/share/koha/misc/translator/po/

Is that possible?

Bernardo

Hi Bernardo, Thank you very much for this enhancement. It will save us time and simplify our translation work. I believe it will work great. If I run into any problems, I'll let you know. Thanks again. Have a good day Michal KohaCZ po 9. 5. 2022 v 21:41 odesílatel Bernardo Gonzalez Kriegel < bgkriegel@gmail.com> napsal:

Hi Michal, there was no specific moment for the update of the exported files, normally when we need to *sync* the files before adding a new project, or every time a release maintainer needs to update the translation files before a release.

I have added a cron job to sync the files once a day at 00:00 UTC.

Bernardo

-- Bernardo Gonzalez Kriegel bgkriegel@gmail.com

On Mon, May 9, 2022 at 2:46 PM Mike D. <black23@gmail.com> wrote:

...

Hi Bernardo, you've described exactly the procedure we use. Today I was chatting on IRC with Cait and we were unable to find out how often the .po files are generated. For Koha 21.11, which I am now actively translating, the generation occurred on Friday 6/5 and today 9/5. Does this mean that the script does this every day? Or is the frequency different? We have a script that downloads .po files from Pootle (for example https://translate.koha-community.org/export/21.11/cs/) and replaces the files on our Koha server disk. For this to work well though, we need to know how often the files in /export/version/cs change. Ideally this would be once a day. That would be perfect. Thank you

Michal

po 9. 5. 2022 v 19:07 odesílatel Bernardo Gonzalez Kriegel < bgkriegel@gmail.com> napsal:

...

Hi Michal,

we are working on how to efficiently fix (hotfix) translations on

...

production servers with Koha. Generating .po files on package release seems slow to us. For active languages, would it be possible to generate .po files more frequently, e.g. daily? This would help us a lot.

one possible workflow would be to translate on the translation server, and then download the updated translation files to replace the ones that come in the packages.

For example, for version 20.05 and CS language, the files can be downloaded from https://translate.koha-community.org/export/20.05/cs/ and used to replace the ones at /usr/share/koha/misc/translator/po/

Is that possible?

Bernardo

Hi Bernardo and community, daily generation of .po files works great. However, we did run into one limitation. 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. Thank you Michal po 9. 5. 2022 v 21:46 odesílatel Mike D. <black23@gmail.com> napsal:

Hi Bernardo, Thank you very much for this enhancement. It will save us time and simplify our translation work. I believe it will work great. If I run into any problems, I'll let you know.

Thanks again.

Have a good day

Michal KohaCZ

po 9. 5. 2022 v 21:41 odesílatel Bernardo Gonzalez Kriegel < bgkriegel@gmail.com> napsal:

...

Hi Michal, there was no specific moment for the update of the exported files, normally when we need to *sync* the files before adding a new project, or every time a release maintainer needs to update the translation files before a release.

I have added a cron job to sync the files once a day at 00:00 UTC.

Bernardo

-- Bernardo Gonzalez Kriegel bgkriegel@gmail.com

On Mon, May 9, 2022 at 2:46 PM Mike D. <black23@gmail.com> wrote:

...

Hi Bernardo, you've described exactly the procedure we use. Today I was chatting on IRC with Cait and we were unable to find out how often the .po files are generated. For Koha 21.11, which I am now actively translating, the generation occurred on Friday 6/5 and today 9/5. Does this mean that the script does this every day? Or is the frequency different? We have a script that downloads .po files from Pootle (for example https://translate.koha-community.org/export/21.11/cs/) and replaces the files on our Koha server disk. For this to work well though, we need to know how often the files in /export/version/cs change. Ideally this would be once a day. That would be perfect. Thank you

Michal

po 9. 5. 2022 v 19:07 odesílatel Bernardo Gonzalez Kriegel < bgkriegel@gmail.com> napsal:

...

Hi Michal,

we are working on how to efficiently fix (hotfix) translations on

...

production servers with Koha. Generating .po files on package release seems slow to us. For active languages, would it be possible to generate .po files more frequently, e.g. daily? This would help us a lot.

one possible workflow would be to translate on the translation server, and then download the updated translation files to replace the ones that come in the packages.

For example, for version 20.05 and CS language, the files can be downloaded from https://translate.koha-community.org/export/20.05/cs/ and used to replace the ones at /usr/share/koha/misc/translator/po/

Is that possible?

Bernardo

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

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

Ok, thanks. st 1. 6. 2022 v 12:40 odesílatel Bernardo Gonzalez Kriegel < bgkriegel@gmail.com> napsal:

Hi Michal, sorry, but on-demand generation of *.po files is not an option. There is no button in pootle for that, it's an operation that is performed on the command line, or in a cron job such as the current daily generation.

Best regards, Bernardo

-- Bernardo Gonzalez Kriegel bgkriegel@gmail.com

On Wed, Jun 1, 2022 at 4:05 AM Mike D. <black23@gmail.com> wrote:

...

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