Thank you, that confirms my current understanding :) I hadn't released that cultures were just for fall-backs and couldn't understand why light accepted multiple wxls of different locales when the MSI can only hold 1.
On 18 August 2010 14:53, Mike Carlisle <mike.carli...@gmail.com> wrote: > Thank you, that confirms my current understanding :) > > I hadn't released that cultures were just for fall-backs and couldn't > understand why light accepted multiple wxls of different locales when the > MSI can only hold 1. > > > On 18 August 2010 14:13, Nick Ramirez <nickra...@hotmail.com> wrote: > >> >> You are right. An MSI can only be localized for one language. What that >> means >> is actually pretty simple. If you look inside the MSI database (with a >> tool >> like Orca.exe), you'll see that many of the tables contain text (the >> Control >> table, for instance). Once the MSI is built, these strings are there, hard >> coded. >> >> When we're talking about -loc flags and -cultures and Light.exe, this is >> all >> happening before the MSI is formed. This all happens in the linking stage >> of >> the build process. At that time, it's up in the air what the final strings >> in the MSI will be set to. >> >> So, you can have more than one -loc flag, and yes, you can set -cultures >> to >> several languages. If the string Light is looking for isn't defined in the >> first culture, it falls back to the second and so on. For example: >> >> -cultures:en-us;en >> >> This will use .wxl files that specified en-us as their culture first. If >> it >> can't find a string there, it searches .wxl files that specified "en". If >> it >> can't find it there, you get a build-time error. When all is put together, >> you've got your MSI, with a mixture of code from .wxs files and .wxl >> files. >> >> When people talk about using transforms, they're saying that the transform >> is going to change the MSI at install time. This has nothing to do with >> Light or its flags. It's similar to applying a patch. It's a technique >> that's completely separate and involves making several fully functional >> MSIs >> that are hard coded in different languages, making diffs of them, and >> storing the diffs in transforms. That's the essence of making a patch. >> -- >> View this message in context: >> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Yet-another-localization-question-tp5431565p5436209.html >> Sent from the wix-users mailing list archive at Nabble.com. >> >> >> ------------------------------------------------------------------------------ >> 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
