On 21 January 2016 at 22:13, Karl Berry <[email protected]> wrote: > Web browsers don't hyphenate words anyway. > > Yes they do, or can. I think it's abominable, but no one asked me :). > In code, they take it upon themselves to consider breaking lines at > explicit hyphens. > > So that's the whole reason the <span> is there, and I don't think it > should just go away. There might be a runnable example as part of the > initial submission, or we can create one ... -k
I wonder if there's any way to disable it globally for the entire page? Although that wouldn't be perfect as it can be turned on and off, affecting only a region within the Texinfo source. Maybe it could be included within the parent element, like <samp class="nocodebreak">--date</samp> instead of <samp><span class="nocodebreak">--date</span></samp>. This wouldn't help with <a href="<span class="nocodebreak">ftp://ftp.rfc-editor.org/in-notes/rfc3339.txt</span>"> though. The appearance of the output, like line breaks, changes for the HTML output, unlike the output for TeX, so I don't think it matters that much to control it. We don't force browsers to hyphenate at "-" in code if "@allowcodebreaks true" or to hyphenate elsewhere. I'd prefer it if customization of the HTML output (and other) could be done outside of the Texinfo source instead of adding new commands.
