Dear NXP Support Team,
I am using GUI Guider (vX.X.X) to design an interface that contains an lv_tabview widget with several tabs.
When I type Chinese characters (e.g. “设置”, “关于”) in the tab-text field, Guider automatically re-uses the same string as the C identifier for the tab object. As a result, the generated code looks like:
When I type Chinese characters (e.g. “设置”, “关于”) in the tab-text field, Guider automatically re-uses the same string as the C identifier for the tab object. As a result, the generated code looks like:
This produces a compiler error because the C language does not allow non-ASCII identifiers.
Could you please consider one of the following improvements in a future release?
- Split the two concepts
- Provide two separate input boxes:
– “Display text” (any Unicode string)
– “Object ID / variable name” (restricted to ASCII letters, digits and underscore) - Use the Object ID only in the generated C code, and keep the Display text for the label that appears on screen.
- Automatic sanitisation
- If the user enters Unicode text, silently transliterate it to a valid C identifier (e.g. “设置” → “tab_setting”) while preserving the original Unicode string for the label.
- Built-in i18n support
- Always store an English/ASCII ID internally, and let the user supply translations through the existing internationalisation table. This is already possible, but it is not obvious to new users because the single input box implies that the typed text will be used verbatim in the code.
At the moment the only workaround is to:
- type an English ID first,
- generate the code,
- then manually change the label text back to Chinese,
which is tedious and error-prone.
Thank you for your attention. I would appreciate any feedback on whether this enhancement can be placed on the roadmap.
Best regards,
Hi @yyxy
I try to change it to Chinese.
And i can compile it successfully.
Which version you are using?
BR
Harry
