Yes, we support seven languages. If I pass UserLanguageID or SystemLanguageID in my var "LCID" and then pass it as a property to the MSI package in the form of TRANSFORMS=LCID.mst all is well for the supported languages, however an unsupported language results in an error because the transform does not exist. I have two msi packages in my chan which have a different set of 'supported' transforms. I like your approach and will check it out. I added the BAFunction.dll into the project (which meant I had to change to the extended bootstrapper), late last week. I plan to read the LCID var and then limit the range of LCIDs that I pass to each Msi package. Also if a user has a 'related' language we default to the nearest supported language. We support 1034 (Spanish) and when we detect Mexican or any other variant of Spanish we default to 1034 (rather than defaulting to English). This is standard behavior in our existing InstallScript projects. So I am working on implementing similar behavior with WiX. I am going to try out WiX 3.8 and I may still need to do some 'custom' processing of the property before passing it to the MSI. But thanks for telling me about how you used MsiPackage/@InstallCondition to address this issue.
-- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/My-experiences-making-a-multi-language-bundle-tp7208949p7587949.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
