Hi, how is it possible to make a language localisation? Im ready to produce full translation of QGC to russian, but I don’t know in which files should I make changes… Could someone guide me please?
Have a look at what others have done maybe?
https://github.com/mavlink/qgroundcontrol/pulls?q=is%3Apr+translation+is%3Aclosed
Hi, thanks, I thought about to make a fork and translate only interface for the beginning. Could you please tell how its possible to lock MAVlink parametres from user changing?
Are you referring to the PX4 parameters?
YesHi, yes, about PX4 params
They probably need translation on the PX4 side.
I’m not sure if it is supported yet. There was a PR here: component information: add translation support by bkueng · Pull Request #21326 · PX4/PX4-Autopilot · GitHub
And I’m pinging @bkueng here, he should know better.
Thanks! I also want to how its possible (if it is) to lock parameters from changing
Yes it’s all there now and translation can be done via https://crowdin.com/.
@hamishwillee can give you the details.
OK, so docs PR to provide all the information here: Pull requests · PX4/PX4-user_guide · GitHub
@reinzler The simple version is that you need to join this project on Crowdin: Crowdin . Can you see it? If so I can add a Russian translation there. If not, ping me and I can make this visible.
@bkueng This only works takes source metadata from main builds - do we need to think about versioned translations for metadata?
@bkueng This only works takes source metadata from main builds - do we need to think about versioned translations for metadata?
I would do that once we have enough data. On PX4 it’s quite easy to set a version-specific URL, and then we can do a tag/branch on the translation repo.