-
-
Notifications
You must be signed in to change notification settings - Fork 977
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Glossary import and export with explanations #5519
Comments
This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger. In case your question is already answered, making a donation is the right way to say thank you! |
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. |
I've just released https://github.com/translate/translate/releases/tag/3.9.0 that makes this possible. |
Excellent. Thank you! |
Supported for TBX only right now for glossaries. Fixes WeblateOrg#5519
Supported for TBX only right now for glossaries. Fixes WeblateOrg#5519
Supported for TBX only right now for glossaries. Fixes WeblateOrg#5519
Supported for TBX only right now for glossaries. Fixes #5519
Thank you for your report; the issue you have reported has just been fixed.
|
This is not a bug, but more a support question and/or feature request.
Again, I want to stress how great this new enhancement of Glossary is and I understand that a lot of effort went into it already.
In our case, we regularly import and export Glossaries into and from Weblate.
So the question is now
and
Any plan to "fix" 1) and to perhaps implement a solution for 2)
Thanks a mil.
The text was updated successfully, but these errors were encountered: