Cheers Rob. It's pretty much what we thought and as I said before we don't really use the functionality of having a language neutral MSI so it's not impacting us, we were always doing it just in case. I don't think 1252 will be an issue for us in future. I was just concerned that other people were following this pattern.
Thanks Dave W -----Original Message----- From: Rob Mensching [mailto:r...@robmensching.com] Sent: 15 December 2010 16:22 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Upgrade to wix 3.5 doesn't honourtheprod...@codepage A few things: 1. You are correct that, WixUI no longer supports codepage 0. Arguably codepage 1252 is more correct since we just writing English and have not done the work to ensure everything is ASCII. So this isn't a bug we'll address in WiX v3.5 because we are in escrow and there is a work-around. However, we've moved the bug to WiX v3.6 to reconsider how to build neutral MSIs. 2. It is not recommended to change your WiX toolset version for patching. Patching is pretty fragile and there could be sublte (or not so subtle) changes in the output of the WiX toolset between versions that break things. #1 is a perfect example of one of those sublte changes. If you really need to do upgrade your WiX toolset after the product is released, test your patches very closely. I could not anticipate the issues that might come arise. 3. You might be able to copy the en-us.wxl and change it's codepage to "0" and give it a different culture (i.e. "x-neutral") and pass that in. If all goes as I hope, your neutral .wxl will override the built in .wxl files and get the codepage right. That's probably better because you can also ensure your neutral.wxl file is pure ASCII. (This *may* be the solution we come up with for v3.6). On Mon, Dec 13, 2010 at 4:09 AM, David Watson <dwat...@sdl.com> wrote: > Hi, > > We only use the UI extension to get the error messages and progress > text, all our UI is external. We don't pick a culture at all, one is > being chosen for us. > > We set prod...@language and prod...@codepage to 0 and link with > -cultures:null. > > We were following the pattern of making language neutral MSIs > (http://msdn.microsoft.com/library/aa368057.aspx) in case we needed to > localize later. This was working in Wix 3.0 but may have caused us > issues if we did localize. Oddly we've never localized our installations > even though we are one of the world's largest translation companies, I > suppose that's the benefit of selling to translators that almost always > know English. > > It now seems that there is no way to use the Wix UI strings and make a > language neutral MSI even though the wixUI-en-us.wxl (which I assume is > the default) looks like it could be set to codepage 0 as there is only > ascii in there. This will not really affect us as we have the following > work around so I don't know if it's an issue for anyone else. > > For our patch building process we will have to hack our compiled MSIs > back to codepage 0 and will use 1252 as a base codepage in the future. > > Dave > > > -----Original Message----- > From: Rob Mensching [mailto:r...@robmensching.com] > Sent: 11 December 2010 21:25 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Upgrade to wix 3.5 doesn't > honourtheprod...@codepage > > 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<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 > > > ------------------------------------------------------------------------ ------ > 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 ------------------------------------------------------------------------ ------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
