[rfc-i] xml2rfc issue

erik.wilde at dret.net (Erik Wilde) Thu, 04 February 2016 00:18 UTC

From: erik.wilde at dret.net (Erik Wilde)
Date: Wed, 3 Feb 2016 16:18:00 -0800
Subject: [rfc-i] xml2rfc issue
In-Reply-To: <026c01d15ee0$3e9b5eb0$bbd21c10$@augustcellars.com>
References: <569ECD88.6050800@dret.net> <08865843-A8BB-430A-AE6A-0F7E715DF4DF@rfc-editor.org> <569FCE6B.7060503@att.com> <56B0F8C9.3030705@dret.net> <56B24BEE.7070701@gmail.com> <56B250B9.40806@dret.net> <026c01d15ee0$3e9b5eb0$bbd21c10$@augustcellars.com>
Message-ID: <56B298B8.2080700@dret.net>

On 2016-02-03 16:08, Jim Schaad wrote:
> This looks like a case where the HTML output should be different from the
> text output.  In the text output there has been a section added to the
> bibliography for the eref targets as putting the url inline is not
> necessarily what is desired.

but that's not what 
https://tools.ietf.org/id/draft-wilde-registries-00.txt looks like. what 
happens there (as well as in the html-ized txt version 
https://tools.ietf.org/html/draft-wilde-registries-00) is that for the 
eref element, textual references [1] and [2] are generated, but they 
link to the bibliographic references section instead of the URIs that 
were actually specified in the input XML. in both cases, the 
eref/@target is completely ignored, and instead a reference is generated 
to something completely unrelated.

cheers,

dret.