The MST doesn't have to be embedded, it's just "easier" to do it that way. You could just as easily have them external, and instead of Value=":[TransformFileName].mst" use Value="[TransformFileName].mst". Then you would need a <Payload ... for each supported MST so burn would put them in the right location (Payload element would need to be a child of the MsiPackage element).
I don't know of an easy way to get a variable conditionally assigned from another variable, based on a condition. That's where "but it may require a custom BA/UX to take the Lang ID's and assign the TransformFileName variable" came in. Not certain of this workaround, but one could utilize http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Multiple-shortcut-localizations-in-one-MSI-td3437236.html as a starting point. IE, you could have multiple locale specific shortcuts defined (each in their own component) and then condition the component based on the locale. I'd probably have a secure property that defaults to the SystemLanguageID/UserLanguageID but would allow it to be overridden from the command line. Based on this property, if your MSI package has that translation then use it, otherwise fall back to a default language. -----Original Message----- From: TimM [mailto:timmay...@smarttech.com] Sent: Friday, June 28, 2013 2:36 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Adding language transform .mst's to Burn Bundle Chain? Thanks for the response... No we are not going to be showing the MSI in UI. What is in the language .mst files are the application shortcuts. The names of the shortcuts are translated and therefore if say you are on a french machine then we want the shortcuts to be in French... We have not looked at embedding the .mst's in the MSI. How do we accomplish that step? So once we get the .mst's embedding into the .msi then we can use the following method to trigger the install to use the correct embedded .mst: <MsiPackage ...> <MsiProperty Name="TRANSFORM" Value=":[TransformFileName].mst" /> </MsiPackage> Where the [TransformFileName] = SystemLanguageID? If we only support selective languages then in the bundle how do we condition the value of TransformFileName to only be one of the supported languages and if SystemLanguageID is not a supported language then we set it to English? Thanks again for your help. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Adding-language-transform-mst-s-to-Burn-Bundle-Chain-tp7586986p7586997.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
