Re: [iri] #25: Adapt rules for bidi components to those in IDNAbis

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: [iri] #25: Adapt rules for bidi components to those in IDNAbis

iri issue tracker
#25: Adapt rules for bidi components to those in IDNAbis

Changes (by adil@…):

 * keywords:   => bidi
 * owner:   => adil@…
 * status:  new => assigned


--
-----------------------------+-----------------------
 Reporter:  duerst@…         |       Owner:  adil@…
     Type:  defect           |      Status:  assigned
 Priority:  major            |   Milestone:
Component:  bidi-guidelines  |     Version:
 Severity:  -                |  Resolution:
 Keywords:  bidi             |
-----------------------------+-----------------------

Ticket URL: <http://trac.tools.ietf.org/wg/iri/trac/ticket/25#comment:2>
iri <http://tools.ietf.org/wg/iri/>


Reply | Threaded
Open this post in threaded view
|

Re: [iri] #25: Adapt rules for bidi components to those in IDNAbis

iri issue tracker
#25: Adapt rules for bidi components to those in IDNAbis


Comment (by adil@…):

 >Starting with this case, the IDNAbis work carefully reevaluated the bidi-
 related constraints on a 'component' (label in the DNS case), resulting is
 some additional changes

 Is there a link for these changes that I can check?

--
-----------------------------+-----------------------
 Reporter:  duerst@…         |       Owner:  adil@…
     Type:  defect           |      Status:  assigned
 Priority:  major            |   Milestone:
Component:  bidi-guidelines  |     Version:
 Severity:  -                |  Resolution:
 Keywords:  bidi             |
-----------------------------+-----------------------

Ticket URL: <http://trac.tools.ietf.org/wg/iri/trac/ticket/25#comment:3>
iri <http://tools.ietf.org/wg/iri/>


Reply | Threaded
Open this post in threaded view
|

Re: [iri] #25: Adapt rules for bidi components to those in IDNAbis

iri issue tracker
In reply to this post by iri issue tracker
#25: Adapt rules for bidi components to those in IDNAbis


Comment (by duerst@…):

 For IDNA and bidi, please see http://tools.ietf.org/html/rfc5893. The
 sections to look for in particular may be
 http://tools.ietf.org/html/rfc5893#section-4 and
 http://tools.ietf.org/html/rfc5893#section-7, but the whole document is
 worth reading for you (and anybody else interested) anyway.

 Please note that we can NOT just use the rules in RFC 5893 directly,
 because these rules have not been checked against characters such as '/',
 ':', '?', '#', and so on that appear as component separators in IRIs but
 not in IDNs. Harald Alvestrand has sent me the script that he used to
 check this (for '.' as a component separator only), but I have yet to try
 to adapt it to our needs (it's in Perl, and so the first thing I might do
 is to change it to Ruby :-(). I'll send you (Adil) a copy privately. If
 somebody else is still fluent in Perl (I used to be) and wants to give it
 a try, please contact me.

--
-----------------------------+-----------------------
 Reporter:  duerst@…         |       Owner:  adil@…
     Type:  defect           |      Status:  assigned
 Priority:  major            |   Milestone:
Component:  bidi-guidelines  |     Version:
 Severity:  -                |  Resolution:
 Keywords:  bidi             |
-----------------------------+-----------------------

Ticket URL: <http://trac.tools.ietf.org/wg/iri/trac/ticket/25#comment:4>
iri <http://tools.ietf.org/wg/iri/>