Re: [PATCH 2/9] Protect literals from hyphenation.

[Thomas Dickey]

----- Original Message -----
| From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
| To: "Thomas Dickey" <dickey@his.com>
| Cc: "Ncurses Mailing List" <bug-ncurses@gnu.org>
| Sent: Saturday, September 23, 2023 6:28:44 PM
| Subject: Re: [PATCH 2/9] Protect literals from hyphenation.

| Hi Thomas,
| 
| Sorry for the unauthenticated mail; I'm travelling, but wanted to
| acknowledge the issue. Actually there are 9 occurrences of this problem in
| v2 of the patch.
| 
| Long story short, sequences like this:
| 
| (\fB\%
| 
| need to be rewritten as
| 
| \%(\fB
| 
| because of how *roff defines word boundaries, and the semantics of `\%`.
| 
| I can prepare a v3 probably tomorrow if you'd like.

That seems the easiest - since you'll have a reference version with your 
changes,
then my fixes are much smaller.

| Regards,
| Branden
| 
| On Sat, Sep 23, 2023, 16:07 Thomas Dickey <dickey@his.com> wrote:
| 
|> On Fri, Sep 22, 2023 at 12:58:16PM -0500, G. Branden Robinson wrote:
|> > Everything that is boldfaced is literal, so protect it from hyphenation.
|> > A few very short words that *roff won't hyphenate (like "tic") are left
|> > as-is.
|> >
|> > GNU troff (by default) won't hyphenate "color", but will "colors".
|> >
|> ...
|> > * man/curs_trace.3x: Do it.
|>
|> In this diff, there's one error:
|>
|>    Command-line Utilities
|>        The  command-line  utilities  such  as  tic(1) provide a verbose
|> option
|>        which extends the set of messages written using the curses_trace
|> func‐
|>        tion.   Both  of  these  (-v and curses_trace) use the same
|> variable (‐
|>        _nc_tracing), which determines the messages which are written.
|>
|> --
|> Thomas E. Dickey <dickey@invisible-island.net>
|> https://invisible-island.net

-- 
Thomas E. Dickey <dickey@invisible-island.net>
https://invisible-island.net