RE: data for cp1252

From: Shawn Steele <>
Date: Sat, 8 Dec 2012 00:41:23 +0000

It's a variation. The undefined codepoints in 1252 probably shouldn't be used, and I can't imagine that adding a code page helps anything, nor that changing an existing behavior helps anything. People really should be using UTF-8.


From: Buck Golemon []
Sent: Friday, December 7, 2012 4:34 PM
To: Shawn Steele
Cc: unicode
Subject: Re: data for cp1252

I've been told that bestfit1252 wasn't meant to redefine the cp1252 mapping, although its first line declares "CODEPAGE 1252".

Is it a separate encoding or not?

If so, I'll submit a new "bestfit1252" to the python stdlib.
If not, I believe the cp1252 mapping needs brought into line.

On Fri, Dec 7, 2012 at 4:27 PM, Shawn Steele <<>> wrote:
Received on Fri Dec 07 2012 - 18:45:07 CST

This archive was generated by hypermail 2.2.0 : Fri Dec 07 2012 - 18:45:08 CST