Importing glossary from CSV with comments
Describe the issue
Importing glossary from csv does not add "developer_comments" I know it's a different file format. Import from csv works, adds / updates "source", "target", "context" At the moment it is not possible to import a glossary with recently added enhancements. Weblate 4.5dev latest image bleeding dockerhub
Right now this is expected behavior (it matches how translation import works). But it makes sense to extend it. How do you import the glossary?

I created a regular component from csv files. I downloaded the translations as .tbx and imported them as glossaries.
This issue has been added to the backlog. It is not scheduled on the Weblate roadmap, but it eventually might be implemented. In case you need this feature soon, please consider helping or push it by funding the development.
Has there been any progress on this? Is there anything I could do to contribute towards a solution?
I'm currently importing a bunch of glossary terms where the developer_comments value is important, so I'd love for this to work!
Equally important to me though is the translator_comments value, if this is indeed the value that corresponds to the other "Explanation" field. Is this actually the case though? It doesn't seem to have been exported when I download a .csv
We are experiencing the same problems using the CSV export/import function. When using "context" it just displays the "context" from the "source language".
We have such developer/translator comments per language, which would be nice to import it that way.
Using XLIFF to export English, adapt it to German also does not import the developer comment:
After import:
Would be nice when there would be any way to import the comments.
Also other formats like TBX which should support the flags and comments are not exported.
https://docs.weblate.org/en/latest/formats.html#translation-types-capabilities
I'm out of ideas how to work around this.
TBX improvements are covered by https://github.com/WeblateOrg/weblate/issues/12795. If you have other suggestions for TBX please open a separate issue and keep this for CSV only.