[rfc-i] Bring Back the BR! Re: typesetting poetry
loa at pi.nu
Mon Oct 12 05:23:49 PDT 2015
Just to brood - we had a <vspace=n> discussion about 700 mails ago.
My take away from that discussion was
- I'm not convinced
- I was supposed to understand that I don't need vspace or something
- and that if I did there were far more complicated ways of doing
the same thing
Now I hear that
- <br> within <th> and <td> will work, but not within <t>
I don't think this is worth crying over, and that a substantial part of
people that write drafts that I will have to review and sort out will
continue to do so in Word or nroff.
On 2015-10-12 16:15, Miek Gieben wrote:
> [ Quoting <dev+ietf at seantek.com> in "Re: [rfc-i] Bring Back the BR! Re:
> ..." ]
>>> On 9/5/2015 7:56 AM, Donald Eastlake wrote:
>>>> Section 1.1 of RFC 6325 is also a poem.
>>> See: a modern reference!
>> To clarify and modulate my outburst:
>> There is in fact a <br> (in v3 xml2rfc-15 and beyond), but it only
>> appears as the child of a <th> or <td> element; it cannot appear in a
>> <t> element (aka paragraph).
>> I suppose that means that poetry, and pseudocode, can appear inside
>> tables (namely tables with one column and one row), but not inside
>> "text" per-se. Inside <th> and <td>, <t> is mutually exclusive with
>> the other elements including <br>. I suppose that if your poetry or
>> pseudocode has multiple paragraph-like divisions (e.g., multiple
>> stanzas, multiple verses, multiple function blocks), you need to put
>> them in multiple cells or rows. Not really sure about the wisdom of that.
> <br> only solves the line-break. Leading whitespace (for instance) is
> also a
> problem. Basically: for poetry you'll need a paragraph-type where *all*
> whitespace is significant.
> Miek Gieben
> rfc-interest mailing list
> rfc-interest at rfc-editor.org
More information about the rfc-interest