Opened 10 years ago

Closed 8 years ago

#11 closed defect (fixed)

dealing with "document character encoding"

Reported by: lmm@… Owned by: masinter@…
Priority: minor Milestone:
Component: 3987bis Version:
Severity: - Keywords:


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:

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"/>).


Change History (3)

comment:1 Changed 8 years ago by masinter@…

  • Owner set to masinter@…

What I really want to do here is to say that

  • an IRI is an abstract sequence of UCS or unicode characters
  • what's printed on the side of a bus or read aloud isn't an "IRI" but some presentation of an IRI, and subject to guidelines and warnings because a human is involved as a transcoder (reading or listening and then writing something into an input buffer)
  • what's contained in files in other charcter encodings is not quite an IRI, and also subject to translation rules that depend on the context.
  • The subject of "recognizing and extracting IRIs from plain text" as a special call-out of this translation.

Peter St. Andre wrote:
" Belongs in the processing spec (a.k.a. "Reschke-Weber"), specifically in text about on the topic of pre-processing."

We will need to get the Reschke/Weber/Barth? documents together to describe parsing and preprocessing specifically for HTML?

comment:2 Changed 8 years ago by masinter@…

Looking at this item again...

The section "Mapping Query Components" actually does address this. I'm not sure whether the "(pre)processing" may need to describe this in more detail?

comment:3 Changed 8 years ago by lmm@…

  • Resolution set to fixed
  • Status changed from new to closed

Looking at the bug reported and the comments,

actually seems to do a decent job of saying what needs to happen to query components.

So I'm marking this bug as "fixed".

Note: See TracTickets for help on using tickets.