-
-
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
Unify the two ways of adding glossary terms #10969
Labels
Milestone
Comments
Also, in the second UI, there's a checkbox titled "Auto-adjust context when an identical string already exists." which doesn't exist in the first UI and does not seem to be explained in Weblate's documentation. |
nijel
added
enhancement
Adding or requesting a new feature.
ux
Issues related to user experience.
labels
Feb 12, 2024
In that line of thinking, unifying things into adding glossary terms from the translation field would help? |
nijel
added a commit
to nijel/weblate
that referenced
this issue
Feb 13, 2024
nijel
added a commit
that referenced
this issue
Feb 13, 2024
5 tasks
5 tasks
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
Labels
Describe the problem
Currently Weblate has two UIs for adding glossary terms:
The UIs that open are similar in terms of content (most of the fields are the same) but not identical. In the first case, there's a text field called "Explanation" and a menu for selecting the glossary to add the term to. In the second case, there's a text field called "Key"(TDF Weblate 5.3.1) or "Context" (current Hosted Weblate) 5. and additionally some buttons for inserting special characters.
It's not clear whether "Explanation" is the same field as "Key"/"Context".
Describe the solution you would like
It would be better to unify the layouts and terminology as much as possible or even better, remove one of the UI altogether to avoid user confusion and simplify code maintenance.
Describe alternatives you have considered
No response
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: