xml2rfc mistakenly thinks it's ok to add a line-break in the middle of "S/MIME"

[dkg]

Describe the issue

Over on draft-ietf-lamps-header-protection-14 the text version reads:

   Privacy and security issues regarding email Header Protection in S/
   MIME and PGP/MIME have been identified for some time.  Most current

This is from the source XML:

<t>Privacy and security issues regarding email Header Protection in S/MIME and PGP/MIME have been identified for some time.
Most current 

I'd like to ensure that there's no linebreak in either "S/MIME" or "PGP/MIME" (the WG chair suggests the same concern). Any suggestions on how to improve the situation?

Code of Conduct

• [X] I agree to follow the IETF's Code of Conduct

[kesara]

You can use a Unicode hack like the word joiner ⁠. Changing how xml2rfc breaks lines is another option but it might have undesired effects on previous documents.

[cabo]

Clearly, this is something where authoring tools could help. E.g., declare S/MIME as a non-breakable term (automatically generating the word joiners Kesara mentioned). (Note that there are other slash-joined terms where you very much do want line breaking to occur.)

[cabo]

Clearly, this is something where authoring tools could help.

Please see https://github.com/cabo/kramdown-rfc/commit/adf04a2 for an experimental solution that is now in 1.6.31 — feedback requested.

[cabo]

More about <nobr> support in kramdown-rfc: https://mailarchive.ietf.org/arch/msg/rfc-markdown/umCatJwgKIhYF3yRRGdRhKVSy4U