inav-configurator
inav-configurator copied to clipboard
iNavFlight
Update chinese translations
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.
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.
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.
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.
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
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.
- 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.
- This translation is not the best yet. We will keep maintain it make it better.
- PX4/ArduPilot users in china have more basic knowledge and skills, they will make this circle more professional.
Also like the header of betaflight, the old translation breaks the UI, ours make it looks better.
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.
怎么把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
怎么把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