Remember, when you add the WixUIExtension it will bring in localization files which will change your codepage depending which culture you pick. That's almost always the reason your MSI codepage changes... because the UI you chose defined an override.
On Fri, Dec 10, 2010 at 7:56 AM, Thom Leigh <t...@mondago.com> wrote: > So you've hard-coded the Product/@Codepage to 0, but when you add a > reference to votive, it ignores that and sets it to 1252 internally? > > What if you hard-code it to another value? Like 1256? Same behavior? > > You should probably see if this is reproducible and if so file a bug > report... > > > -----Original Message----- > From: David Watson [mailto:dwat...@sdl.com] > Sent: 10 December 2010 14:35 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Upgrade to wix 3.5 doesn't > honourtheprod...@codepage > > Hi, > I am indeed using the escrow 2 (2403) build, I also tried in wix 3.6. > > I also notice that you don't even need to use anything in the > WixUIExtension just add a votive reference and it changes the codepage. > > Dave > > > > -----Original Message----- > From: Thom Leigh [mailto:t...@mondago.com] > Sent: 10 December 2010 13:45 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Upgrade to wix 3.5 doesn't honour > theprod...@codepage > > I had a thing like that a couple of months ago. Product/@Codepage would > be 1252 no matter what I set it to, even if setting it to something > totally different like 1256. > > I opened a bug in the tracker and I think it got fixed. Which weekly are > you using? Have you tried it in "Escrow 2"? > > PS I was originally trying to set the codepage to 65001, so I don't > know, setting it to 0 might well be something that changed from 3.0 to > 3.5... > > > -----Original Message----- > From: David Watson [mailto:dwat...@sdl.com] > Sent: 10 December 2010 12:47 > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] Upgrade to wix 3.5 doesn't honour the > prod...@codepage > > Hi, > I am doing Wix 3.5 upgrade testing and I notice that the MSI I created > after upgrading my votive Wix 3.0 project to 3.5 alters the schema > codepage to 1252 even though I explicitly set it to 0. > > This means that I can't make a patch as the msi codepages do not match. > > After a bit of experimenting I notice that when we UI reference the > WixUI_ErrorProgressText from WixUIExtension is when the schema codepage > is forced to be 1252. > > Does this mean that the Wix error strings are now no longer suitable for > a language neutral MSI? > (http://msdn.microsoft.com/library/aa368057.aspx) > > > Dave > SDL PLC confidential, all rights reserved. > If you are not the intended recipient of this mail SDL requests and > requires that you delete it without acting upon or copying any of its > contents, and we further request that you advise us. > SDL PLC is a public limited company registered in England and Wales. > Registered number: 02675207. > Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire > SL6 7DY, UK. > > > ------------------------------------------------------------------------ > ------ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > ------------------------------------------------------------------------ > ------ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > ------------------------------------------------------------------------ > ------ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ------------------------------------------------------------------------------ > Oracle to DB2 Conversion Guide: Learn learn about native support for > PL/SQL, > new data types, scalar functions, improved concurrency, built-in packages, > OCI, SQL*Plus, data movement tools, best practices and more. > http://p.sf.net/sfu/oracle-sfdev2dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC ------------------------------------------------------------------------------ Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL, new data types, scalar functions, improved concurrency, built-in packages, OCI, SQL*Plus, data movement tools, best practices and more. http://p.sf.net/sfu/oracle-sfdev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
