Michael Urman wrote:
> On 9/7/06, David Hopwood <[EMAIL PROTECTED]> wrote:
>
>>Yes. However, this is not a good idea for precisely the reason described
>>on that page (false detection of Unicode), and so any Unicode detection
>>algorithm in Python should only be based on detecting a BOM, IMHO.
>
Michael Urman wrote:
> On 9/7/06, Jeff Wilcox <[EMAIL PROTECTED]> wrote:
>
>>>From: "Paul Prescod" <[EMAIL PROTECTED]>
>>>1. On US English Windows, Notepad defaults to an encoding called "ANSI".
>>>"ANSI" is not a real encoding at all (and certainly not one from the
>>
>>On Japanese Windows 2000,
Michael Urman wrote:
> As for whether cp932 is the same as Shift JIS, David and I seem to
> disagree. While I lack hard data, the string '\\' round trips through
> either on my box.
I missed this part. On any single implementation, '\\' will usually round-trip
from Unicode -> Shift-JIS -> Unicode;
David Hopwood <[EMAIL PROTECTED]> writes:
>> Right, except BOMs break tons of Unix applications (and even
>> occasional Windows ones) which do not expect them.
>
> This problem is overstated. A BOM anywhere in a text causes no
> problem with display, and *should* be treated as an ignorable
> chara
On 9/9/06, Marcin 'Qrczak' Kowalczyk <[EMAIL PROTECTED]> wrote:
> Note that there are plenty of other characters that should be> treated as ignorable, so the applications that are broken for BOMs> are broken more generally.I disagree. UTF-8 BOM should not be used on Unix. It's not a reliable
method
On 9/7/06, Jeff Wilcox <[EMAIL PROTECTED]
> wrote:> From: "Paul Prescod" <
[EMAIL PROTECTED]>> 1. On US English Windows, Notepad defaults to an encoding called "ANSI".> "ANSI" is not a real encoding at all (and certainly not one from theOn Japanese Windows 2000, Notepad defaults to ANSI as it does
"Paul Prescod" <[EMAIL PROTECTED]> writes:
> text data cannot even be reliably processed on the desktop on which
> it was created (yes, even on Unix: look back in this thread).
Where?
> Do you have a positive prescription?
New communication protocols and newly created file formats designed
for
On 9/9/06, Marcin 'Qrczak' Kowalczyk <[EMAIL PROTECTED]> wrote:
"Paul Prescod" <[EMAIL PROTECTED]> writes:> text data cannot even be reliably processed on the desktop on which> it was created (yes, even on Unix: look back in this thread).
Where?http://mail.python.org/pipermail/python-3000/2006-Sept
Op do, 07-09-2006 te 12:21 -0700, schreef Paul Prescod:
> Guido has asked me to do some research in aid of a file encoding
> detection/defaulting PEP.
>
> I only have access to a small number of operating systems and language
> variants so I need help.
>
> If you have access to "German Windows XP
PEP: XXXTitle: Easy Text File Decoding
Version: $Revision$Last-Modified: $Date$
Author: Paul Prescod <[EMAIL PROTECTED]>
Status: DraftType: Standards Track
Content-Type: text/x-rstCreated: 09-Sep-2006
Post-History: 09-Sep-2006Python-Version: 3.0
Abstract
Python 3000 will use Unicode as the
Michael Chermside wrote:
> It doesn't necessarily imply that
> the traceback be materialized immediately upon exception creation
> (which is undesirable because we want exceptions lightweight enough
> to use for things like for loop control!)... but it might mean that
> pieces of the stack frame ne
11 matches
Mail list logo
