From: Michael S. Kaplan (firstname.lastname@example.org)
Date: Sat Oct 13 2007 - 21:18:54 CDT
From: "Doug Ewell" <email@example.com>
To: "Unicode Mailing List" <firstname.lastname@example.org>
Sent: Saturday, October 13, 2007 3:59 PM
Subject: Re: New FAQ page
> 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.
Actually, as usual Philippe is completely wrong and his .NET tangent is
about as off-topic as it could possibly have been.
The files that are up on the Unicode site are actually the source files used
to build the code page files in WINDOWS. The .Net framework is not the
source of the files on the site, and .NET does not use the Windows best-fit
mappings in >=2.0 unless you specify the appropriate fallback behavior
He is trying to prove one of those three lessons that Roger Fenwick learned
while he was at Oxford, the one about verbiage...
This archive was generated by hypermail 2.1.5 : Sat Oct 13 2007 - 21:19:26 CDT