How to setup iTwin Synchronizer GUI localization?

Hi,

after the last iTwin Synchronizer client update I realized it switched from English to Czech GUI.

Well, it's just a disaster. Unfortunately it continues in amateurs translation quality, similarly to CONNECTION client and Bentley Advisor. Bentley today represents the worst (the lowest) CAD/GIS product localization level from the products I used (at least occasionally like ESRI or AutoCAD). Evidently it's based on copy/paste process using Google Translator or similar general service, by somebody who have no idea what functionality the translated product has and what standard terminology is used in target country (defined as standard by Microsoft, because it relates to Windows, or as standard by some industry user groups or also is in some national standards). And it's, again the same as CONNECTION client and Advisor, not tested by native speaker, because at many places, the translations are just nonsense.

Ok, never mind, when it's Bentley policy and standard, fine. But how can I switch it back to English language? Or is it like Advisor, that cannot be switched to another language (do not respecting quite normal situation in Europe, when Windows / used software / user himself can represent 3 different languages?).

With regards,

  Jan

  • I don't think there's an elegant way... I've been told the language can be influenced by passing a command line parameter, so try updating your application shortcut and adding " --lang=en" (no quotes) to the end of the 'Target' field... but I don't think this helps the MicroStation integration workflow. We've already raised this issue with the application framework team, but have had trouble getting it prioritized.

    MISSING RESOURCE: VerifiedBy Jan Šlegr 

  • Hi Jeff,

    thanks for your answer.

    Honestly, I do not understand who design this feature and what idea is behind it. I reported the same problem for Bentley Advisor long time ago, which also follows Windows language (and not MicroStation, even it should be integrated) and cannot be changed. It's completely out of reality of e.g. environment in international companies in Europe.

    Optionally I would accept Czech GUI (even it's annoying and time consuming especially in learning period, and when documentation is not in the same language), but not Czech GUI with so unprofessionally done localization, where the most of sentences are nonsense.

    Fortunately, when cs.pak is renamed, the client does not find this "Czech language trash" and uses English GUI ;-) But it has to be done again and again after any update.

    With regards,

      Jan

    MISSING RESOURCE: VerifiedBy Jan Šlegr