Here for example, this part:
"conceptName": "Nutritional Values"
The config points to a concept using its fully specified name.
Even if you were to provide Thai translations for the above concept, the fully specified name in Thai would still have to remain the English expression "Nutritional Values" to keep things working. Leading to a willingly wrong metadata import: a Thai fully specified name is in fact provided as an English set of words, just to match its English references across the config when you use the app in the Thai locale.
Cc @darius, @angshuonline: we believe this is a design flaw and there should be a configuration locale specified somewhere. This will be the subject of another thread at some point.