Message129239
> Accepting all common forms for
> encoding names means that you can usually give Python an encoding name
> from, e.g. a HTML page, or any other file or system that specifies an
> encoding.
I don't buy this argument. Running attached script on http://www.iana.org/assignments/character-sets shows that there are hundreds of registered charsets that are not accepted by python:
$ ./python.exe iana.py| wc -l
413
Any serious HTML or XML processing software should be based on the IANA character-sets file rather than on the ad-hoc list of aliases that made it into encodings/aliases.py. |
|
Date |
User |
Action |
Args |
2011-02-24 02:10:20 | belopolsky | set | recipients:
+ belopolsky, lemburg, georg.brandl, pitrou, ezio.melotti, mrabarnett |
2011-02-24 02:10:19 | belopolsky | set | messageid: <1298513419.85.0.00455767376339.issue5902@psf.upfronthosting.co.za> |
2011-02-24 02:10:19 | belopolsky | link | issue5902 messages |
2011-02-24 02:10:19 | belopolsky | create | |
|