On May 12, 2005, at 03:00, [EMAIL PROTECTED] wrote:
> As was pointed out, I'm not American. I guess the problem stems
> from an
> American cultural assumption, though, in that Americans (I think)
> developed the
> ASCII character set without any thought for other languages.
At that tim
On May 12, 2005, at 02:42, Tony Meyer wrote:
>>
>> From the email address, chances are that this was a New Zealand
>> cultural
>>
> assumption. Ah, the French, lumping all English speakers under the
> American
> banner .
Touché. :D
-- Max
( What makes it even more unforgivable is that
On Wednesday, May 11, 2005, at 20:43 America/Chicago,
[EMAIL PROTECTED] wrote:
> I believe Max's guess was that the file is compressed with bzip (the
> first
> two characters will be BZ, as you found). Try doing:
>
import bz2
print bz2.decompress(data)
>
> Where data is a string co
[me, typo'ing]
>> hexidecimal representations of characters.
[Bob Gailer]
> Did you mean "hexadecimal"?
Sigh. Yes. I did a one character typo. Please forgive me.
=Tony.Meyer
___
Tutor maillist - Tutor@python.org
http://mail.python.org/mailman/lis
At 06:42 PM 5/11/2005, Tony Meyer wrote:
> You mean é? Oh, it is
perfectly printable. It's even on my
> keyboard (as unshifted 2), along with è, ç, à and ù. Ah,
American
> cultural assumption... ^^
>From the email address, chances are that this was a New Zealand
cultural
assumption. Ah, the
Quoting Max Noel <[EMAIL PROTECTED]>:
> You mean é? Oh, it is perfectly printable. It's even on my
> keyboard (as unshifted 2), along with è, ç, à and ù. Ah, American
> cultural assumption... ^^
I was waiting for someone to call me on that ...
As was pointed out, I'm not American. I guess th
> You mean é? Oh, it is perfectly printable. It's even on my
> keyboard (as unshifted 2), along with è, ç, à and ù. Ah, American
> cultural assumption... ^^
>From the email address, chances are that this was a New Zealand cultural
assumption. Ah, the French, lumping all English speakers under
On May 12, 2005, at 02:22, D. Hartley wrote:
> Max - yep, and the hint was "BUSY" (... BZ...)...
>
> Unfortunately that hint doesnt lead me anywhere (except to bz2, which
> involves compression, and didnt seem very likely).
>
> I went through and removed all the \x## 's that represented
> 'unprin
[D. Hartley]
> Max - yep, and the hint was "BUSY" (... BZ...)...
>
> Unfortunately that hint doesnt lead me anywhere (except to bz2, which
> involves compression, and didnt seem very likely).
>
> I went through and removed all the \x## 's that represented
> 'unprintable'/carraigereturn/etc characte
Max - yep, and the hint was "BUSY" (... BZ...)...
Unfortunately that hint doesnt lead me anywhere (except to bz2, which
involves compression, and didnt seem very likely).
I went through and removed all the \x## 's that represented
'unprintable'/carraigereturn/etc characters, but that wasnt it, ha
On May 12, 2005, at 01:50, [EMAIL PROTECTED] wrote:
chr(130)
> '\x82'
>
> If you look at http://asciitable.com/, you will see that ascii
> chracter 130 is
> an e with a tick on its head. This is not something you can find
> on your
> keyboard, so python can't/won't display it.
>
Quoting "D. Hartley" <[EMAIL PROTECTED]>:
> Does anyone have a hint as to what things like this:
> \xaf\x82\r\x00\x00\x01\
>
> refer to?
Basically, they are unprintable characters.
>>> ord('\x82')
130
>>> chr(130)
'\x82'
If you look at http://asciitable.com/, you will see that ascii chracter
12 matches
Mail list logo
