search

wixtoolset / issues

WiX Toolset Issues Tracker
http://wixtoolset.org/
129 stars 36 forks source link

Product@codepage is being overridden when you use WixUIExt #3007

Open wixbot opened 13 years ago

wixbot commented 13 years ago

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.

Originally opened by wyrdfish from http://sourceforge.net/p/wix/bugs/2391/

wixbot commented 12 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.

wixbot commented 12 years ago

Correct. WixUI includes .wxl files that override the Product Codepage so the UI will display correctly.

wixbot commented 12 years ago

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).

wixbot commented 12 years ago

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.

wixbot commented 10 years ago

Originally changed by barnson Area changed from light to linker Release changed from future to v4.x

CyberSinh commented 7 years ago

Is there any chance for a better support of codepage 65001 (UTF-8) as well ?