Need guidance to improve Ukrainian translation

[smsnvc]

Hi,

Thanks for your work on the Mission Planner.

I need some help with improving Ukrainian translation.

As I understand, most of the strings are in the *.uk.resx
So potentially we can go file by file, making pull requests.

However, I do not see the translation of descriptions in the full parameter list.
Will there be some localization in the future?

[robertlong13]

Param metadata is a tough one.

• Planner fetches the parameter descriptions straight from the ArduPilot build server, so that it always has the latest documentation.
• ArduPilot maintains these descriptions in special comments in the code, from which the param metadata xml files are autogenerated.

If we want to start localizing the param descriptions (which is a worthy goal), we should come up with a way to handle this on the ArduPilot side, then Planner can just fetch a language-specific xml file.

[smsnvc]

If we want to start localizing the param descriptions (which is a worthy goal), we should come up with a way to handle this on the ArduPilot side, then Planner can just fetch a language-specific xml file.

Usually those are just values extracted via {key}+{language} pair with a fallback to English if the string is missing in translation. Betaflight configurator case: half of the localizations are lagging behind. So to me putting the UI localization to the firmware is not quite practical - you would have to release some localization updates when translators complete, and then bump versions in tools like Mission planner, duplicates the number of moves.

[robertlong13]

I don't mean we put the UI localization in the firmware. What I mean is that Mission Planner is not the place to maintain the translation of those files, as it's not the only consumer of them. QGC, MAVProxy, any other GCS software, and even the wiki, all use those, and they could all potentially benefit from that translation being maintained somewhere central. I'm thinking a new repo just for parameter translation would maybe be the right move.

[robertlong13]

Oh and regarding this:

then bump versions in tools like Mission planner

That step isn't necessary. They aren't baked into Mission Planner. It downloads them fresh every single time. As soon as new parameter metadata files hit the ArduPilot firmware server, all versions of Mission Planner immediately use them. There's no extra step.

The idea would be basically as soon as a PR gets merged on the param translation repo, it would automatically update for everyone.

[smsnvc]

That step isn't necessary. They aren't baked into Mission Planner. It downloads them fresh every single time. As soon as new parameter metadata files hit the ArduPilot firmware server, all versions of Mission Planner immediately use them. There's no extra step.

Cool, then it may work well.