From: luigi scarso <luigi.scarso@gmail.com>
To: Mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: French typography is back
Date: Fri, 22 May 2009 18:40:54 +0200 [thread overview]
Message-ID: <fe8d59da0905220940t3aef1defwd4cf48c482bc3f1f@mail.gmail.com> (raw)
In-Reply-To: <20090522155157.GF30326@phare.normalesup.org>
[-- Attachment #1.1: Type: text/plain, Size: 1080 bytes --]
On Fri, May 22, 2009 at 5:51 PM, Arthur Reutenauer <
arthur.reutenauer@normalesup.org> wrote:
> > but instead of arbitrary adding a 0.25em
> > before and 1em after the punctuation mark you should use the real nnbsp
> > (U+202F) before and real normal space (U+0020) after.
>
> I don't think so. Space characters don't mix very well with TeX glue
> and should best be avoided, generally speaking. In particular, all
> inter-word spaces that are input in the TeX source as one or more of
> U+0020 are simply ignored, and replaced by normal inter-word glue, with
> its appropriate stretchability and shrinkability. This has always been
> the case in TeX and is not going to change. All other types of Unicode
> spaces should really, in my opinion, be processed in the same way, while
> respecting their additional properties in the case of non-breakable
> spaces, for instance.
>
Maybe one can use
something like this
\defineremapper[filterItem]
\remapcharacter[filterItem][`•]{\item}
for "spaces" too
--
luigi
[-- Attachment #1.2: Type: text/html, Size: 1493 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-05-22 16:40 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
2009-05-22 16:40 ` luigi scarso [this message]
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=fe8d59da0905220940t3aef1defwd4cf48c482bc3f1f@mail.gmail.com \
--to=luigi.scarso@gmail.com \
--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).