Maybe more a comment than a question.
There are 3 types of flags at Weblate: terminology, forbidden, and read-only. As far as I understand, both read-only
and forbidden flags are not supposed to be used on a glossary term because forbidden is supposed to be used with erroneous or confusing translations. For example,
AAC is now
html:
forbidden, read-only, terminology
but probably should be
html:
read-only, terminology
.
Do I get the glossary usage wrong?
EDIT:
I think you're right about your example.
You can read details about glossary terms in the post below.
Are
source reviews enabled? How can I report an erroneous source string?
E.g. I believe
Kodi GIT should be Kodi Git, as Git (if it is the VCS) is not an acronym. Or "Kodi media center" in en_gb should be "
media centre".
Source reviews are not enabled at Weblate, as I doubt anyone from the team will read them.
You probably have most luck reporting erroneous source strings here in the translations forum or at Github:
https://github.com/xbmc/xbmc/issues
(2021-07-25, 01:01)homocomputeris Wrote: [ -> ]Maybe more a comment than a question.
There are 3 types of flags at Weblate: terminology, forbidden, and read-only. As far as I understand, both read-only and forbidden flags are not supposed to be used on a glossary term because forbidden is supposed to be used with erroneous or confusing translations. For example, AAC is now html:
forbidden, read-only, terminology
but probably should be html:
read-only, terminology
.
Do I get the glossary usage wrong?
Not an expert, but my take is that 'forbidden' should very well be used in the glossary to show the translators how NOT to translate terms. I have no idea what Weblate makes out of that flag. It would be great if Weblate would flag translated strings containing forbidden phrases as 'to check' or refuses to save them or the like.
I also added read-only phrases to the glossary to show translators the phrases which must not be translated.
I'm not 100% sure what 'terminology' is good for. I thought everything added to the glossary would be terminology.
EDIT: Re AAC I'm with you. Should have read-only and terminology set, but not forbidden. Forbidden imo means that AAC must not appear anywhere in the translation which is definitely not what we want here.
(2021-07-14, 19:02)queeup Wrote: [ -> ] (2021-07-14, 18:57)Gade Wrote: [ -> ]However, there is a way:
You can select the language, click "Tools" > "Bulk edit".
Select "Strings waiting for review" and State to set: Approved.
Apply.
Unfortunately I don't have that option. Maybe something about permission issue.
Is there any news about bulk approve issue?
Using Weblate:
Where are the strings used in the WELCOME SECTION ? The WELCOME wizard we can see after a new fresh installation please.
At Weblate, for many strings I get
Quote:Inconsistent
This string has more than one translation in this project or is untranslated in some components.
which refers to
Quote:The following string has the same context and source.
Kodi core/kodi main (Matrix)
Propagated
Translated
However, when I try to fix it by opening the URL for
Kodi core/kodi main (Matrix), I get:
Quote:Page Not Found
The page you are looking for was not found. The project you are looking for does not exist or is not publicly available.
And also I cannot 'Apply selected translation to all propagated strings'.
How do I deal with it? Do I need access to
Kodi core/kodi main (Matrix)?
Kodi core/kodi main (Matrix) is only available to admins.
Translated strings for all languages are copied from Kodi main (Nexus) to Kodi main (Matrix).
This is for Russian?
I have fixed most issues in Kodi main and Kodi main (Matrix)?
Is there something more I can do to help?
Okay, I see.
Yes, it is for ru.
Thanks! Now that I know it's a feature and not a bug, that's all for now I believe.