[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #58962] Latin-1 NO-BREAK SPACE does not behave as documented
From: |
Dave |
Subject: |
[bug #58962] Latin-1 NO-BREAK SPACE does not behave as documented |
Date: |
Wed, 25 Aug 2021 03:59:12 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Firefox/45.0 |
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/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [bug #58962] Latin-1 NO-BREAK SPACE does not behave as documented,
Dave <=