-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 André,
On 4/3/2009 6:43 PM, André Warnier wrote: > 4) the HTML specs are distinct from the HTTP specs. [...] It also > seems to be superfluous and confusing considering (1) and (2) above. > (Like, what if (1) and (4) specify different charsets/encodings ?). The HTML spec says that the Content-Type wins the argument ;) > Why hasn't a proposal for HTTP 2.x / HTML 5.x > come about, reconciling those aspects and establishing Unicode/UTF-8 as > the default (or only) encoding, for URLs as well as content ? http://dev.w3.org/html5/spec/Overview.html > 8) What is also missing in my view, is some more general proposal > covering the format of text files (and text streams), anywhere. To > alleviate any ambiguity, each text file/stream should contain at least a > short prefix indicating its MIME type and its charset/encoding. I always thought this was a good idea: http://en.wikipedia.org/wiki/Resource_fork > All the above is why I keep on seeing my name echoed back to me as > André, even on some well-known supposedly international websites. :( - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAknaUF8ACgkQ9CaO5/Lv0PAqHACfbVa11mljL/B7U6oLkkUI5/8k 3uEAn3wEFNHyTYjdYLAey+gbzffz1Vv6 =5qZ1 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
