This is never going to work for you. The problem is that Windows Installer files are ANSI (byte-oriented character sets) internally. They can have only one associated codepage, and it has to be one that can be set as the system default codepage - UTF-8 is sadly not allowed.
WiX can readily accept almost any script in its input files, because it is Unicode throughout. However, when it comes to writing out to the MSI file, it has to convert to the chosen codepage and this is where the characters are being lost. I would strongly recommend using satellite resource DLLs rather than registry entries if possible. Registry lookups are not free. If you have to persist with this approach, look at creating a language-neutral installer, which uses codepage 0, and a collection of language transforms which transform the MSI appropriately. However, the user will have to reinstall the product multiple times to get each additional language. -- Mike Dimmick -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony Hoyle Sent: 12 December 2007 12:16 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] UTF8 in registry Bob Arnson wrote: > Tony Hoyle wrote: >> I've been tasked with modifying an existing installer to include >> localised country names. Unfortunately wix seems to be mishandling >> the registry entries and replacing every extended character with '?'. >> > > You need to set a codepage that handles all the characters you want to > use. The default is the zero codepage and MSI replaces characters like > you described. > It needs to have the native names for 20 odd countries including korea and japan, so no single codepage is going to work. codepage 65001 appears to work but I found the following comment while searching around: "If system default code page (for non-unicode applications) is not 1252, 65001 is not available, which means CJK Windows does not recognize 65001." Is this true? A large chunk of our installed base is in Korea/China/Japan so we can't ship something that isn't compatible with their OS. The other option is a post-install installer application that sets up the registry manually, which is a pain for uninstall. Tony ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
