Anthony J. Bentley said:
> The sane place is the HTTP header. Well, saner would be to assume UTF-8
> by default, but this is the next best option.
No. There is only one sane place for stating encoding: the bloody
standard. It should unambiguously require that no other encoding then
UTF-8 may be used for HTML5, and that browser should not render document
that failed UTF-8 validation.
If UTF-8 ever becomes inadequate for some reason, there should be HTML6
(or whatever next number will be then), that states the next sane
encoding.
--
Dmitrij D. Czarkoff
Received on Fri Oct 31 2014 - 21:48:13 CET