From: Doug Ewell (firstname.lastname@example.org)
Date: Sat Oct 13 2007 - 17:59:20 CDT
Philippe Verdy <verdy underscore p at wanadoo dot fr>
>> This is explicitly specified in the "best fit" mappings on the
>> Unicode site, which are based on .NET behavior, as Peter knows:
>> CPINFO 1 0x3f 0x003f ;Single Byte CP, Default Char = Question Mark
> Note however that the codepage conversion API (in the Windows SDK)
> allows an application to specify the behaviour for unmapped
> characters. Only the default value of this API is using a mapping to a
> question mark, but other behaviour is possible: returning en error or
> exception, using another default mapping (for example a SUB control).
All right, then:
This is explicitly specified in the "best fit" mappings on the Unicode
site, which are based on **DEFAULT** .NET behavior.
Which I'm sure is what is being used in the Windows apps where John
Hudson noticed the question marks.
-- Doug Ewell * Fullerton, California, USA * RFC 4645 * UTN #14 NEW URL --> http://home.roadrunner.com/~dewell <-- NEW URL http://www1.ietf.org/html.charters/ltru-charter.html http://www.alvestrand.no/mailman/listinfo/ietf-languages ˆ
This archive was generated by hypermail 2.1.5 : Sat Oct 13 2007 - 18:00:46 CDT