I recently upgraded to WiX 3.5 (from 3.0) to solve a difxapp compatibility
problem, and now I've got different problem. Several of the localized
installers fail to build with LGHT0311 ("A string was provided with characters
that are not available in the specified database code page '1252'"). In some
languages, I found out-of-range characters in the corresponding .wxls (mostly
Unicode-y dashes and spaces), replaced them with boring ASCII, and the build
worked again. In other cases, I couldn't find the text light was complaining
about.
But the real question here is, what changed? Why didn't WiX 3.0 bug me about
these problems? I have the product building now, but since our company allows
third-party partners to create "branded" installers (with their own string
tables and images), I worry many of these will break in WiX 3.5.
It seems preposterous to me that, in 2011, I have to force all strings in an
installer to fit in a single ANSI code page. A years-old comment in the code
warned about the uninstaller becoming unintelligible if we try and use UTF-8,
and web searches on the subject have corroborated this ... does anyone have a
workaround for this problem? Because that's the only solution I can think of.
------------------------------------------------------------------------------
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
