From: "Robert-André Mauchin" <zebob.m@pengzone.org>
To: ntg-context@ntg.nl
Subject: French typography is back
Date: Thu, 21 May 2009 14:28:59 +0200 [thread overview]
Message-ID: <4A15490B.3050607@pengzone.org> (raw)
Hi again,
I have been reading all threads about the French typography in this
mailing list, however the current solution is alas far for perfect. The
command \setcharacterspacing[frenchpunctuation] was a good idea, but it
only deals with spacing. French typography rules not only tells us that
there should be a narrow, or a normal space before some punctuation
marks like :, ;, , !, ?, « or », but also that theses spaces must be non
breakable otherwise line breaking could occur just before a punctuation
mark (and this is very bad).
Take a look at the following example:
\section{Production locale indigène ou production romaine importée?}
With the current frenchpunctuation command, we got:
Production locale indigène ou production romaine importée
?
We should obtain:
Production locale indigène ou production romaine
importée ?
Of course we could achieve this manually by adding the correct NNBSP
like this:
\section{Production locale indigène ou production romaine importée\,?}
But I believe the whole point of TeX is to let the engine make all the
typographic stuff.
The best would be to get rid off \setcharacterspacing[frenchpunctuation]
and adapt the frenchb Babel module from Daniel Flipo (source and
explanation here http://daniel.flipo.free.fr/frenchb/ ), as a module
(t-french modification), or when loading the language, but I really
don't know how hard it would be since it handles a lot more than just
punctuation marks.
Regards,
Bob.
___________________________________________________________________________________
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 reply other threads:[~2009-05-21 12:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 12:28 Robert-André Mauchin [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2009-05-20 6:25 MkIV italic correction? Corsair
2009-05-21 9:55 ` Hans Hagen
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
2009-05-22 16:40 ` luigi scarso
2009-05-22 17:06 ` 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=4A15490B.3050607@pengzone.org \
--to=zebob.m@pengzone.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).