Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update chinese translations #984

Open
wants to merge 19 commits into
base: master
Choose a base branch
from

Conversation

hjjoe1213123
Copy link

Translation description mostly to Chinese,Hope to join Chinese.

@hjjoe1213123
Copy link
Author

Modify some i18n and add some Chinese translation

@hjjoe1213123
Copy link
Author

Update chinese translations

@DusKing1
Copy link

DusKing1 commented Jun 15, 2020

I don't know what you guys think about this @shellixyz @digitalentity @DzikuVx Looking at this matter from a public perspective, I think that translators contribute to the different projects but their users are almost the same must try to keep the translation consistent. From this point of view, and considering we have spend tons of spare time on maintaining zh_CN translation for betaflight configurator, many strings should be kept the same. So I strongly disagree with the translation of some of the strings in your .json.

Willing to provide help if you want @hjjoe1213123 . Just ask your team mates on wechat, most of them have my contact.

@hjjoe1213123
Copy link
Author

I don't know what you guys think about this @shellixyz @digitalentity Looking at this matter from a public perspective, I think that translators contribute to the different projects but their users are almost the same must try to keep the translation consistent. From this point of view, and considering we have spend tons of spare time on maintaining zh_CN translation for betaflight configurator, many strings should be kept the same. So I strongly disagree with the translation of some of the strings in your .json.

Willing to provide help if you want @hjjoe1213123 . Just ask your team mates on wechat, most of them have my contact.

After all, inav and betaflight are still very different. For the fields with conflicting translations, we can only say that the semantics are as close to each other as possible. We are more concerned about the rapid understanding and use of inav in Chinese.

@DusKing1
Copy link

After all, inav and betaflight are still very different. For the fields with conflicting translations, we can only say that the semantics are as close to each other as possible. We are more concerned about the rapid understanding and use of inav in Chinese.

I don’t know if you really understand the user characteristics and demands of INAV users in Chinese. From my maintenance experience and contribution experience, as well as the experience from the former third-party maintainer of Chinese translation for INAV-Configurator, 97% of Chinese INAV users are all transferred from betaflight. If the code on the MCU causes a torn user experience on the same hardware board of the user, then I don’t think this is the correct way.

@hjjoe1213123
Copy link
Author

After all, inav and betaflight are still very different. For the fields with conflicting translations, we can only say that the semantics are as close to each other as possible. We are more concerned about the rapid understanding and use of inav in Chinese.

I don’t know if you really understand the user characteristics and demands of INAV users in Chinese. From my maintenance experience and contribution experience, as well as the experience from the former third-party maintainer of Chinese translation for INAV-Configurator, 97% of Chinese INAV users are all transferred from betaflight. If the code on the MCU causes a torn user experience on the same hardware board of the user, then I don’t think this is the correct way.

We had considered this problem at the beginning, so most of the translation of inav is based on betaflight, but there are indeed no corresponding words in betaflight. This kind of argument is meaningless. It is better to participate in inav translation together.

Copy link

@DusKing1 DusKing1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fine, by reviewing the commits you submit, now I start to think if you are on a pretty old betaflight zn_CN translation.

We had considered this problem at the beginning, so most of the translation of inav is based on betaflight, but there are indeed no corresponding words in betaflight.

Or you are just an arrogant guy who ignores the facts. Because the problems I pointed out are not all problems, there are various similar problems everywhere in your entire translation. What is your answer to this situation?

},

"backupFileIncompatible": {
"message": "抱歉,提供的备份文件是为先前版本的配置器生成的,并且与该版本的配置器不兼容。"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please let me convince this string is refered from betaflight not your random translate.

},

"defaultWelcomeIntro": {
"message": "欢迎使用<strong>INAV - Configurator</strong>, 为简化固件升级,设置和调校飞控而生的工具。"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again, please convince me you have already thought about risk of tearing user experience. Betaflight configurator using "配置程序" at this string, please offer the reason for changing it back to "configurator".

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again, please convince me you have already thought about risk of tearing user experience. Betaflight configurator using "配置程序" at this string, please offer the reason for changing it back to "configurator".

I suggest you look at what is written in the default language of inav and then discuss this issue. You can’t point something with inav to your betaflight. Again, if you think there is ambiguity, welcome to fork to correct the accusations of maintenance. What can’t be solved?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please do not use the method of transferring topics to avoid my question. Do you take into account the issues I raised above? Please answer my question first, and then I will consider answering your question.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have said it many times, most of them are directly quoted based on betaflight, you see if this is the same
"defaultWelcomeIntro": { "message": "欢迎使用 <strong>Betaflight - 配置程序</strong>,为简化固件升级,设置和调校飞控而生的工具。" },
But some of us think that betaflight is not well understood, then we will replace it with semantics that we think is better understood

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great, now please explain this sentence

I suggest you look at what is written in the default language of inav and then discuss this issue.

Can I understand it as - for Chinese users, "Configurator"is easier to understand than "配置程序"?

ARE YOU A NATIVE SPEAKER?

Except for this one, the software frame we all using will cause an ugly rendering if the words are not in standard UTF-8, especially for Chinese characters. The space I add is NEEDED for almost all strings. I believed you have seen that, but LET ME REMIND YOU ONCE MORE. MANY SPACEs IN CHINESE TRANSLATION ARE UNDELETABLE.

Copy link

@DusKing1 DusKing1 Jun 15, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The problem of confusion between ‘配置器’and ‘配置程序’ is not in this string, so I still have to ask you:

Can I understand it as - for Chinese users, "Configurator"is easier to understand than "配置程序"?

ARE YOU A NATIVE SPEAKER?

Don't use the method of transferring topics to avoid my question.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hahaha, unexpectedly, welcome to maintain inav translations in the future, there are still a large number of translations that have not been completed

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hjjoe1213123 Maybe “配置工具” is better.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

then please elaborate and clarify the ambiguity caused by changing this entry and why we using this for years but now you suddenly jumped out and we should change this.

Copy link

@bys1123 bys1123 Jun 15, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Not the oldest is the best, if so MWC will be the most popular flight controller today.
  2. iNav is very new project for most of chinese users, so it's a good chance to give users a fresh new experience.
  3. If most of users think our translation is better, then maybe it's the time you should change yours, otherwise, we will change ours.

_locales/zh_CN/messages.json Outdated Show resolved Hide resolved
@digitalentity
Copy link
Member

Summoning @DzikuVx to the discussion as well :)

@digitalentity
Copy link
Member

My opinion - it would be awesome to have a common set of strings with Betaflight, Cleanflight and other projects as we re-use some of them. This way *flight ecosystem will have to maintain just one translation. However, I'm not sure *flight folks would be willing to join the effort

@DusKing1
Copy link

Only stands for zh_CN and zh_TW: *I'm always willing to help if any flight folks summoned me.

Frankly speaking, adding additional 17k words of translation is not worth mentioning compared to my current workload.

@bys1123
Copy link

bys1123 commented Jun 15, 2020

  1. I don't agree iNav and Betaflight is sharing the same user base. Betaflight users need a fast racing or freestyle experience. But inav is providing slower flying experience under GPS or optical flow assist. Lots of PX4 and Ardupilot users is transfering to iNav, since PX4 and Ardupilot become more and more complicated and expensive.
    So reference both PX4/ArduPilot and Betaflight, choose the best common term translation is important.
  2. This translation is not the best yet. We will keep maintain it make it better.
  3. PX4/ArduPilot users in china have more basic knowledge and skills, they will make this circle more professional.

@bys1123
Copy link

bys1123 commented Jun 15, 2020

image
image
Also like the header of betaflight, the old translation breaks the UI, ours make it looks better.

@DusKing1
Copy link

hehe, fine. I gave you straight questiones, but your guys never directly answer on me. I'm done with your nonsense @hjjoe1213123 @bys1123 . Shut up on this thing to me

The first criterion of collaboration: Never work for something based on a shit mountain.

@bys1123
Copy link

bys1123 commented Jun 15, 2020

Yes, never work for something based on a shit mountain.

@Jarrettma
Copy link

怎么把inav转化为中文?
How to convert INAV into Chinese?

@hjjoe1213123
Copy link
Author

怎么把inav转化为中文?
根据本地语言环境自动切换,前提是这个中文翻译有合并到主分支,否则只能单独检出中文的分支,或者直接下载:https://gitee.com/hjjoe1213123/inav-configurator
How to convert INAV into Chinese?
Automatically switch according to the local language environment, provided that the Chinese translation is merged into the main branch, otherwise you can only check out the Chinese branch separately, or download it directly: https://gitee.com/hjjoe1213123/inav-configurator

1 similar comment
@hjjoe1213123
Copy link
Author

怎么把inav转化为中文?
根据本地语言环境自动切换,前提是这个中文翻译有合并到主分支,否则只能单独检出中文的分支,或者直接下载:https://gitee.com/hjjoe1213123/inav-configurator
How to convert INAV into Chinese?
Automatically switch according to the local language environment, provided that the Chinese translation is merged into the main branch, otherwise you can only check out the Chinese branch separately, or download it directly: https://gitee.com/hjjoe1213123/inav-configurator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants