If you specify Codepage="1252" in the Product or Module
element, the characters will be stored correctly. It doesn't
matter whether you use ä or type "" directly in the
WXS file. (In the latter case, you may have to declare the
encoding of the source file with something like .)
However, I think this is still a bug. WiX should at least warn if
it cannot encode the intended characters in the selected
codepage.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
kal-le's suggestion is not necessarily a bad idea. However, it
is extremely costly to evaluate the codepage of each string
in the MSI to verify that it is possible. I'm going to close this
bug because the cost vs. benefit is bad.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=20705
If you specify Codepage="1252" in the Product or Module
element, the characters will be stored correctly. It doesn't
matter whether you use ä or type "" directly in the
WXS file. (In the latter case, you may have to declare the
encoding of the source file with something like .)
However, I think this is still a bug. WiX should at least warn if
it cannot encode the intended characters in the selected
codepage.
Logged In: YES
user_id=991639
kal-le's suggestion is not necessarily a bad idea. However, it
is extremely costly to evaluate the codepage of each string
in the MSI to verify that it is possible. I'm going to close this
bug because the cost vs. benefit is bad.