Review of draft-ietf-idnabis-bidi-04

Harald Alvestrand harald at alvestrand.no
Mon Aug 24 16:18:34 CEST 2009


Paul Hoffman wrote:
> This draft is not yet ready for publication. The text is still very confusing about the relationship between this document and RFC 3454. In many places, the wording makes it sound like this new algorithm is a replacement for that in RFC 3454, which it is not: it is the algorithm to use with IDNA2008.  I would be happy to do a thorough edit to remove this ambiguity and make it clear that, while the algorithm is an improvement on the old one, it does not "change" or "fix" or "replace" the old one.
>   
It changes the old definition in exactly the same meaning of the word 
"change" as the way IDNA2008 changes IDNA2003.

I'll send you the XML under separate cover; if you can make the changes 
you feel are needed, I can see if I agree with them.
> The terminology section needs to define "the end of the label". Tests 3 and 6 of section 2 are confusing without some definition.
>   
Will add "beginning" and "end" to the paragraph that says

        <t>In this memo, we use "network order" to describe the sequence of
        characters as transmitted on the wire or stored in a file; the terms
        "first", "next", "previous", "before" and "after" are used to 
refer to
        the relationship of characters and labels in network order.</t>

> Editorial:
> . . .
>    not fulfil.  This document therefore proposes replacing the RFC 3454
> s/fulfil/fulfill/
> . . .
>    "LTR" and "RTL" are abbreviations for "right to left" and "left to
>    right", respectively.
> s/"LTR" and "RTL"/"RTL" and "LTR"/
> . . .
>   5.  In an LTR label, only characters with the BIDI properties L, En,
>        ES, CS.  ET, ON and NSM are allowed.
> s/En/EN/
>   
Thanks, will fix.
> _______________________________________________
> Idna-update mailing list
> Idna-update at alvestrand.no
> http://www.alvestrand.no/mailman/listinfo/idna-update
>
>   



More information about the Idna-update mailing list