public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Lemaire <contact@martinlemaire.fr>
To: Dave Kemper <saint.snit@gmail.com>
Cc: Groff <groff@gnu.org>, linux-man@vger.kernel.org
Subject: Re: Paragraphs formatted differently depending on previous ones
Date: Fri, 2 May 2025 20:46:47 +0200	[thread overview]
Message-ID: <aBUTF6SphOspqAKT@starship> (raw)
In-Reply-To: <CACRhBXOPUdngLptS-oGqkeCZ=R=as8Fhkf6jSuznC+TMbbQx0w@mail.gmail.com>

Although Gutenberg had a major impact on printing in the 15th century,
there are traces in Asia of xylogprahy[1] as early as the 6th century. 
It is argued that western educations give the guy too much credit. 
His contribution to the craft was more about crafting inks allowing the
printing on both side of the sheet.
Earlier than that – and closer to the practice that is printing
characters in a monospaced grid – there has been stoichedon[2], a style
of stone engraving where letters are aligned vertically and
horizontally. Words seem to be separated by a spaceless sign between
them. I assume this absence of spaces produced the most uniform and
pleasing grayness.
To my knowledge, we have to wait for the year 2000 for someone called
rs1n to produce a perfectly justified monospaced document[3] without adding or
removing between-word space, writing and typesetting at the same time.

How does *roff monospace justification algorithm relate to its sibling
justifying proportional letters ?
Are the two vaguely related or it's another approach ?

Martin


[1] Printed copy of the Vajracchedikaprajnaparamitasutra, 868 https://idp.bl.uk/collection/51FDAEAFB4A24E2E9981692A98130BC8/

[2] Stoichedon https://en.wikipedia.org/wiki/Stoichedon

[3] Super Metroid – FAQ/Speed Guide, rs1n, 2000 https://gamefaqs.gamespot.com/snes/588741-super-metroid/faqs/10114
mirrored here https://www.martinlemaire.fr/metroid.html


Le Fri, May 02, 2025 at 12:42:30PM -0500, Dave Kemper a écrit :
> On Fri, May 2, 2025 at 8:07 AM Martin Lemaire <contact@martinlemaire.fr> wrote:
> > Off-topic to Alejandro's initial question but related to the subject of
> > justifying text set in monospace, do we owe this typographic gesture to
> > the early *roff formaters or was it already a thing in previous
> > publication tool, either software or hardware ?
> 
> Branden addressed the conceptual basis for such adjustment.  The
> origin of the specific algorithm used for monospace fonts was revealed
> by its inventor in a post a few years ago:
> 
> http://lists.gnu.org/r/groff/2018-06/msg00044.html
> 
> Other than starting with a different adjustment "direction," this
> algorithm remains unchanged in groff today.
> 

  reply	other threads:[~2025-05-02 23:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-02 10:56 Paragraphs formatted differently depending on previous ones Alejandro Colomar
2025-05-02 12:01 ` G. Branden Robinson
2025-05-02 12:26   ` grof --run Alejandro Colomar
2025-05-02 14:19     ` G. Branden Robinson
2025-05-02 14:59       ` Alejandro Colomar
2025-05-03  0:49         ` G. Branden Robinson
2025-05-03  7:25           ` Alejandro Colomar
2025-05-05 10:50           ` Colin Watson
2025-05-05 15:41             ` Ingo Schwarze
2025-05-07 18:10               ` G. Branden Robinson
2025-05-02 12:42   ` Paragraphs formatted differently depending on previous ones Alejandro Colomar
2025-05-02 14:29     ` G. Branden Robinson
2025-05-02 15:30       ` Alejandro Colomar
2025-05-02 13:06   ` Martin Lemaire
2025-05-02 14:51     ` G. Branden Robinson
2025-05-02 15:34       ` Alejandro Colomar
2025-05-03  1:30         ` G. Branden Robinson
2025-05-02 17:42     ` Dave Kemper
2025-05-02 18:46       ` Martin Lemaire [this message]
2025-05-03  0:14         ` G. Branden Robinson
2025-05-05 16:00           ` Joey Hess
2025-06-02  6:49             ` on "bricktext" (was: Paragraphs formatted differently depending on previous ones) G. Branden Robinson
2025-06-02  7:16               ` on "bricktext" James Cloos

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=aBUTF6SphOspqAKT@starship \
    --to=contact@martinlemaire.fr \
    --cc=groff@gnu.org \
    --cc=linux-man@vger.kernel.org \
    --cc=saint.snit@gmail.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