MPV Easy Player 0.330.12 - Multilanguage GUI issues

[bovirus]

@422658476

There are some issue regarding multilanguage GUI Pelase check screenshots.

[422658476]

The options in the setting drop-down menu are in English no matter what language, because the content of the options is exactly the same as the value set by mpv, and it is not translatable by default. Video(1)、Other(1) and audio(1) are correct in themselves, because if there is a second tab page that is video(2)、Other(2), audio(2), this should also be found and translated in the translation file. osc(A), osc(1), osc(2) are English abbreviations, the meaning of this abbreviation has been described in detail in osc(A), osc(1), if translated into other languages, then other settings will use this The abbreviations must be revised, so it is recommended to maintain the status quo without translation. The names osc(A), osc(1), and osc(2) are also correct, because osc(A) is for mpv-easy borderless gui, and osc(1) and osc(2) are for mpv native gui. It needs to be distinguished in this way. For the remaining untranslated parts that are circled, do you update the language file to me or need me to do other operations, because these untranslated parts should be in the translation file you provided to me. Thank you so much for the feedback

[bovirus]

@422658476

I checked italian language files and is 100% translated. In previous MPV Easy Player version (0.33.0.11) most of the strings were translated.

Then probably some strings are changed in source files. Please check and update language files.

Thanks.

[422658476]

Okay, I will download the language file you provided to me last time and process it again to see if there will be any changes. Many thanks

[422658476]

I downloaded language.zip again I first found the first place that was not translated, but please see the screenshot, this seems to have not been translated into Italian. I am looking for other parts that have not been translated. Please help me to reconfirm whether the language file is translated. Many thanks

[422658476]

It should be that these parts were missed in the translation, I found a few others, the Italian translation is also in English

[422658476]

It seems from your last message that the translation of the setting interface is not 100%

==================================

This is the first step of italian language files. EasyGUI 100% translated. Easy Settings is not 100% translated but most of them. Optimized fiels after a long test about GUI in place. Please rename them (github repository need anotehr langaueg file name then application), load in your system and run lupdate to align this file to yoiur source.

What's the meaning of "[Cycle]" in translation?

======================================

[bovirus]

@422658476

The error/misudnerstanding was all strings are marked as green. Then is not so easy to check if somethings changes becasue are all always green. Then for each new translation I have to check from first line which line are translated and other not.

On QT standard the lines with changes are marked with yellow tick (no green tick).

[422658476]

The problems you encounter are easy to encounter when translating. Then I wait for you to update the language file to me, thank you very much. You can get the latest language files (*.ts) in the language file, they have been synchronized by me, just modify them. Many thanks.

[bovirus]

@422658476

Could be interesting when you will update the .ts files if you can mark new/changed strings with yellow tip (instead green tick).

Are you using lconvert/lrelease QT SDK tool?

[422658476]

Usually qt linguist detects the difference is red, only when the qt linguist feels that the translation is biased will it be a yellow mark.

I have been using lupdate and lrelease in qt linguist and qt creator

[422658476]

The problem now is that the part of the Italian file that should be translated into Italian is not a vacancy, but is filled with English, so this is not detectable and marked as red. It can only be manually confirmed. It may be because you have previously It was caused by first filling in English and then modifying it to Italian. Otherwise these untranslated parts should be blank.

[bovirus]

@422658476

I found a solution. With lconvert I converted .ts file in .po file. With POEditor I marked the 47 strings currently in English as fuzzy strings (not checked) using "CTRL+U" and I saved the .po file. Then with lconvert I converted .po file (with fuzzy strings) in .ts file. Now the .ts file show me with yellow ? the strings to check (fuzzy).

Thanks.

[422658476]

Google Translate does not translate the meaning very well, so I can't understand what you mean, but I don't recommend it. Using the qt tool, I will only save files in two formats, ts and qm. If you want to find all the parts in Italian that are not translated and are now in English, you only need to use a text comparison software (such as beyone compare) to compare English .ts and Italian .ts. The same part of the two files is untranslated. The Italian part, because the text of these parts in the two files are the same. If you don't have such software, I can give you a screenshot of the comparison result.

[422658476]

Text comparison software doesn't work at all, omg.

[422658476]

I modified the ts file and added extra [xxxxxxx] characters to the English translation part of the Italian file. You only need to use qt linguist to open the ts file, use the search function to search for xxxxxx, then the searched content is The not translated part. You just need to keep searching for the next one until the end. Hope this can help you. Finally, if some parts are still unchanged, the existing xxxxxx characters need to be removed manually. it.zip

[bovirus]

@422658476

Sorry but I didn't understand because you cannot translate simple words like

GUI mode -> Execution mode -> Priority -> idle/belownormal/normal/abovenormal/high/realtime (are translated but showed in english) Video -> Discard frames -> vo ???? what's this word? Video -> Decoding mode? auto-safe/ auto-copy Video -> Disable video adapting -> no/yes/downscale-big (are translated but showed in english) Audio -> Audio channel -> auto-safe OSC - OSC (A) _>Box style -> box/box-original/slimbar/webplayer/one-to-one/1-2-1 OSC -> OSC (A) -> Sekking bar style -> bar/bar-alpha/line/line-alpha OSC -> OSC (B) -> OSC display mode -> auto OSC -> OSC (B) -> OSC stile -> bar/bar-alpha/line/line-alpha OSC -> OSC (2) -> Seeking range style -> inverted OSD -> OSD (1) -> OSD axis position -> left/center/right - top/center/bottom OSD -> OSD (1) -> Show with OSD durinmg seek -> left/center/right - no/bar/msg/msg-bar

Tomorrow morning I will load complete translated file for Italian

Thanks. MPV-Easy-Player-italian-2021.08.09-17.54.59.zip

If you want to test this the late build of italian .ts language files (not 100% translated - 19 string not checked/translated).

[422658476]

The options in the drop-down menu are very easy to translate from the translator's point of view, just convert the word into another word. But from a programming point of view, this is very difficult, because these options must be consistent with what mpv can read, and mpv can only recognize the corresponding options in English. If you translate it into other languages, read and write These values ​​will be very complicated and error-prone. For example: there is a setting in the setting file size=aaa #Optional values ​​include: aaa, bbb, ccc. When you translate aaa, bbb, ccc into jjj, kkk, LLL, the problem arises. When the code reads the value of size from xxx.conf, it must first determine whether it is one of aaa, bbb, or ccc. If it is aaa, set the value in the drop-down menu to aaa. But after translation, the value in the drop-down menu has changed to jjj, kkk, LLL (translation is read before setting). If the read value is aaa, then the corresponding value in the drop-down menu is jjj at this time, and you must write a piece of code. When the value is aaa, set the value of the drop-down menu to jjj. The same is true when saving. If the current option is detected as jjj when saving, then a piece of code needs to be handwritten. When the value is jjj, the size value in xxx.conf is set to aaa. This is just a switch between two languages, which is quite scary. In fact, there are more problems, so keeping only the English option is the best choice. I don't know if Google Translate can translate these translations for you to understand.

[bovirus]

@422658476

Ok. Thanks for the explanation.

[422658476]

I may have some problems with the operation of pull requests. If it does not meet expectations, please submit an issue again, because I am completely unfamiliar with this. However, after I synchronized the Italian language and converted it to qm files, the parts that were not translated before became Italian. I believe there should be no problem with pull requests. I will close this issue, and the latest Italian translation will be used in the next version (maybe 1 month).