sounds like a esk8 drivetrain parameters tutorial in your language is more the issue than VESC tool not having more than EN
1 Like
More like all knowledge needed for diy is an issue. There just ain’t much info here😂
1 Like
In this case you shouldn’t use VESC at all
2 Likes
5 Likes
Time to recommend lingyi to everyone 
1 Like
I can help with editing and compiling the VESC tool if you can provide the English to Chinese translations.
It would be great to get a bunch of language translations and submit them back to the main github
2 Likes
That’s fantastic news! I’ve had trouble understand how to work with QT, managed to translate some UI. I guess I gotta get back on ripping the terms outta QT and translating them.
1 Like
Google translate photo feature lol
It really is pretty neat honestly haha
Fairly accurate from my experience as well
1 Like
Way too time consuming, also all google stuff is blocked by the grate firewall. Surprisingly this forum isn’t
4 Likes
If you can get me the terms (strings? It’s been a while) I can get to it as soon as I wake up. Or I can spend a few hours figuring it out again🥲
If you’ve got the spare time of course
It got “neat” wrong😂 not surprising at all, it’s hard to get sayings in translation apps
1 Like
If these XML files are translated into Chinese, that should do it.
For example, the Motor Current Max Brake setting
The longName and description tags in the XML motor config file would need to be changed. Specifically the part in bold:
<longName>Motor Current Max Brake</longName>
and for the help text
<description><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"> <html><head><meta name="qrichtext" content="1" /><style type="text/css"> p, li { white-space: pre-wrap; } </style></head><body style=" font-family:'Roboto'; ; font-weight:400; font-style:normal;"> <p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-family:'Sans Serif';">Maximum (braking) motor current. The is the maximum current that will be fed back to the VESC and when braking, thus negative. The energy from the braking current will be fed back to the battery.</span></p></body></html></description>
The rest is HTML formatting and can probably stay the same.
For the tab names at the top, that’s the subgroup tag in the same XML files
<subgroupName>Current</subgroupName>
For the menu on the left side, that’s in the mainwindow.cpp file under addPageItem
addPageItem(tr("Welcome & Wizards")
you could probably find more help and resources on the VESCtool forums themselves
Navigating that forum is harder than the hedge maze in the shining…
3 Likes
I got QT to spit out a .TS file containing the strings, after translation it’s going to output a .qm file. Not sure how to plug it back in. There are 1300+ strings lol
after spending the whole afternoon translating stuff. here’s the file containing translated strings. i have no clue how to compile the vesc tool…project_cn.qm (105.6 KB)
2 Likes
After finishing the translation and exporting a .em file, I’m facing a big problem.
I got a prompt set up that will let you select language on start-up, buttttttttt I’m unfimiliar with C++ let along Qt.
I can just edit the stings and call it a day but that’ll be a hard fork and I don’t want to start over again with every update.
Now the problem I’m facing is that in the tutorials I’m following it has a.InstallTranslator(&t) where t refers to the translated strings. And in vedder’s main function “a” is not declared where as in the tutorial a is referred to as return “a.exe” or something like that.
So, I’m very stuck and I hope someone on the forum that’s familiar with C++ or Qt can give me some help with it.
2 Likes
Nice work on translating all of that!
Good news and bad news.
The good news is that Vedder wrapped all of the GUI text in Qt with tr() so it could be translated in the future, and the .qm file you provided did exactly that.
The bad news is that all of the settings are firmware version specific, so they are located in the XML files I posted above. They are separate from Qt. The only way to translate that at the moment is to change the text directly in the XML, and that would prevent you from switching between languages, but we could compile a separate English and Chinese version for example.
I’m thinking if we submit these minor code changes and the .qm translation file, that may motivate Vedder to find a way to incorporate the firmware settings into the translation files.