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
Users should not be able to add entries to other languages' glossaries by default #8807
Comments
This issue has been automatically marked as stale because there wasn’t any recent activity. It will be closed soon if no further action occurs. Thank you for your contributions! |
Has this ever been a problem? |
This issue has been put aside. It is currently unclear if it will ever be implemented as it seems to cover too narrow of a use case or doesn't seem to fit into Weblate. Please try to clarify the use case or consider proposing something more generic to make it useful to more users. |
@comradekingu Yes, on The Document Foundations's Weblate this happens every now and then. I just deleted some unwanted entries yesterday. It's not a huge problem though, but IMO what I propose would be a better default. |
@tjhetala Pretty sure I am one of the people doing it for the source language. Similarly, between good entries and bad entries in the glossary, the benefit greatly outweighs the detriment. |
There are two situations that could be a problem. First, some glossaries only make sense in a specific language. For example, German users might create two glossaries for "lion", one for the male version "der Löwe" and one for the female version "die Löwin". This does not make sense for languages that don't have such grammatical gender. Second, "Auto-adjust context when an identical string already exists." is on by default too. So I regularly see different versions of the same string with auto-generated context like "1". That's is so frustrating to maintain. I guess it's because some languages created a non-terminology glossary:
|
Apparently it's currently also possible to add the "forbidden" flag to other languages' glossaries by default, see: https://translations.documentfoundation.org/translate/libo_ui-master/glossary/fi/?checksum=6a157b0604755bd8 IMO this should not be allowed by default either. |
@comradekingu I don't see how banning users would be preferable over setting good defaults. I think the people doing these changes are by and large doing it by accident, i.e. they don't know they're affecting other languages' glossaries. |
@tjhietala I disagree that limiting potential for getting work done is a good default to prevent harm. Weblate is IMO a better platform because of default openness and good functionality to deal with that, If the problem arises from it being difficult to gauge what dictionary the user is editing and why, that is the problem to solve. Having the same problem for fewer users is largely the same problem. If malice is what I want to do, changing the glossaries when the translations are wide open without quality-reaffirming tools is not what anyone clever enough to do real damage would attempt. Where are the examples of what went wrong, and maybe we can work from there to avoid the confusion? |
@comradekingu I don't think there's any malice involved. Like I said, my guess would be that these users think they're modifying the glossary for one language and don't realise they're doing it for other languages as well. |
I spend a lot of time removing unwanted entries from my glossaries added inadvertently by other translators not in my language teams. They use other capitalization conventions, and I have to go through them one by one. So yes, it is annoying. |
Describe the problem
Currently, if a user has the rights to add a glossary entry, they can add it for every language by checking the "Terminology" check box. I don't think this is good default behaviour for Weblate. Yes, the unneeded entries can be deleted, but it's an unnecessary annoyance.
Describe the solution you'd like
The "Terminology" check box should be disabled by default, except for managers (or possibly also reviewers, if deemed necessary).
Describe alternatives you've considered
No response
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: