@Rhywden We have many customers using the Twiddler3 in a non-English environment. While I agree that the current version of Tuner for non-English users can be a bit clunky; we have yet to come up with a solution that is intuitive for all languages. (Trust me, this is an ongoing conversation we have here) Educating our customers on how the Twiddler3 (and every keyboard for that matter) works at a low level, is the best and most direct method of solving this issue. Once this is understood, the shortcomings of the Tuner make logical sense and can be worked around to create a proper config file.
You don't run into this with a standard keyboard as most people do not, and cannot, remap what the button under the "A" key sends to the OS. It always sends HID 4 to the OS. In the Twiddler's case pressing 0 R000 (Factory "A") can send any HID code, or HID codes, to the OS. Representing this feature in a non-English environment in an intuitive fashion has proved illusive on many levels:
How do you handle different region and language combinations?
How do you handle a case where different language settings are used in a single config file?
How do you store the language information when a particular chord is created?
What happens if that language is not installed in the OS when the chord is issued?
While we appreciate the criticism, as it brings shortcomings to light, what is really needed is a viable solution, and, we are all ears.