> Because WiX v3.0 didn't check as thoroughly for codepage problems. IOW, > the problems always existed, WiX is just telling you about them now.
What went into the MSI database before? Were unrepresentable characters simply replaced by question marks or something? And is there any way I can revert to this behavior? Since our branding process lets third party OEMs supply text for the installer, I would rather have one or two slightly messed-up strings that the OEM can fix if anybody notices it (nobody ever did for the three years we used WiX 3.0), rather than failing the entire branding operation (which I am certain somebody would notice). ------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
