Opened 9 years ago

Closed 8 years ago

#26 closed defect (fixed)

disallow combining characters at start of a component

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


This is issue from the old issues list. This issue is related to issues #25 and #16.

Change History (4)

comment:1 Changed 9 years ago by duerst@…

  • Owner set to duerst@…

from editorial teleconference 2010-09-28:

Ticket #26: disallow combining characters at start of a component

Addison: issue is that we don't want a combining mark to modify a separator

Addison: split first and then interpret the pieces, or interpret the entire string?

Larry: from an IRI perspective, significant characters matter

Martin: I think we need to say that parsing is first, a '/' followed by a combining mark is still as '/'

Addison: "MAY use combining characters at start of component but you ought to avoid it"

ACTION ITEM: Martin to write proposed text

Larry: three categories -- (1) reasonable, (2) legal but a bad idea, (3) illegal -- we seem to be moving more things from (3) to (2) and it would be good to be somewhat consistent about that

Martin: I think these are just a few instances

Addison: let's take these on a case-by-case basis

comment:2 Changed 8 years ago by masinter@…

Peter St Andre wrote: #26 - I think it's fine to say this is legal but a bad idea.
Chris Weber agreed.

Text still needs to be written and inserted.

comment:3 Changed 8 years ago by duerst@…

I propose the following text, to be added in the section "Limitations on UCS Characters Allowed in IRIs":

--- C:/Users/duerst/AppData/Local/Temp/draft-ietf-iri-3987bis.xml-revBASE.svn000.tmp.xml	木 3  1 19:10:21 2012
+++ C:/Data/ietf-iri/draft-ietf-iri-3987bis/draft-ietf-iri-3987bis.xml	木 3  1 19:16:29 2012
@@ -930,6 +930,13 @@
     includes many look-alikes of "space", "delims", and "unwise",
     characters excluded in <xref target="RFC3491"/>.</t>
+  <t hangText="c.">At the start of a component, the use of combining
+    marks is strongly discouraged. As an example, a COMBINING TILDE OVERLAY
+    (U+0334) would be very confusing at the start of a &lt;isegment>.
+    Combined with the preceeding '/', it might look like a  solidus with
+    combining tilde overlay, but IRI processing software will parse
+    and process the '/' separately.</t>

comment:4 Changed 8 years ago by duerst@…

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

fixed in revision 97 as proposed in comment 3

Note: See TracTickets for help on using tickets.