I suspect that wxl files were used to batch build the msi resulting in n msi packages for n cultures defined. I used to do what I think he is doing, using torch(or similar) to create mst files of the difference between my base msi (english msi) and each of the other cultures, named ":lcid.mst". Then used EmbedTranorms.exe (or similar script) to embed it into the base msi so I only needed to deploy one msi. All of that worked great when the base msi was deployed as a single file. But embedding the transforms results in problems when using a Burn driven model (I think because the ProductCode gets changed in the mst). The problems may not be obvious until a 'on-demand' install scenario kicks in. So to address that particular issue I went back to including each culture specific msi in my bundle (which has other issues). Maybe this is not related to the original question, but if planing to use Burn, don't embed.
-- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Embedded-Transforms-for-L10n-and-how-to-display-them-tp7598340p7598364.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
