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

[Julian Reschke <[e-mail]>]

On 18.10.2019 19:36, Henrik Levkowetz wrote:
> ...
>   1) https://www.ietf.org/id/draft-levkowetz-xml2rfc-v3-implementation-notes-10.html
>      (or, if you prefer)
>      https://www.ietf.org/id/draft-levkowetz-xml2rfc-v3-implementation-notes-10.txt

This IMHO is a case of "this is a good place for a line break, but it's
not required here". <br/> is unconditional. Previously, the Production
Center has handled this by adding NBSPs in places where no line break
was wanted. (not ideal, I agree, but workable).

>   2) In a PDF rendering received from the RPC, the title of RFC8648-to-be,
>      "RADIUS Attributes for Softwire Mechanisms Based on Address plus Port (A+P)"
>      broke across lines as follows:
>
>        RADIUS Attributes for Softwire
>        Mechanisms Based on Address plus Port (A
>        +P)
>
>      which is less than perfect.  Having <br/> as a tool makes sense to me
>      here too.

No. I'd question why the render breaks the line there, and not before
"(A+P)". This really looks like a bug to me.

 > ...

Best regards, Julian