But how would a system-wide default encoding help with any of these
situations? These situations are IN FACT caused by system-wide default
encodings used by naive programmers. Python should be part of the
solution, not part of the problem.

On 9/6/06, Oleg Broytmann <[EMAIL PROTECTED]> wrote:
> On Wed, Sep 06, 2006 at 03:08:21AM -0700, Paul Prescod wrote:
> ...
>    Unfortunately, the real world is a bit worse than that. There are many
> protocol and file formats that cary textual information and still don't
> provide a hint on encoding.
>    First, there are text files. Really, there are still text files. A user
> can dump a README file unto his/her personal FTP server, and the file
> ususally is in the local encoding.
>    MP3 tags. Real nightmare. Nobody follows the standard - tag editors
> write tags in the local encoding, and mp3 players interpret them in the
> local encoding.
>    FTP and other dumb protocols that transfer file names in the encoding
> local to the server without announcing that encoding in the metadata.
>
> Oleg.
> --
>      Oleg Broytmann            http://phd.pp.ru/            [EMAIL PROTECTED]
>            Programmers don't die, they just GOSUB without RETURN.
_______________________________________________
Python-3000 mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe: 
http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com

Reply via email to