Current Situation of English Support
Closed this issue · 6 comments
Ref #33 (comment)
English support has always been on my plan list. But currently, less than 50% of the progress has been completed, and a large number of configuration files need to be translated, resulting in slow progress.
But due to @aicynide malicious slander, this plan will be put on hold indefinitely.
Yup it's annoying to see people constantly ask you and @hooke007 to translate to English when they themselves can translate the entire repo by simply using the google translate extension.
Regarding your efforts to support English natively, what method are you currently using to translate files?
When I compare/test both yours and @hooke007's configs I use the google translate website to translate any files I want to read in English. It works well but iirc it can cause some formatting issues and files first need to be converted to .docx.
Maybe this could help speed up the process?
Yup it's annoying to see people constantly ask you and @hooke007 to translate to English when they themselves can translate the entire repo by simply using the google translate extension.
Regarding your efforts to support English natively, what method are you currently using to translate files?
I use this extension of vscode-google-translate in vscode for translation.
It actually works well, and currently only the comments in the configuration files in the script-opts directory have not been translated yet.
But I am unwilling to serve users like @aicynide, so English support will be put on hold.
Why don't you use chatgpt, imo it would be better than google translate.
This aicynide guy may be a pro English, I agree, but remember why you put this repo on GitHub in the first place, you want to share your work with millions of people on GitHub, and to get that outreach you "need" to use English, and if you don't want that that's ok too, English is not my native language also, so I'm not an elitist or something. Also you can just block this aicynide guy and get him off of your mind
Why don't you use chatgpt, imo it would be better than google translate.
Due to can't use the numbers of Chinese region or google voice to register chatgpt, it is not possible to use chatgpt with OpenAI-key for translation unless someone is willing to provide it.
This aicynide guy may be a pro English, I agree, but remember why you put this repo on GitHub in the first place, you want to share your work with millions of people on GitHub, and to get that outreach you "need" to use English
As I mentioned there: #15 (comment)
The initial plan of creating this repo is only to help more people who use chinese as mother language learn about the mpv player and share my own mpv config.
This project was initially aimed at Chinese users, and at the same time, I have other open source projects in English primarily aimed at more users.
Are all public projects on Github aimed at English users? In fact, to my knowledge, there are a large number of non English projects. So I cannot accept this kind of bandit logic.
The reason why I added English support to the to-do list is mainly because the methods mentioned #16 (comment) are no longer available.
Considering that there are also some English users who believe this project is useful to them, I have added English localization support to the to-do list and are gradually implementing it.
But @aicynide slander dampened my motivation for this, so the plan was put on hold.
After spending a period of vacation, I adjusted my mood and used my free time to complete English localization support.
Prepare to push it after making some adjustments.
English localization support has finally been completed and pushed, see https://github.com/dyphire/mpv-config/tree/eng
Note: It should be pointed out that the English branch is difficult to actively maintain. Because I personally do not use it, it increases maintenance costs. This requires other people who will use it in the future to spontaneously maintain and open PR, if any.