[Bug 26632] MultiByteToWideChar with MB_ERR_INVALID_CHARS doesn't fail for some code points.

http://bugs.winehq.org/show_bug.cgi?id=26632

--- Comment #7 from Sagawa  2011-04-02 23:10:41 CDT ---
(In reply to comment #5)
> AFAIK wine's unicode tables are generated directly from unicode.org data, and
> I'm sure it already was a request to customize that (case Windows does some
> things other way).

The Unicode tables is not a problem. The table doesn't cover
MB_ERR_INVALID_CHARS behavior. Without flags, the results (WCHARs) are same as
Windows.
In my opinion, wine raises an error for the conversion with
MB_ERR_INVALID_CHARS to some PUA code points (as Windows does). Currently wine
does raise a error when it meets a default Unicode character only.

(In reply to comment #6)
> What is the impact on the user of this problem?

For instance, encoding detection. In Japanese CP932, 0xFE is an undefined
character, not used in normalized sequence. But in EUC-JP (another encoding
system), it is a valid code sequence. 
In Windows, MB_ERR_INVALID_CHARS flag helps this.