[EMAIL PROTECTED] (Judson Valeski) writes:
> We decided on the following proposal. dougt, rpotts, chak, dmose, gagan,
> valeski, and nhotta attended the meeting.
>
> URI's would accept, and store, only UTF8 encoded strings. Protocols not
> able to handle UTF8 (HTTP for example), would access the charset
> attribute (proposed) off of nsIURI to convert back to the original
> string. The charset would be set by the URI creator as they have the
> best charset context. Is nsIURI the right
> place for the charset attribute?
nhotta pointed out that calling the attribute charset might be a bit
confusing, and perhaps charsetEncodingHint might be better. Since
what's really being described is a hint to (perhaps) be used by the
specifical protocol handler for what charset to convert it to before
sending it back over the network.
One thing that those of us in the meeting were still a bit unsure of
was whether this is sufficient for all HTTP cases, given that in some
cases this should be "server charset", and in some cases the "document
charset", which will sometimes be different from each other (eg
Latin-1 web server serving up a Kanji page). Any guidance here would
be much appreciated...
Dan
--
