The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Doug McIlroy <doug@cs.dartmouth.edu>
Cc: tuhs@tuhs.org, groff@gnu.org
Subject: Re: [TUHS] [groff] How to show all hyphenation points?
Date: Thu, 8 Nov 2018 11:49:09 -0500	[thread overview]
Message-ID: <20181108164907.xayhiclk5osnssly@crack.deadbeast.net> (raw)
In-Reply-To: <201811081630.wA8GUkXS135455@tahoe.cs.Dartmouth.EDU>

[-- Attachment #1: Type: text/plain, Size: 918 bytes --]

[adding groff@gnu back into CC]

I think the TUHS guys might be wondering where this topic came from. :)

At 2018-11-08T11:30:46-0500, Doug McIlroy wrote:
> > I have a vague intuition right now that the hyphenation decisions
> > ...
> > should be accessible without having to invoke the output driver.
> 
> Would't that require some way to detect a hyphenation event?
> Offhand, I can't think of a way to do that.

That's a harder problem than I was trying to crack; I just wanted to be
able to ask the underlying *roff where it _might_ hyphenate a word, not
where it actually ended up hyphenating one on the output.

> But if you know in advance what word's hyphenation is in
> question, you could switch environments, use the .ll 1u 
> trick in a diversion, and base your decision on the result.

That had not occurred to me; I am not au fait with diversions.  Thanks!

-- 
Regards,
Branden

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2018-11-08 20:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 16:30 Doug McIlroy
2018-11-08 16:49 ` G. Branden Robinson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181108164907.xayhiclk5osnssly@crack.deadbeast.net \
    --to=g.branden.robinson@gmail.com \
    --cc=doug@cs.dartmouth.edu \
    --cc=groff@gnu.org \
    --cc=tuhs@tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).