I guess this is more of an operating system problem than a WiX / MSI one but lets see if anyone else has hit it.
Scenario-1 ------------ 1. Shortcut created in a sub folder of 'Start menu' called 'xyz.lnk'. The 'Name' column for this shortcut is localized (i.e. transformed via language transforms). Also, the DisplayResourceDLL & DisplayDescriptionResourceDLL fields are populated to point to mui resource dlls. 2. The package is installed on Vista, under MUI with the display language in an east asian language (e.g zh-TW ) - with the system setting for 'language for non-unicode applications' set to the corresponding language (Chinese Traditional ) In this case, once installed, the shortcut appears correctly in traditional chinese, and so does the tooltip. However, upon switching the display language to English, the shortcut name remains in traditional chinese (but the description switches correctly). If the above scenario is repeated, without changing the 'language for non unicode applications' modified (i.e. left to English), the problem does not occur. Also, if the installation is done in a non east asian language before switching to English, the problem again, does not occur. Further investigation of this led to the 'desktop.ini' file that was created under the sub-folder of Start Menu, which appeared to have some encoding errors when pointing to the localized shortcut file name ( "立即建立家庭電影.lnk" appeared as "立即建立家庭電?影.lnk" - i.e. the extra question mark). Furthermore, the desktop.ini file was an 'ANSI' file. After manually creating this file in Unicode and writing the same entries, the shortcut display name switched correctly with MUI. Lastly, I tried using the SHSetLocalizedName api defined in "shlapi.h" - which i assume is the same one used internally by windows installer - to link up shortcut file to a resource dll (under the same conditions as described above in Scenario-1) - and the entry in the desktop.ini again appeared corrupted, which led to the display name not switching correctly with MUI. *any ideas*? btw: the obvious workaround for this problem would agreeably be to create the shortcut file with an english name and then point it to the resource dll, however - this mechanism will not work for XP since the MUI redirection is not available. -- Ali-Akber Saifee ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
