> From: Suresh Krishnan <[email protected]>
> Thanks for the quick response. I am happy with the RFC editor manual
> edit solution. I was just playing around with the xml and I found that
> the following formulation of the reference *does* provide the URL in the
> text and the html versions. I used
>
> <reference anchor="kyzivat-2"
> target="https://lists.cs.columbia.edu/pipermail/sip-implementors/2008-September/020426.html";>
>
> instead of the current
>
> <reference anchor="kyzivat-2">
> ...
> <format type="TXT"
> target="https://lists.cs.columbia.edu/pipermail/sip-implementors/2008-September/020426.html";
> />
Yes, I'd tried the "target" attribute of the "reference" element and
it didn't work for me. But yesterday I discovered that the failure
was due to an error in how I was running XML2RFC. I've updated the
draft to use the "target" attribute, and now the HTML version has
links. The text version has references like this:
[kyzivat-1]
Kyzivat, P., "Subject: Re: [Sipping] I-D ACTION:draft-
ietf-sipping-service-examples-11.txt", IETF Sipping
mailing list msg12181, October 2006, <http://www1.ietf.org
/mail-archive/web/sipping/current/msg12181.html>.
[kyzivat-2]
Kyzivat, P., "[Sip-implementors] draft-worley-service-
example-02", sip-implementors mailing list 020426,
September 2008, <http://lists.cs.columbia.edu/pipermail/
sip-implementors/2008-September/020426.html>.
Dale
_______________________________________________
Gen-art mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/gen-art
