Using Weblate
#1
You can sign up at Weblate either using Google, Facebook or Github.
We don't collect any informations at all.
https://kodi.weblate.cloud/accounts/register/

If you don't have any of those accounts, please PM me your email adress. Then I'll send you an invite to the system.


Profile tips and informations are here: https://kodi.wiki/view/Translations#Profile

Translation tips and informations are here: https://kodi.wiki/view/Translations#Tran...components


Please use this thread for any questions on how to use the system.
Reply
#2
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
forbidden, read-only, terminology
but probably should be
read-only, terminology
.
Do I get the glossary usage wrong?
Reply
#3
EDIT: 
I think you're right about your example.

You can read details about glossary terms in the post below.
Reply
#4
Info on glossary terms: https://docs.weblate.org/en/latest/user/...sary-terms
Reply
#5
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".
Reply
#6
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
Reply
#7
(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
forbidden, read-only, terminology
but probably should be
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.
Reply
#8
(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?
Reply
#9
Using Weblate:

Where are the strings used in the WELCOME SECTION ? The WELCOME wizard we can see after a new fresh installation please.
Reply



Logout Mark Read Team Forum Stats Members Help
Using Weblate0
This forum uses Lukasz Tkacz MyBB addons.