[rfc-i] Non-contiguous URL numbers in text format

Jeffrey Yasskin jyasskin at chromium.org
Mon Aug 28 15:39:28 PDT 2017

Hi RFC folks,

If this isn't the right place to report a bug with xml2rfc, please
point me toward the right place. I found you via

The attached XML (generated via kramdown-rfc2629 from the attached
markdown) produces URLs [1] and [3], but not [2]. The three links are:

<t><eref target="https://example.com/link1">Link 1</eref></t>
<t><eref target="https://example.com/link2">https://example.com/link2</eref></t>
<t><eref target="mailto:link2 at example.com">link2 at example.com</eref></t>

And from that `xml2rfc test.xml` generates the following text:

1.  Introduction

   Link 1 [1]


   link2 at example.com [3]

2.  References

2.1.  URIs

   [1] https://example.com/link1

   [3] mailto:link2 at example.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: test.md
Type: text/markdown
Size: 422 bytes
Desc: not available
URL: <http://www.rfc-editor.org/pipermail/rfc-interest/attachments/20170828/e817a01f/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test.xml
Type: text/xml
Size: 1514 bytes
Desc: not available
URL: <http://www.rfc-editor.org/pipermail/rfc-interest/attachments/20170828/e817a01f/attachment.xml>

More information about the rfc-interest mailing list