[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Update of charset windows-1252, draft 3
As discussed, I am a better contact now than Mike Ksar here at
Microsoft.
I don't think that the Dr. International book should be considered as a
published specification. I'm certain that in the event of a discrepancy
between that book and the actual behavior or the Microsoft.com/globaldev
data that the book would "lose". It is an interesting resource for
people wanting a printed copy, but that book wasn't intended to be a
spec.
Otherwise I am happy with this draft.
- Shawn
> ---------------------------
> Charset name: windows-1252
> Charset aliases: (None)
> Suitability for use in MIME text:
> Yes, windows-1252 is suitable for use with subtypes of the "text"
> Content-Type. Note that windows-1252 is an 8-bit charset. Care should
> be taken to choose an appropriate Content-Transfer-Encoding.
> Published specification(s):
> 1) Dr. International "Developing International Software, Second
Edition",
> Microsoft Press, ISBN 0-7356-1583-7, 2003, p. 743-747
> 2) http://www.microsoft.com/globaldev/reference/sbcs/1252.htm
> ISO 10646 equivalency table:
>
http://www.unicode.org/Public/MAPPINGS/VENDORS/MICSFT/WINDOWS/CP1252.TXT
> Additional information:
> This is an update of an existing registration of this charset. This
> charset name is in use.
> Older versions of this charset have been registered as
> ISO-8859-1-Windows-3.0-Latin-1 and ISO-8859-1-Windows-3.1-Latin-1.
> This charset is also known as Windows Code Page 1252 or cp1252 for
> short; these are NOT aliases.
> The graphic (non-control) characters of Windows-1252 are a superset of
> the graphic characters of the ISO-8859-1 charset. See the range 80 to
> 9F (hex).
> Person & email address to contact for further information:
> Mike Ksar
> Email: mikeksar@microsoft.com
> Microsoft Corporation
> One Microsoft Way,
> Redmond, WA 98052
> U.S.A.
> Intended usage: COMMON