Dear all,
if anybody interested, I can send complete workflow for L10N, very similar to M$ espresso.
Here is what I have:
- batch commands to rename resx files (eg. *.cs-cz.resx to *.resx) and back, recursively
- batch files to robocopy all resx from dnn and into work folders
- MDB file (requres M$ access installed) with some VB code inside that works with 2 folders (original and translation) with same structure. Mdb can load new dnn resource pack, then upload previous version of translation and automatically match/translate same terms in new and autotranslate similar terms and mark non translatable terms, plus IMHO ergonomical dialog for easy translation.
- batch to create manifest body with files...
this allows anybody to translate without having dnn.
Main purpose of such tool was that as developer changes number of items in resource and their names from version to version, if U use older app resource it might fail, as it happends to me with UDT module where old Czech resource didnt contain some 200 new terms and fallback didnt helped and module failed.
So it seems to me, that it is crucial to have exactly same resources for root portal lang and localized files which my mdb ensures for 100%, plus autotranslation is also very usefull, plus sql to search same terms, order same terms, ....
As a bonus with this package I can create language pack for any version of dnn core in some 5 minutes. I have 7000 translated terms in my lang that can be applied in 100% safe way to any version of dnn.