From: Phil!Gregory Date: 21:42 on 11 May 2004 Subject: Charset Abuse Okay, getting everyone on a single, encompassing character set/encoding is pretty much a pipe dream. But why can't tools at least communicate what charset they're using? I'm used to getting web paged that misreport their charsets. When I read things like "I m sure it s ok", I can generally tell w3m, "Ignore what you were told; this page is in CP1254." This doesn't work if the content was written in CP1254 but the publishing tool turned those 0x92 apostrophes into ’ HTML entities, which is just wrong. This isn't really a rant directed at any one thing in particular. I just wish all this stuff with character sets happened transparently and that I wouldn't have to have learned what little I do know about the whole process. Like so many things, it should just _work_.
From: John Sinteur Date: 06:07 on 12 May 2004 Subject: Re: Charset Abuse -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11-mei-04, at 22:42, Phil!Gregory wrote: > I'm used to getting web paged that misreport their charsets. Get me drunk one evening and get me to talk about Oracle and charsets... brrrrr. When it comes to charsets, software is still following the "ascii a stupid question, get a stupid ansi" rule... - -John -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFAobD/YffhuCsYUkURAu2/AKD0MuoT56f3XkjrLN+8WBouHl1yhQCgoTB1 55uqSZtVgPpp+fb5v6wDK/Q= =FrkR -----END PGP SIGNATURE-----
Generated at 10:28 on 16 Apr 2008 by mariachi