Login at Kodi Home

roliverosc · (This post was last modified: 2020-02-01, 22:55 by roliverosc.)

I am sorry to announce that the bug was my fault, download the translation file to make some tweaks more easily but when uploading it, they showed up with some strange characters. I have tried to solve everything that is visible to the naked eye. but of course there are things that are not shown as after they are running the program. I admit my mistake. But now I dare not touch it again. @myron how can we fix it?

boblo · (This post was last modified: 2020-02-02, 15:58 by boblo.)

(2020-02-01, 22:55)roliverosc Wrote: I am sorry to announce that the bug was my fault, download the translation file to make some tweaks more easily but when uploading it, they showed up with some strange characters. I have tried to solve everything that is visible to the naked eye. but of course there are things that are not shown as after they are running the program. I admit my mistake. But now I dare not touch it again. @myron how can we fix it?

If you want, I can help you with the text encoding. Just send me a link to the file in a private message and I'll check it out. I have some experience translating PO files (I have translated the K desktop environment for GNU/Linux and other systems in the past and now the Netflix and HBO Go addons).

roliverosc · 2020-02-02, 19:51

Only you have go to https://hosted.weblate.org/projects/tinymediamanager/

boblo · (This post was last modified: 2020-02-02, 20:55 by boblo.)

(2020-02-02, 19:51)roliverosc Wrote: Only you have go to https://hosted.weblate.org/projects/tinymediamanager/

Ok, I have already downloaded the file as a PO text file. The file encoding is OK, UTF-8 with Unix style (only a line feed character per line, without carriage returns). This is standard. I don't see those "extra hyphens".
Are you sure the hyphen issue is your fault? I think @myron is right:

Quote:Although the translation is set to UTF8, we got an UTF16 "t" with a silent whitespace hyphen before (not visible in GUI)
We fixed the output translation for next release.

Make sure you select the proper encoding (UTF-8) when uploading again the file to Weblate. Hope this helps.

EDIT: Can I test the new translation with my TMM setup? if so, how?

Edit 2: Please don't use 'raspador' for 'scraper', use 'extractor' instead. Keep in mind the word 'scraper' has several meanings and I think this is the most suitable, don't you?

roliverosc · (This post was last modified: 2020-02-03, 00:32 by roliverosc.)

Thanks for watching, also "scraper" is already corrected and changed. I had been thinking about changing that for a while.

myron · 2020-02-03, 09:42

np.
Should be all fine now.

Local editing and uploading a complete file... is not so a good approach.
Editing this online is the preferred solution, since we do not know how many users are translating the same time...
Else you would overwrite someones changes i guess....
(Beside the encoding problems you might run into)

Testing local changes is not so easy in v3, as the translations are packed into the tmm.jar.
Will think about it...
(workaround: A jar is a zip, and after renaming you should be able to extract/update the messages*.properties ;)

boblo · 2020-02-03, 16:25

(2020-02-03, 00:30)roliverosc Wrote: Thanks for watching, also "scraper" is already corrected and changed. I had been thinking about changing that for a while.

Thanks. Did you see my suggestions? I have not changed anything of your work, only suggested some corrections, since Weblate allows users to suggest alternative translations.

dcyxxt · 2020-02-12, 05:22

no Chinese simaple option...only Chinese traditional