Windows Installer, while supporting using transforms for localization purposes, doesn't dictate how those transforms are to be named, distributed, or invoked in any "canonical" way. Thus, given the variety of groups that have engineered different approaches to deal with this, there isn't away for the linker to do it all in "one step". Instead, once you have identified how you will do it, between the toolset and the SDK you have all the necessary tools to create whatever you engineer.
-----Original Message----- From: Mike Carlisle [mailto:moik...@hotmail.com] Sent: Tuesday, August 17, 2010 4:09 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Yet another localization question Hi, Sorry I've been reading through the localization threads and blogs and getting more confused. It seems to localize the MSI I need to use transforms and apply these at install time. My question is why then does the linker accept multiple cultures and WXL files when it compiles the MSI? What is the purpose if not to produce a single MSI with multi-language support? Am I missing something? Thanks, Mike ---------------------------------------------------------------------------- -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-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 Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
