On Mon, Feb 14, 2011 at 02:02:11PM +0000, Philipp Kern wrote:
> On 2011-02-14, Klaus Ethgen <kl...@ethgen.de> wrote:
> > ~> LC_CTYPE=en_GB.utf-8 perl -e 'print "\x{00a3}\n";'
> > ~> LC_CTYPE=en_GB.utf-8 perl -e 'print "\x{00a3}\n";' | cat
> > Both gives the same result, a '£' sign as expected.
> 
> And what's the value in that demonstration?  Yes, you can treat UTF8 like a
> bytestream.  And the thread was about the problems that can arise of this.

Er, and tell me where exactly it makes sense to allow one encoding but not
another for a "bytestream"?

It appears that Python has a nasty bug where it ignores the encoding if
isatty(stdout) returns 0.  So let's go fixing or reporting that rather than
arguing about it.

-- 
1KB             // Microsoft corollary to Hanlon's razor:
                //      Never attribute to stupidity what can be
                //      adequately explained by malice.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110214143608.ga8...@angband.pl

Reply via email to