Re: Python shell wont open idle or an exisiting py file

From	Terry Reedy <tjreedy@udel.edu>
Subject	Re: Python shell wont open idle or an exisiting py file
Date	2014-02-01 00:46 -0500
References	(1 earlier) <lcguq4$a3s$1@ger.gmane.org> <lchjk7$8og$1@ger.gmane.org> <CAPTjJmpc6+hSjTy9tn_AMNMVsdnfQh6E+GHx0a=SmJmJ5=5Uvw@mail.gmail.com> <52EC61FF.4060204@mrabarnett.plus.com> <CAPTjJmrPNEvo4D=ZYcFxadAbyYm4+r=c1rAr-Cvpmw2_SDNsTA@mail.gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.6268.1391233806.18130.python-list@python.org> (permalink)

Show all headers | View raw

On 1/31/2014 10:36 PM, Chris Angelico wrote:
> On Sat, Feb 1, 2014 at 1:54 PM, MRAB <python@mrabarnett.plus.com> wrote:
>> I think that some years ago I heard about a variation on UTF-8
>> (Microsoft?) where codepoint U+0000 is encoded as 0xC0 0x80 so that the
>> null byte can be used as the string terminator.
>>
>> I had a look on Wikipedia found this:
>>
>> http://en.wikipedia.org/wiki/Null-terminated_string
>
> Yeah, it's a common abuse of UTF-8. It's a violation of spec, but an
> understandable one. However, I don't understand why the first part -
> why should \0 become U+0000 but (presumably) the \a later on
> (...cs\accel...) doesn't become U+0007, etc?

Because only  \0 has a special meaning in a C string, and Tk is written 
in C and uses C strings.

-- 
Terry Jan Reedy

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Python shell wont open idle or an exisiting py file Terry Reedy <tjreedy@udel.edu> - 2014-02-01 00:46 -0500

csiph-web