Adding support for lang_data.zip file operations on Audi vehicles

[filippz]

I have written a small app (.NET) that is able to use existing lang_data.zip and add a language to it and/or change existing translations.
To transfer lang_data.zip file itself I was using direct telnet connection to transfer the file from the unit to SD card and once changed I used the same way to copy it back to the unit.
IMHO those operations could be simple added to the MIB tool in the following manner:

• backup of the unit could include lang_data.zip (/net/mmx/mnt/app/eso/hmi/lsd/jars/lang_data.zip)
• the MIB could offer the possibility of transferring lang_data.zip back to unit from the SD card (and reboot to apply)

Things to consider:

• instead of simply transferring the file back to unit script could also check the content of the checksum_lang_data.md5 inside the zip file to confirm these are the same (as lang_data.zip varies over firmware versions checksum_lang_data.md5 is used to verify that the lang_data.zip matches with firmware)
• if the user adds another language with the mentioned app there is also a need to add that language to the DATASET_2D00 in setlang script (description of the mentioned dataset: https://mibwiki.one/doc/language-dataset-ggPAc1Or7X)

Any thoughts about this? Anybody willing to test the app and take a crack at integration with MIB tool?

Additional notes:

• I have only used my own MHI2 unit in my Audi A4 B9 so I can't really tell if other units might benefit from the tool apart MHI2/MHI2Q in Audi vehicles. In any case more testing is needed.
• Details of the format have been described here: https://mibwiki.one/doc/audi-mhi2mhi2q-language-files-hd6YoHG0fx/insights
• Some translations contain placeholders (ie %1) which should be kept but the app doesn't force it.
• App loads the lang_data.zip and tries to generate it back from it's internal representation of it and checks if there are any differences - if there are differences then the save function is disabled in order to prevent the generation of the invalid file.
• App has a possibility to use "reference" lang_data.zip to speed up translations in the following manner – for example MHI2_ER_AUG22 doesn't have ro_RO language but MHI2Q_ER_AUG22 does have it and both have en_GB:

1. Open the MHI2 lang_data.zip
2. Select language en_GB from it to use as a base for translation and add a new ro_RO language as a copy of the en_GB. Now we have ro_RO in MHI2 lang_data.zip that is exactly the same as the en_GB
3. Open the lang_data.zip from MHI2Q that already contains en_GB and ro_RO and select en_GB as a reference
4. App tries to find the matching translations from MHI2 by searching for it in MHI2Q en_GB (reference language) and if it finds it then it places the translation next to the untranslated MHI2 string from ro_RO (selected language) translation in MHI2Q
5. User has a possibility to either copy the offered translation to MHI2 and/or translate the message manually