Glossary translation explanation mapping is broken

[pavelhoral]

Describe the issue

We are using TBX glossary and there is a bug when the TBX gets updated and Weblate pulls changes from the repo.

When we add new glossary entry in Weblate, the explanation is written as <descrip> for source unit explanation and as <note from="translator"> for target unit explanation.

However when we modify TBX in the VCS and pull the changes, everything from the TBX file gets mapped to note column in the database. So we end up with duplicate explanations that can not be deleted via UI.

I already tried

• I've read and searched the documentation.
• I've searched for similar issues in this repository.

Steps to reproduce the behavior

1. Create new translation project
2. Create glossary component
3. Add new glossary entry with source string explanation
4. Push to repository
5. Make new commit in the repository by changing glossary translation
6. Pull changes to Weblate (update from repo)
7. Observe duplicate explanation that can no longer be edited

Expected behavior

Source string explanation and translation explanation should be mapped to explanation only and note should no longer be used.

Screenshots

Exception traceback

No response

How do you run Weblate?

Docker container

Weblate versions

4.18.1

Weblate deploy checks

No response

Additional context

No response

[github-actions]

The issue you've reported needs to be addressed in the translate-toolkit. Please file the issue there, and include links to any relevant specifications about the formats (if applicable).

[nijel]

Ah, translate-toolkit sets the from attribute note when saving this, but does no filtering when reading. Needs to be fixed there.

[pavelhoral]

Ah, translate-toolkit sets the from attribute note when saving this, but does no filtering when reading. Needs to be fixed there.

Should I create the issue there? I am not sure I understand the cause you've described.

[nijel]

Should be fixed by translate/translate#4955 and #9485

[github-actions]

Thank you for your report; the issue you have reported has just been fixed.

• In case you see a problem with the fix, please comment on this issue.
• In case you see a similar problem, please open a separate issue.
• If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.