Maybe it could even be done without the use of Accept-Charset?
I don't like the idea of an ever-growing Accept-Charset header.
(Efficiency issues.) Hmmm... perhaps clients should just say
"Accept-Charset: *"?
>If I were a commercial vendor of WWW browsers, I would probably set
>someone about the task of adding charset=xxx support to all the
>freeware products, because it'd probably be much cheaper than
>maintenace, and development costs associated with not supporting it
>correctly.
Netscape employees are not permitted to look at freeware source...
Don't know about other commercial vendors...
Erik