Vietnamese is missing, and we would like to get it there for a local project. Is anybody aware of a list of steps/conditions that need to be taken/fulfilled?
Is it a question of adding the option somewhere in the code of QField? Or does the language need a minimum translation % on the Transifex platform?
We’re very grateful for any knowledge or experience that can be shared.
@Mathieu_Pellerin , thank you for taking the time to answer! That 50% is a clear goal It should be possible indeed to reach that percentage. Quick follow-up question. Are there, apart from translating itself, any other steps we will need to take? And imagine the translations reach the treshold, how long would it take before we would see the Vietnamese lanuage present in the app? Is it something that takes days/weeks/months? Thank you for everything!
After updating QField to the latest version, however, I don’t see Vietnamese available yet in the languages dropdown-menu. Do changes like this maybe only become available with major updates? Or is there anything else I miss?
@Ward , that’s fantastic. A brand new localization popping up on the main QField repository makes me so happy every time it happens.
The 50% threshold was met after we branched off QField 4.2. It’s therefore not available in the 4.2.X series of patch releases. It will be available in the next version coming out towards the end of next month.
If you want to see the fantastic results of your efforts, you can install a recent development build APK by looking for QField fairy comments in the repository history (e.g. Synchronize translations · opengisch/QField@e398fab · GitHub). You’ll most likely want the arm64 APK package unless you have a >10 year old device, in which case you should check if your device has arm / arm-neon CPU.