Re: ASCII and Unicode

2013-12-08 Thread rusi
On Monday, December 9, 2013 1:41:41 AM UTC+5:30, giacomo boffi wrote: > the wrong one... i.e, the one JUST BEFORE your change of > subject --- if i look at the "ellipsis" post, i see the same encoding > that you have mentioned > sorry for the confusion And thank you for pointing the way to the c

Re: ASCII and Unicode

2013-12-08 Thread giacomo boffi
Steven D'Aprano writes: > On Sat, 07 Dec 2013 17:05:34 +0100, giacomo boffi wrote: > >> Steven D'Aprano writes: >> >>> Ironically, your post was not Unicode. [...] Your post was sent using >>> a legacy encoding, Windows-1252, also known as CP-1252 >> >> i access rusi's post using a NNTP serve

Re: ASCII and Unicode

2013-12-08 Thread rusi
e he used the ellipsis characters: > Subject: Re: Managing Google Groups headaches > Date: Thu, 5 Dec 2013 23:13:54 -0800 (PST) > Content-Type: text/plain; charset=windows-1252 > Then his reply to me: > Subject: Re: ASCII and Unicode [was Re: Managing Google Groups headaches] &

Re: ASCII and Unicode

2013-12-08 Thread Steven D'Aprano
013 23:13:54 -0800 (PST) Content-Type: text/plain; charset=windows-1252 Then his reply to me: Subject: Re: ASCII and Unicode [was Re: Managing Google Groups headaches] Date: Fri, 6 Dec 2013 18:33:39 -0800 (PST) Content-Type: text/plain; charset=UTF-8 And finally, his reply to you: Subj

Re: ASCII and Unicode

2013-12-08 Thread rusi
On Saturday, December 7, 2013 9:35:34 PM UTC+5:30, giacomo boffi wrote: > Steven D'Aprano writes: > > Ironically, your post was not Unicode. [...] Your post was sent > > using a legacy encoding, Windows-1252, also known as CP-1252 > i access rusi's post using a NNTP server, > and in his post i

Re: ASCII and Unicode

2013-12-07 Thread giacomo boffi
Steven D'Aprano writes: > Ironically, your post was not Unicode. [...] Your post was sent > using a legacy encoding, Windows-1252, also known as CP-1252 i access rusi's post using a NNTP server, and in his post i see Content-Type: text/plain; charset=UTF-8 is it possible that what you see is

Re: ASCII and Unicode [was Re: Managing Google Groups headaches]

2013-12-06 Thread Chris Angelico
On Sat, Dec 7, 2013 at 2:16 PM, rusi wrote: > On Saturday, December 7, 2013 8:11:45 AM UTC+5:30, Chris Angelico wrote: >> On Sat, Dec 7, 2013 at 1:33 PM, rusi wrote: >> > That seems to suggest that something is not right with the python >> > mailing list config. No?? > >> If in doubt, blame someo

Re: ASCII and Unicode [was Re: Managing Google Groups headaches]

2013-12-06 Thread rusi
On Saturday, December 7, 2013 8:11:45 AM UTC+5:30, Chris Angelico wrote: > On Sat, Dec 7, 2013 at 1:33 PM, rusi wrote: > > That seems to suggest that something is not right with the python > > mailing list config. No?? > If in doubt, blame someone else, eh? > I'd first check what your browser's

Re: ASCII and Unicode [was Re: Managing Google Groups headaches]

2013-12-06 Thread MRAB
On 07/12/2013 02:41, Chris Angelico wrote: On Sat, Dec 7, 2013 at 1:33 PM, rusi wrote: That seems to suggest that something is not right with the python mailing list config. No?? If in doubt, blame someone else, eh? I'd first check what your browser's actually sending. Firebug will help ther

Re: ASCII and Unicode [was Re: Managing Google Groups headaches]

2013-12-06 Thread Chris Angelico
On Sat, Dec 7, 2013 at 1:33 PM, rusi wrote: > That seems to suggest that something is not right with the python > mailing list config. No?? If in doubt, blame someone else, eh? I'd first check what your browser's actually sending. Firebug will help there. See if your form fill-out is encoded as

Re: ASCII and Unicode [was Re: Managing Google Groups headaches]

2013-12-06 Thread rusi
On Saturday, December 7, 2013 12:30:18 AM UTC+5:30, Steven D'Aprano wrote: > On Fri, 06 Dec 2013 05:03:57 -0800, rusi wrote: > > Evidently (and completely inadvertently) this exchange has just > > illustrated one of the inadmissable assumptions: > > "unicode as a medium is universal in the same wa

Re: ASCII and Unicode [was Re: Managing Google Groups headaches]

2013-12-06 Thread Chris Angelico
On Sat, Dec 7, 2013 at 6:00 AM, Steven D'Aprano wrote: > - character 33 was permitted to be either the exclamation > mark ! or the logical OR symbol | > > - consequently character 124 (vertical bar) was always > displayed as a broken bar ¦, which explains why even today >

Re: ASCII and Unicode [was Re: Managing Google Groups headaches]

2013-12-06 Thread Roy Smith
Steven D'Aprano pearwood.info> writes: > Yes, it appears that MT-NewsWatcher is *deeply, deeply* confused about > encodings and character sets. It doesn't just assume things are ASCII, > but makes a half-hearted attempt to be charset-aware, but badly. I can > only imagine that it was written b

Re: ASCII and Unicode [was Re: Managing Google Groups headaches]

2013-12-06 Thread Gene Heskett
On Friday 06 December 2013 14:30:06 Steven D'Aprano did opine: > On Fri, 06 Dec 2013 05:03:57 -0800, rusi wrote: > > Evidently (and completely inadvertently) this exchange has just > > illustrated one of the inadmissable assumptions: > > > > "unicode as a medium is universal in the same way that