Hi again Branden,
I'll let others respond regarding the morality of dangling hyphens on
the last line. :-)
On 30/8/24 16:38, G. Branden Robinson wrote:
At 2024-08-30T16:29:03+1000, Robert Thorsby wrote:
I wouldn't call myself a typographer but I refuse to allow hyphens to
break, usually via '
> .hlm nSet the consecutive automatically hyphenated line limit
>to to n. A negative value means "no limit".
What happens after that count is reached is that the next
line is stretched wide, simply to avoid hyphenation (unless
.na is used, in which case the line is simply broke
> \s[-X]\H[+X]text to be kerned goes here\H[0]\s0
I believe distorting the shapes of letters is even more frowned
upon in typesetting circles than consecutive hyphenation is.
As a practical approach to manually optimizing the line
breaks in a paragraph, I have found that twiddling the space
siz
> However, no matter what you do, you simply *cannot* end the last line
> of a column or page with a hyphen.predicting
Alas, it happens regularly in real life.
The groff line-filling algorithm would have a hard time predicting a page
break, for the break is usually the result of a yet-unseen .br,
On 30/8/24 20:54, Tadziu Hoffmann wrote:
\s[-X]\H[+X]text to be kerned goes here\H[0]\s0
I believe distorting the shapes of letters is even more frowned
upon in typesetting circles than consecutive hyphenation is.
I agree that if the distortion becomes visible then it was the wrong
tool fo
On Fri, Aug 30, 2024, Douglas McIlroy wrote:
> > However, no matter what you do, you simply *cannot* end the last line
> > of a column or page with a hyphen.predicting
>
> Alas, it happens regularly in real life.
> ...
> Back to Branden's original question. I woulld expect the hyphenation count
>
> > I believe distorting the shapes of letters is even more frowned
> > upon in typesetting circles than consecutive hyphenation is.
>
> Tadziu, were you referring to your language (where I *think*
> hyphenation would always be necessary)?
Sorry if my wording was a bit vague. I was referring t
Hi folks,
Those of us who worked with groff 1.22.4 may remember a couple of
diagnostic messages that gobsmacked one with their incomprehensibility.
Here's the source code that produced them.
error("can't transparently output node at top level");
error("can't translate %1 to special character
Congrats, Branden!
[1] https://xkcd.com/149/
Fixed that for you:
[image: sandwich.png]
On Sat, 31 Aug 2024 at 08:26, G. Branden Robinson <
g.branden.robin...@gmail.com> wrote:
> Hi folks,
>
> Bertrand and I have heard back from the GNU maintainers team. As of
> yesterday, they have offere
Hi folks,
Bertrand and I have heard back from the GNU maintainers team. As of
yesterday, they have offered me the maintainer role for groff and I have
communicated my acceptance.
I haven't received notification of any changed "permission bits" or
anything else, and don't expect to immediately, s
10 matches
Mail list logo
