[bug #58962] Latin-1 NO-BREAK SPACE does not behave as documented

[Dave]

Follow-up Comment #2, bug #58962 (project groff):

[comment #0 original submission:]
> I believe the documented behavior is more sensible than the
> actual behavior.  But that's a judgment call and open to debate.

The Texinfo manual is increasingly subscribing to this view as well.

Commit d19a3b98
<http://git.savannah.gnu.org/cgit/groff.git/commit/?id=d19a3b98> (from a week
before this bug was filed) says "\ " is "not optimal in most situations."

Last week's commit b20ff768
<http://git.savannah.gnu.org/cgit/groff.git/commit/?id=b20ff768> reinforced
this, saying "Usually you want one of the following escapes instead" of "\ ",
and further clarifying, "often '\~'."

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?58962>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/