Opened 9 years ago

Closed 8 years ago

#66 closed defect (fixed)

Allow %-encoding to punycode conversion for ireg-name?

Reported by: duerst@… Owned by:
Priority: major Milestone:
Component: 3987bis Version:
Severity: - Keywords:


Taken out of draft -04:
DESIGN QUESTION: What about e.g. in an IRI? Will that get converted to punycode, or not?

Change History (2)

comment:1 Changed 8 years ago by masinter@…

Section 3.4.2. Mapping using Punycode

should first require that sequences of %xx hex-encoded octets be translated back to unicode if they are valid UTF-8 sequences, and that sequences that are not valid UTF-8 are not allowed, should be left alone (since there is no valid conversion to punycode.)

comment:2 Changed 8 years ago by masinter@…

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

Resolution: inserted at top of section 3.4.2 Mapping using Punycode:

If there are any sequences of <pct-encoded>, and their
corresponding octets all represent valid UTF-8
octet sequences, then convert these back to Unicode
character sequences. (If any <pct-encoded> sequences are not
valid UTF-8 octet sequences, then leave the entire field as is
without any change, since punycode encoding would not succeed.)

Note: See TracTickets for help on using tickets.