Open wixbot opened 13 years ago
When setting Product@language and Product@codepage to 0 and linking with -cultures:null. Shouldn't you get a Codepage 0 wxl?
I will lower the priority also as we have a work around.
Correct. WixUI includes .wxl files that override the Product Codepage so the UI will display correctly.
We should investigate how to best support "code-page 0". But that will be a breaking change that we shouldn't do until major revision (WiX v4.0).
Extensions have a default culture; for WixUIExtension, it's en-US. That pulls in the en-US loc strings, which set the codepage to 1252.
Originally changed by
barnson
Area
changed fromlight
tolinker
Release
changed fromfuture
tov4.x
Is there any chance for a better support of codepage 65001 (UTF-8) as well ?
In build 2403 of Wix 3.5 I have found that if you create a new project and add a reference to WixUIExtension then the product@codepage is ignored and the msi DB schema is always set to 1252.
I found this when rebuilding an old msi to test patch building across wix versions and my patch build failed as the new msi had a different code-page to my old msi. My msis are set to code-page 0. I assume this is related to bug 3060416 but I could not see a way to comment on that bug or reopen it.