[rfc-i] xml2rfc issue

Brian E Carpenter brian.e.carpenter at gmail.com
Wed Feb 3 16:30:53 PST 2016


On 04/02/2016 13:18, Erik Wilde wrote:
> 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.

Or to put it another way, <eref/> doesn't do what draft-iab-xml2rfcv2-02 says it should
do, if the element has text content. If there is no text content, it works as intended.
That's been true since 2007 to my personal knowledge.

Anyway - not really a topic for this list.

   Brian


More information about the rfc-interest mailing list