Re: [WiX-users] Globalized Bundle?
I'm very interested in the answer to this also. I will be working on internationalizing our installer in the next couple of weeks, and I was worried that we would have to go with the multiple MSI file route. If the localization files can be loaded at runtime that would be great! Kelly On Jan 9, 2012, at 5:53 PM, Ian Williams iawil...@microsoft.com wrote: Merging threads; just ensuring my reply doesn't get lost. Thanks. -Original Message- From: Ian Williams [mailto:iawil...@microsoft.com] Sent: Monday, January 09, 2012 11:15 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Globalized Bundle? Hmm, I'm a bit confused here. I'm under the impression that originally .wxl files were used for an MSI in conjunction with a few options passed to light.exe (-cultures:ja-jp -loc path to ja-jp .wxl file). And what you get it a Japanese localized MSI (this is all compiled into it). You're saying that the WixStdBA will look for .wxl files at runtime - great! That's exactly the sort of thing I'm looking for, that should avoid the creation of an installer for each language. But I can't figure out the usage pattern here. If I add things like !(loc.ProductName) to my bundle authoring, light complains that the localization variable !(loc.ProductName) is unknown. So at link time I have to point it to a particular .wxl file... and we're back where we've started! I also tried pointing light to multiple .wxls for each language I want but that doesn't seem to work either. What the piece I'm missing here that allows runtime localization decisions? As an aside, the most important thing for me really is to be able to choose the WiXVariable WixStdbaLicenseRtf at runtime based off of the system language. Not sure if even runtime loading of .wxls will accomplish this. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Monday, January 09, 2012 12:36 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Globalized Bundle? We do LCID because we still support WinXP SP2 On Mon, Jan 9, 2012 at 3:46 AM, Sam Morris s...@red-redemption.com wrote: On Sat, 07 Jan 2012 08:50:15 -0800, Rob Mensching wrote: The wixstdba will automatically search for a .wxl file of the system language (i.e. look in 1033 directory for english and 1041 for german and 1044 for japanese, or are those last two switched?). Failing to find a matching .wxl file will cause wixstdba to fall back to a .wxl in the root. There are a few bugs about localization open that need to be fixed before this works well but you can see the beginnings. Would you consider keying translations by the string representation of the locale name rather than the numeric locale ID? This will allow more intelligent fallback behaviour. Currently if I ship a .wxl file in the 1031 directory (de-DE) then a user with a UI language setting of 3079 (de-AT) will not see the German strings, even though they are closer to the user's preferred language than the default strings. http://msdn.microsoft.com/en-us/library/windows/desktop/dd374098 (v=vs.85).aspxhttp://msdn.microsoft.com/en-us/library/windows/desktop /dd374098%0A%28v=vs.85%29.aspx describes the UI language fallback behaviour in Vista and later. Emulating this on earlier Windows versions (that lack LOCALE_SPARENT info for a locale) seems straightforward enough: just chop off the hyphen and anything that follows. -- Regards, Sam Morris -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Write once. Port to many. Get the SDK
Re: [WiX-users] Globalized Bundle?
On Sat, 07 Jan 2012 08:50:15 -0800, Rob Mensching wrote: The wixstdba will automatically search for a .wxl file of the system language (i.e. look in 1033 directory for english and 1041 for german and 1044 for japanese, or are those last two switched?). Failing to find a matching .wxl file will cause wixstdba to fall back to a .wxl in the root. There are a few bugs about localization open that need to be fixed before this works well but you can see the beginnings. Would you consider keying translations by the string representation of the locale name rather than the numeric locale ID? This will allow more intelligent fallback behaviour. Currently if I ship a .wxl file in the 1031 directory (de-DE) then a user with a UI language setting of 3079 (de-AT) will not see the German strings, even though they are closer to the user's preferred language than the default strings. http://msdn.microsoft.com/en-us/library/windows/desktop/dd374098 (v=vs.85).aspx describes the UI language fallback behaviour in Vista and later. Emulating this on earlier Windows versions (that lack LOCALE_SPARENT info for a locale) seems straightforward enough: just chop off the hyphen and anything that follows. -- Regards, Sam Morris -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Globalized Bundle?
Hmm, I'm a bit confused here. I'm under the impression that originally .wxl files were used for an MSI in conjunction with a few options passed to light.exe (-cultures:ja-jp -loc path to ja-jp .wxl file). And what you get it a Japanese localized MSI (this is all compiled into it). You're saying that the WixStdBA will look for .wxl files at runtime - great! That's exactly the sort of thing I'm looking for, that should avoid the creation of an installer for each language. But I can't figure out the usage pattern here. If I add things like !(loc.ProductName) to my bundle authoring, light complains that the localization variable !(loc.ProductName) is unknown. So at link time I have to point it to a particular .wxl file... and we're back where we've started! I also tried pointing light to multiple .wxls for each language I want but that doesn't seem to work either. What the piece I'm missing here that allows runtime localization decisions? As an aside, the most important thing for me really is to be able to choose the WiXVariable WixStdbaLicenseRtf at runtime based off of the system language. Not sure if even runtime loading of .wxls will accomplish this. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Saturday, January 07, 2012 8:50 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Globalized Bundle? The wixstdba will automatically search for a .wxl file of the system language (i.e. look in 1033 directory for english and 1041 for german and 1044 for japanese, or are those last two switched?). Failing to find a matching .wxl file will cause wixstdba to fall back to a .wxl in the root. There are a few bugs about localization open that need to be fixed before this works well but you can see the beginnings. On Thu, Jan 5, 2012 at 2:59 PM, Ian Williams iawil...@microsoft.com wrote: I'm trying to investigate the viability of making my bundle installer globalized - that is, it is one installer that will look at the language of the system in order to choose how to present itself to the user (and perhaps what to install). I thought that was one of the advantages of using a bundle, but I'm realizing now that that doesn't seem to be part of the intent. For starters, I wanted to do something like PropertyRef Id=SystemLanguageID / !-- This is a wix property that stores the language windows is set to -- WixVariable Id=WixStdbaLicenseRtf Value=...[SystemLanguageId]...license.rtf / But I can't have a PropertyRef in a bundle. There are more issues that leave me to believe that bundles are not designed to be able to intelligently choose a language to present themselves in... at least with WixStdBA (been trying to avoid writing my own BA). Does anyone have any advice on what direction I should be going here? If this doesn't work I guess users must choose what language the installer will be in when the download it (so I need to make a different version of the .exe for each language using the !(loc.X) stuff). Thanks, Ian -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Globalized Bundle?
We do LCID because we still support WinXP SP2 On Mon, Jan 9, 2012 at 3:46 AM, Sam Morris s...@red-redemption.com wrote: On Sat, 07 Jan 2012 08:50:15 -0800, Rob Mensching wrote: The wixstdba will automatically search for a .wxl file of the system language (i.e. look in 1033 directory for english and 1041 for german and 1044 for japanese, or are those last two switched?). Failing to find a matching .wxl file will cause wixstdba to fall back to a .wxl in the root. There are a few bugs about localization open that need to be fixed before this works well but you can see the beginnings. Would you consider keying translations by the string representation of the locale name rather than the numeric locale ID? This will allow more intelligent fallback behaviour. Currently if I ship a .wxl file in the 1031 directory (de-DE) then a user with a UI language setting of 3079 (de-AT) will not see the German strings, even though they are closer to the user's preferred language than the default strings. http://msdn.microsoft.com/en-us/library/windows/desktop/dd374098 (v=vs.85).aspxhttp://msdn.microsoft.com/en-us/library/windows/desktop/dd374098%0A%28v=vs.85%29.aspx describes the UI language fallback behaviour in Vista and later. Emulating this on earlier Windows versions (that lack LOCALE_SPARENT info for a locale) seems straightforward enough: just chop off the hyphen and anything that follows. -- Regards, Sam Morris -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Globalized Bundle?
Merging threads; just ensuring my reply doesn't get lost. Thanks. -Original Message- From: Ian Williams [mailto:iawil...@microsoft.com] Sent: Monday, January 09, 2012 11:15 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Globalized Bundle? Hmm, I'm a bit confused here. I'm under the impression that originally .wxl files were used for an MSI in conjunction with a few options passed to light.exe (-cultures:ja-jp -loc path to ja-jp .wxl file). And what you get it a Japanese localized MSI (this is all compiled into it). You're saying that the WixStdBA will look for .wxl files at runtime - great! That's exactly the sort of thing I'm looking for, that should avoid the creation of an installer for each language. But I can't figure out the usage pattern here. If I add things like !(loc.ProductName) to my bundle authoring, light complains that the localization variable !(loc.ProductName) is unknown. So at link time I have to point it to a particular .wxl file... and we're back where we've started! I also tried pointing light to multiple .wxls for each language I want but that doesn't seem to work either. What the piece I'm missing here that allows runtime localization decisions? As an aside, the most important thing for me really is to be able to choose the WiXVariable WixStdbaLicenseRtf at runtime based off of the system language. Not sure if even runtime loading of .wxls will accomplish this. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Monday, January 09, 2012 12:36 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Globalized Bundle? We do LCID because we still support WinXP SP2 On Mon, Jan 9, 2012 at 3:46 AM, Sam Morris s...@red-redemption.com wrote: On Sat, 07 Jan 2012 08:50:15 -0800, Rob Mensching wrote: The wixstdba will automatically search for a .wxl file of the system language (i.e. look in 1033 directory for english and 1041 for german and 1044 for japanese, or are those last two switched?). Failing to find a matching .wxl file will cause wixstdba to fall back to a .wxl in the root. There are a few bugs about localization open that need to be fixed before this works well but you can see the beginnings. Would you consider keying translations by the string representation of the locale name rather than the numeric locale ID? This will allow more intelligent fallback behaviour. Currently if I ship a .wxl file in the 1031 directory (de-DE) then a user with a UI language setting of 3079 (de-AT) will not see the German strings, even though they are closer to the user's preferred language than the default strings. http://msdn.microsoft.com/en-us/library/windows/desktop/dd374098 (v=vs.85).aspxhttp://msdn.microsoft.com/en-us/library/windows/desktop /dd374098%0A%28v=vs.85%29.aspx describes the UI language fallback behaviour in Vista and later. Emulating this on earlier Windows versions (that lack LOCALE_SPARENT info for a locale) seems straightforward enough: just chop off the hyphen and anything that follows. -- Regards, Sam Morris -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Globalized Bundle?
The wixstdba will automatically search for a .wxl file of the system language (i.e. look in 1033 directory for english and 1041 for german and 1044 for japanese, or are those last two switched?). Failing to find a matching .wxl file will cause wixstdba to fall back to a .wxl in the root. There are a few bugs about localization open that need to be fixed before this works well but you can see the beginnings. On Thu, Jan 5, 2012 at 2:59 PM, Ian Williams iawil...@microsoft.com wrote: I'm trying to investigate the viability of making my bundle installer globalized - that is, it is one installer that will look at the language of the system in order to choose how to present itself to the user (and perhaps what to install). I thought that was one of the advantages of using a bundle, but I'm realizing now that that doesn't seem to be part of the intent. For starters, I wanted to do something like PropertyRef Id=SystemLanguageID / !-- This is a wix property that stores the language windows is set to -- WixVariable Id=WixStdbaLicenseRtf Value=...[SystemLanguageId]...license.rtf / But I can't have a PropertyRef in a bundle. There are more issues that leave me to believe that bundles are not designed to be able to intelligently choose a language to present themselves in... at least with WixStdBA (been trying to avoid writing my own BA). Does anyone have any advice on what direction I should be going here? If this doesn't work I guess users must choose what language the installer will be in when the download it (so I need to make a different version of the .exe for each language using the !(loc.X) stuff). Thanks, Ian -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
