Bug 34994 - Consider translations in updatedatabase
Summary: Consider translations in updatedatabase
Status: RESOLVED DUPLICATE of bug 24712
Alias: None
Product: Koha
Classification: Unclassified
Component: I18N/L10N (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-10-05 19:19 UTC by Caroline Cyr La Rose
Modified: 2024-05-03 14:49 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Caroline Cyr La Rose 2023-10-05 19:19:15 UTC
I wanted to open the discussion on this subject. Currently, when we insert things in the database using db_revs or updatedatabase, the strings are inserted in English. For a lot of things, like database structure changes and that type of stuff, it's fine. But for new letters, authorized values or additional content, it inserts in English no matter what the language of the installation is.

That means that when we update Koha, we have to go in and translate all of those new things in the interface.

We already translate the strings for new Koha installations through the translation of yaml files.

I was wondering if it was somehow possible to use the yaml files and their translations to insert the new values?
Comment 1 Caroline Cyr La Rose 2023-10-05 19:24:31 UTC
We have 60+ Koha installations, that means a lot of translating work when we update our clients. (Or a lot of unhappy people when they find a letter or authorized value in English in the cases where we didn't spot all of them.)

For 23.05, I went through all the dbrev files and made an SQL file that goes in and changes the authorized values, letters and additional content that were added with the translated strings. (In addition to having already translated the strings in Pootle.)

I'm probably not the only one in this situation and I'm sure there is a more elegant way of managing this.
Comment 2 Katrin Fischer 2023-10-05 21:00:34 UTC
> For 23.05, I went through all the dbrev files and made an SQL file that goes
> in and changes the authorized values, letters and additional content that
> were added with the translated strings. (In addition to having already
> translated the strings in Pootle.)

We have a very similar approach for updates. It would be nice if the changes could be included somehow or even part of the translation system.
Comment 3 Caroline Cyr La Rose 2024-02-14 20:45:19 UTC
Just a follow-up that my SQL file solution did not really work, as db revs are in perl and consider more things... I was just inserting or updating, but I did not consider all situations.

One of our developpers transformed my SQL into perl, we'll see on our next upgrade if it works, but I'd really like to have a more global solution...
Comment 4 Caroline Cyr La Rose 2024-05-03 14:48:21 UTC
*** Bug 24712 has been marked as a duplicate of this bug. ***
Comment 5 Caroline Cyr La Rose 2024-05-03 14:49:24 UTC

*** This bug has been marked as a duplicate of bug 24712 ***