[rfc-i] I-D Action: draft-iab-rfc-nonascii-01.txt

Joe Hildebrand (jhildebr) jhildebr at cisco.com
Mon Feb 29 12:17:35 PST 2016

The one place we *do* perform sorting is in references, with sortRefs ='true'.  In the prototype prep tool, I'm preferring the reference's displayreference/@to, then falling back to the reference's @anchor.  I'm using javascript's "<" operator for comparison; I have no idea how that actually compares non-ascii strings.

One way to fix this would be to disallow non-ascii strings in reference anchors and displayreference/@to. If that's the approach, the non-ascii draft needs a note and the prep tool draft needs a step to check for those.

Joe Hildebrand

On 2/29/16, 1:11 PM, "rfc-interest on behalf of Joe Hildebrand (jhildebr)" <rfc-interest-bounces at rfc-editor.org on behalf of jhildebr at cisco.com> wrote:

>I agree that sorting is out of scope.  I'm fine with one of the drafts saying that the order of authors in the input file is maintained by the prep tool as well as the output formats.  Maybe in the framework draft? 
>Joe Hildebrand
>On 2/29/16, 11:51 AM, "rfc-interest on behalf of Brian E Carpenter" <rfc-interest-bounces at rfc-editor.org on behalf of brian.e.carpenter at gmail.com> wrote:
>>I just wondered whether we need to say anything about the sorting
>>order of non-ASCII names, or is that out of scope? I hope it is,
>>because it seems like a fiendishly hard problem. Maybe we do need
>>to say somewhere that the order in which the authors appear in the
>>xml source is the order in which they will appear in the RFC and in
>>the RFC index and citations.
>>   Brian
>>rfc-interest mailing list
>>rfc-interest at rfc-editor.org
>rfc-interest mailing list
>rfc-interest at rfc-editor.org

More information about the rfc-interest mailing list