Okay thanks, If 3.8 does correctly detect OS language and launch Burn wrapper in detected language then that should solve part of that issue.
As for your 2nd issue, are you talking about conditioning your MsiPackage so that it will only use your supportted language .mst's that you need to pass to your .msi as transforms? If so I do have a solution that works for that. It requred me to create 2 MsiPackage entries. One that is conditioned only on the SystemLanguageID's that I support and the other will is conditioned on SystemLanguageID not equalling my supported languages, and therefore it will only trigger the 1033.mst. If this was not what you meant then ignore this.... Thanks, -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/My-experiences-making-a-multi-language-bundle-tp7208949p7587948.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
