Lian >>Conditionally installing CHM file according to OS locale does not satisfy the requirement. My goal is that the >>user only install once, then the shortcut works for all locales. It is OK that the shortcut string is English for >>all locales, but this shortcut should load corresponding CHM file for each locale (e.g. ja-jp CHM for ja-jp >>locale, de-de CHM for de-de locale...). >> >>My plan is to install all the CHM files and have one shortcut pointing to an executable which loads corresponding CHM file for different locales.
With Davids method, the user would only install once and the correct locale CHM file and corresponding shortcut would be installed at that time. On a ja-jp machine, the ja-jp CHM file would be installed with a ja-jp shortcut. On a de-de machine, the de-de CHM is installed with the de-de shortcut. All from one MSI that only needs to be run once. This sounds like what you want unless you need the ability to switch locales after the install has been completed or you have different locales on the same machine for different users. What reason do you have for having all the locales to be installed when you install the application? A better way of asking maybe this. Your planned solution to your problem involves a call to an executable that determines which CHM to open. How does this executable determine what CHM file to use? Chris ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
