Ticket #11 (closed defect: fixed)
dealing with "document character encoding"
|Reported by:||firstname.lastname@example.org||Owned by:||email@example.com|
Browsers use the "document character encoding" when deciding how to encode query parameters. Communicating this well in this document is a problem, does this resolve it?
< target="UTR15"/>). In this case, retain the original character
< encoding as the "document character encoding". (DESIGN QUESTION:
< NOT WHAT MOST IMPLEMENTATIONS DO, CHANGE? ) </t>
target="UTR15"/>). There are some contexts (especially in
web browser contexts with URIs originally constructed as
the result of form processing) where the original
"document character encoding" is needed to properly interpret
the query parameters (see <xref target="webaddress"/>).