From: Thomas Savary <compo85@correctionpro.fr>
To: ntg-context@ntg.nl
Subject: Re: characterspacing not always working in LMTX
Date: Wed, 15 Jan 2020 16:10:00 +0100 [thread overview]
Message-ID: <4890898.pTjBHbTJas@debian> (raw)
In-Reply-To: <20200115120200.zudwxt2niqn23aim@phare.normalesup.org>
[-- Attachment #1.1: Type: text/plain, Size: 2105 bytes --]
Arthur :
> I think it happened at about the same time for English. Before that
> it was pretty universal. See
> https://archive.org/details/worksbenjaminfr06spargoog/page/n12 for just one
> example.
>
> (The thin space in that example is really thin! -- but it’s definitely
> there)
Exactly. And this is precisely the thin space still required in French
publications. The main disagreement among French typographs (about twenty years
ago, at least) was about the fixed vs relative width of this thin space : put
in TeX’s terms, should it be proportional to the glue or to the font ?
I think I’d better write an article about this, with quotes and visual
examples.
Greetings
Thomas Savary
1 le Grand-Plessis
F-85340 L’Île-d’Olonne
Tél. 06 22 82 61 34
https://compo85.fr/
mercredi 15 janvier 2020, à 13:02:00 CET, Arthur Reutenauer a écrit :
> On Wed, Jan 15, 2020 at 11:29:35AM +0100, Taco Hoekwater wrote:
> > Dutch typesetting had some rules for thin spaces in a transition period
> > from full spaces (early) to no spaces (modern).
> >
> > Much of this change happened in the (late) 19th century, so I guess it had
> > more to do with linotype/monotype than with modern digitisation.
> I think it happened at about the same time for English. Before that
> it was pretty universal. See
> https://archive.org/details/worksbenjaminfr06spargoog/page/n12 for just one
> example.
>
> (The thin space in that example is really thin! -- but it’s definitely
> there)
>
> Best,
>
> Arthur
> ____________________________________________________________________________
> _______ If your question is of interest to others as well, please add an
> entry to the Wiki!
>
> maillist : ntg-context@ntg.nl /
> http://www.ntg.nl/mailman/listinfo/ntg-context webpage :
> http://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
> ____________________________________________________________________________
> _______
[-- Attachment #1.2: Type: text/html, Size: 9982 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-01-15 15:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 21:58 Joseph
2020-01-14 22:24 ` Wolfgang Schuster
2020-01-14 22:25 ` Thomas Savary
2020-01-15 9:15 ` Hans Hagen
2020-01-15 10:29 ` Taco Hoekwater
2020-01-15 12:02 ` Arthur Reutenauer
2020-01-15 15:10 ` Thomas Savary [this message]
2020-01-15 15:16 ` Henning Hraban Ramm
2020-01-17 8:41 ` Thomas Savary
2020-01-17 9:01 ` Henning Hraban Ramm
2020-01-15 14:59 ` Thomas Savary
2020-01-15 9:16 ` Hans Hagen
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=4890898.pTjBHbTJas@debian \
--to=compo85@correctionpro.fr \
--cc=ntg-context@ntg.nl \
/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).