-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support utf-8 strings in configuration files #36
Comments
May be related to issue #9. |
Sample file: <?xml version="1.0" encoding="utf-8"?>
<root>
<shell>
<menu separator="true" />
<menu name="issue36">
<menu name="do a prompt" description="test for copyright and omega characters">
<actions>
<prompt name="myarguments" title="z©z" default="Hugh _Ω_ Jass" />
</actions>
</menu>
<menu name="psi letter: _Ψ_" description="test for psi letter" />
<menu name="copyright letter: z©z" description="" />
</menu>
<menu separator="true" />
</shell>
</root> |
The |
The following functions also need to be converted to their windows unicode format counterpart:
|
I think the best strategy is to "property" convert to utf-8 when a configuration file is read. Then, in windows functions like |
Properties such as <file path="${env.USERPROFILE}\myapp.ini">selection=${selection.path}</file> This could also be identified as a breaking change in CHANGES file. |
The issue about |
Parsing from an xml configuration file encoded in utf-8 does not seems to be working as expected.
For example, the following menu is not displayed properly:
The action does not support utf-8 strings. For example, the following prompt message is not displayed as expected:
The text was updated successfully, but these errors were encountered: