Open thosgood opened 2 years ago
You can add gender as an explanation, that way the information will be shown in the glossary sidebar.
The Crowdin glossary has markup for distinguishing between nouns/verbs from what I remember.
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!
Part of speech for glossary entry may be needed first?
Not sure if it is related: #3023
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!
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.
You can add gender as an explanation, that way the information will be shown in the glossary sidebar.
Users tend to also mark these as terminology, so it pollutes the glossary of languages that don't have gender / plural differences.
The best solution would be to support multiple values per entry. This is already supported for CSV, and TBX format could handle that as well.
You can add gender as an explanation, that way the information will be shown in the glossary sidebar.
But it will not help finding the gendered/plural terms, right? Maybe I am missing something, but is there a way for the glossary entry for "asset" to appear in the sidebar if the text I want to translate contains the word "assets"?
Presently, you can do this with via variants (see https://docs.weblate.org/en/latest/devel/translations.html#variants), but it's not really comfortable.
@nijel Thanks, but I think that would really pollute our glossary. Having extra entries with redundant translation information is an invitation to chaos. But since you mentioned that there might be an option for multiple values per entry, that sounds like a good intermediate solution for #3023.
Do you think this is in the cards in the foreseeable future?
Presently, it would be reasonably easy to add multiple translations to a single term.
Having multiple terms for the source string is more tricky. The format itself doesn't support that, so it would have to be emulated somehow by Weblate.
@nijel Thanks for your feedback.
Having multiple translations for a term would help reduce redundancy a bit, if some of these could still be marked as "forbidden". Speaking for myself, it's not a pressing issue though.
If the real issue of multiple source alternatives is too tricky or too hacky to implement, I'm fine waiting for morphology support (#3023), but I have no idea how hard that would be to implement.
Describe the problem
In the glossary for my project (multilingual mathematical texts), I would like to be able to record the (grammatical) gender of nouns, as well as their plural forms. That would mean that, when translating strings in other components, the glossary would be more useful in ensuring that the translation is correct.
Describe the solution you'd like
Some way of recording grammatical gender of entries (since all my entries are nouns) in the glossary. Some way of recording plural forms of nouns as well.
Describe alternatives you've considered
I currently have a .json file (https://github.com/thosgood/maths-dictionary/blob/master/nouns.json) that I'm trying to "import" into Weblate, and this file records gender of nouns.
Screenshots
No response
Additional context
No response