[FIX] partner_multi_relation: Translation string couldn't be parsed correctly using str.format KeyError('kategori') issue

[yankinmax]

This fix is needed to stop having pre-commit failing on other PR's.

• [17.0][MIG] partner_address_split: Migration to 17.0 #1774

[gurneyalex]

I'm fine with the change but it has to be implemented through weblate, because the post merge scripts will revert the translations (unless I'm mistaken, maybe @sbidoul can confirm)

I made the change in weblate -> it should sync in a few hours.

[yankinmax]

@gurneyalex for me more important is to merge approved:

• [17.0][MIG] partner_address_split: Migration to 17.0 #1774
  If it can be merged without this fix I'm completely fine. Can it?

[gurneyalex]

It can't be merged now the CI will be red, and the oca bot will refuse to merge.

I've just changed the translation in the weblate UI, it should get merged in the next run of the cron, at which point the issue will be fix. Let's check this again tomorrow.

[gurneyalex]

677e517 fixed the issue

[sbidoul]

I'm fine with the change but it has to be implemented through weblate, because the post merge scripts will revert the translations (unless I'm mistaken, maybe @sbidoul can confirm)

@gurneyalex weblate will not revert translations but may get into a git merge conflict if there are ongoing translations at the same time, and such merge conflicts are painful to resolve. That is why we strongly discourage pushing translations via git, but it can be done in some circumstances.

[sbidoul]

BTW, we should enable more checks in weblate to avoid these translation errors: OCA/oca-weblate-deployment#12