-
-
Notifications
You must be signed in to change notification settings - Fork 959
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 (as tbx) under source control (as git) #2122
Comments
I submitted this feature request, since I couldn't figure out this being possible (may I missed something?) |
It's currently not possible, but it's possible to implement this. |
nijel
changed the title
feat: glossary (as tbx) under source control (as git)
Glossary (as tbx) under source control (as git)
Jul 24, 2018
nijel
added a commit
that referenced
this issue
Jan 18, 2021
nijel
added a commit
that referenced
this issue
Jan 29, 2021
nijel
added a commit
that referenced
this issue
Jan 29, 2021
nijel
added a commit
to nijel/weblate
that referenced
this issue
Feb 4, 2021
nijel
added a commit
to nijel/weblate
that referenced
this issue
Feb 4, 2021
nijel
added a commit
to nijel/weblate
that referenced
this issue
Feb 4, 2021
nijel
added a commit
to nijel/weblate
that referenced
this issue
Feb 4, 2021
Thank you for your report, the issue you have reported has just been fixed.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Actual behaviour
In the glossary management section
project/glossaries/Language
it is possible to manually import a glossary file (as tbx) and also to manually export.Expected behaviour
Have glossary(ies) under source management, similar to components. Allow to specify a repository (as e.g. git), including same features as possible for components as
The text was updated successfully, but these errors were encountered: