search

IETF-OPSAWG-WG / draft-ietf-opsawg-pcap

PCAP next generation file format specification
Other
272 stars 62 forks source link

Question about pcap draft #71

Closed fxlb closed 1 year ago

fxlb commented 4 years ago

Same URI two times in the generated text and pdf (not in html). Should be avoided?

11.2.  URIs

   [1] http://www.tcpdump.org/linktypes.html

   [2] http://www.tcpdump.org/linktypes.html
guyharris commented 4 years ago

I didn't see anything obvious in RFC 7991 to give an eref a name and to refer indirectly to a named eref; what you've come up with in #73 may be the best that can be done.

fxlb commented 4 years ago

Yes, it solves also the problem of missing URIs references in generated HTML.

fxlb commented 4 years ago

The generated HTML for pcapng draft has also missing URIs references like pcap one had before xref use.

guyharris commented 4 years ago

The generated HTML for pcapng draft has also missing URIs references like pcap one had before xref use.

As with pcap, so with pcapng; time for another pull request.

guyharris commented 3 years ago

So is the current generated HTML, as produced from extended Markdown, fixed, or does it still have those issues?

mcr commented 3 years ago

Guy Harris notifications@github.com wrote:

So is the current generated HTML, as produced from extended Markdown, fixed, or does it still have those issues?

The markdown generator has now fixed the hangIndent issue, if that's what you are referring to.