From: bakul@bitblocks.com (Bakul Shah)
Subject: [TUHS] [groff] The hyphenation algorithm produces wrong results
Date: Sun, 4 Mar 2018 13:00:22 -0800 [thread overview]
Message-ID: <645D5FCC-7AAB-43D0-8035-FABB23986EAA@bitblocks.com> (raw)
In-Reply-To: <CAC20D2OABQOq6w230j3NddaX=bRQ-963zBD=uzXHMDYY1S7V1w@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]
> On Mar 4, 2018, at 12:42 PM, Clem Cole <clemc at ccc.com> wrote:
>
>
>> On Sun, Mar 4, 2018 at 3:23 PM, Doug McIlroy <doug at cs.dartmouth.edu> wrote:
>>
>> I hadn't realized that groff hyphenation had been taken from
>> Tex, not troff. Is that becuase Tex did a better job, or
>> because troff's was deemed proprietary?
>>
>
> Given the author, I would guess the later as he wanted to be FOSS and would not have looked at the ditroff source - but that guess is worth just that ;-)
I remembered reading about Knuth's line-breaking algorithm in
Software Practice & Experience in early eighties and being quite
impressed with it. So may be that clear description of the algorithm
has something to do with it? Ah, here it is:
“Breaking Paragraphs into lines” by Donald Knuth & Plass,
SP&E, Volume 11, issue 11, Nov. 1981
(Download from Wiley is not free)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180304/3b71374a/attachment.html>
next prev parent reply other threads:[~2018-03-04 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 20:23 Doug McIlroy
2018-03-04 20:42 ` Clem Cole
2018-03-04 21:00 ` Bakul Shah [this message]
2018-03-04 21:32 ` Toby Thain
2018-03-04 21:50 ` Ralph Corderoy
2018-03-04 22:36 ` Bakul Shah
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=645D5FCC-7AAB-43D0-8035-FABB23986EAA@bitblocks.com \
--to=bakul@bitblocks.com \
/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).