Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] <br> is back, was: New xml2rfc release: v2.32.0

[Henrik Levkowetz <[e-mail]>]

>> I agree with this.  So again, I propose to permit <br> as a child element
>> of these elements, where I think the semantics of a <br> would be well-
>> defined:
>>
>>    blockquote
>>    dd
>>    dt
>>    em
>>    li
>>    name
>>    strong
>>    t
>>    td
>>    th
>>    title
>>    tt
>>
>> Should <sub> and <sup> be in that list?  If we compare with the places where
>> for instance <bcp14> is permitted, the answer would be 'yes'; but I'm not
>> sure it's the right thing to do.
>> ...
> For <title>, I will continue to ask about the use case (line break
> opportunity vs required line break vs title & subtitle), as this affects
> what would happen if it occurs in a <reference>, or if there's an <xref>
> with format="title”.

Of course we'd have to decide how to handle this in <reference> and <xref>.

My first suggestion would be to replace it with a simple space for those
cases, and let the local rendering do its thing based on that.

And as for probably every case where <br/> would be used as a fallback, it
would also be possible to come up with a more sophisticated semantic model
and schema.

But that does not negate the usefulness of having the <br/> fallback until
we have decided to adopt that more sophisticated model and schema.


	Henrik