Summary: | Consider translations in updatedatabase | ||
---|---|---|---|
Product: | Koha | Reporter: | Caroline Cyr La Rose <caroline.cyr-la-rose> |
Component: | I18N/L10N | Assignee: | Bugs List <koha-bugs> |
Status: | RESOLVED DUPLICATE | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | f.demians, koha, martin.renvoize, philippe.blouin |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Caroline Cyr La Rose
2023-10-05 19:19:15 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.
> 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.
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... *** Bug 24712 has been marked as a duplicate of this bug. *** |