> 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 r
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
2 matches
Mail list logo
