ietf
[Top] [All Lists]

Re: xml2rfc is OK ( was: Re: XML2RFC must die, was: Re: Two different threads - IETF Document Format)

2009-07-08 04:33:16
Mark Andrews wrote:
In message <4A544405(_dot_)8020701(_at_)gmx(_dot_)de>, Julian Reschke writes:
Mark Andrews wrote:
I had wierd results with the following just printing out "Zone" and
not the rest of the lines in the table.

        <texttable>
          <ttcol align="left">Zone</ttcol>
          <c>10.IN-ADDR.ARPA</c>
          <c>16.172.IN-ADDR.ARPA</c>
          <c>17.172.IN-ADDR.ARPA</c>
...
That's a bug in the texttable processing code, which I'm currently fixing (download the new version later today...). Thanks for the report.

Will do.

(I just published the new release)

IPv6 reverse addresses are long.  Break and indent.  If you have
a better way I would be happy to hear it.

        <texttable>
          <ttcol align="left">Zone</ttcol>
          <c>0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.\</c>
          <c>&nbsp;&nbsp;&nbsp;&nbsp;0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA</c>
          <c>1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.\</c>
          <c>0&nbsp;&nbsp;&nbsp;&nbsp;.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA</c>
        </texttable>

Ok, that's an interesting case where non-breaking spaces are needed as a last resort.

Also, this case would be simpler if <c> allowed <vspace>, so you wouldn't need to split the contents into two table cells (which *will* look weird when read in HTML...).

...but then, we may be getting off-topic here, so if people want to discuss the xml2rfc vocabulary or the tools in more details we probably should move over to the xml2rfc mailing list.

BR, Julian
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf

<Prev in Thread] Current Thread [Next in Thread>