From: Arthur Reutenauer <arthur.reutenauer@normalesup.org>
To: Mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: French typography is back
Date: Sat, 23 May 2009 00:58:53 +0200 [thread overview]
Message-ID: <20090522225853.GB15587@phare.normalesup.org> (raw)
In-Reply-To: <4A16D4F9.1070405@pengzone.org>
> Not knowing the internals, that's what I tried to say with adding a space
> after instead of 1em, i.e. "calculated by the engine". If w an em is added
> after, it is not stretchable and shrinkable, right?
Right. But no particular space is added after '?' or '!' in French
punctuation mode, TeX sets the standard inter-word glue, as it should.
The only intervention by ConTeXt is the addition of the unbreakable
space before those marks (and, obviously, after '«').
> Thank you so much for the detailed technical explanation! So, AFAIK, I
> believe that the space before should be equivalent to thinspace.
You'd need to take this up with Olivier Guéry, who suggested the 1/4
em value in the first place (refer to his interventions from last Fall,
e.g., http://www.ntg.nl/pipermail/ntg-context/2008/034845.html). He
wrote up a small proposal on the wiki page for French Punctuation
(http://wiki.contextgarden.net/French_Punctuation).
> Thanks, I'll see that. Maybe I could write some detailled specs in the wiki.
Yes, please do so by extending the aforementioned page if needed.
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-05-22 22:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 6:25 MkIV italic correction? Corsair
2009-05-20 7:21 ` Yue Wang
2009-05-20 7:37 ` Corsair
2009-05-21 9:55 ` Hans Hagen
2009-05-21 11:55 ` Corsair
2009-05-21 11:59 ` Taco Hoekwater
2009-05-21 13:36 ` Corsair
2009-05-22 9:15 ` Taco Hoekwater
2009-05-21 13:20 ` Khaled Hosny
2009-05-22 9:25 ` Taco Hoekwater
2009-05-22 10:48 ` Hans Hagen
2009-05-22 11:23 ` Taco Hoekwater
2009-05-22 12:44 ` French typography is back Robert-André Mauchin
2009-05-22 15:51 ` Arthur Reutenauer
2009-05-22 16:38 ` Robert-André Mauchin
2009-05-22 22:58 ` Arthur Reutenauer [this message]
2009-05-22 16:40 ` luigi scarso
2009-05-22 17:06 ` Hans Hagen
2009-05-27 4:34 ` MkIV italic correction? Dohyun Kim
2009-05-27 8:11 ` Hans Hagen
2009-06-01 15:15 ` Khaled Hosny
2009-06-01 20:19 ` Hans Hagen
2009-05-21 12:28 French typography is back Robert-André Mauchin
2009-05-21 14:39 ` Peter Münster
2009-05-21 15:24 ` Arthur Reutenauer
2009-05-21 16:26 ` Hans Hagen
2009-05-21 16:29 ` Hans Hagen
2009-05-21 17:33 ` Wolfgang Schuster
[not found] <mailman.0.1242930320.17979.ntg-context@ntg.nl>
2009-05-21 18:32 ` Robert-André Mauchin
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=20090522225853.GB15587@phare.normalesup.org \
--to=arthur.reutenauer@normalesup.org \
--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).