From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Thomas Savary <compo85@correctionpro.fr>
Subject: Re: characterspacing not always working in LMTX
Date: Wed, 15 Jan 2020 10:15:45 +0100 [thread overview]
Message-ID: <c13e4862-3e5f-4fd2-3e4c-d48e98bc4317@xs4all.nl> (raw)
In-Reply-To: <2199238.F81R2dj7GW@debian>
On 1/14/2020 11:25 PM, Thomas Savary wrote:
> Hello, dear list !
>
> Joseph :
>
> > With LMTX (MkIV is fine) characterspacing (I use frenchpunctuation)
> is not
>
> > applied sometimes (ie no spacing before colon for example) in some
> parts of
>
> Character-spacing for French punctuation marks is incorrect in MkIV
> anyway : the “thin” spaces are much too wide. I will write more about it
> when I have more time. I have just begun to lean ConTeXt. For the time
> being, I don’t use its automatic spacing for French punctuation, but
> real Unicode spaces such as U+202F (non breakable thin space, about
> 0.125 em, depending on the font).
keep in mind that we use values that were specified by french users ...
however, as usual with language specific features, these can differ per
user
anyway, it's configureable
> By the way, thin spaces are not specific to French typography,
> historically speaking, since they seem to have been used everywhere in
> Europe for centuries — at least in England, Belgium, Germany and Italy
> (probably in the Netherlands too, I will check). In France and sometimes
> in England, thin spaces were often used before commas as well. I wonder
> why most countries stopped using them. Out of laziness ? :-)
never seen them in dutch ... i think not so much lazyness but side
effect of going digital ... i bet that these spaces were also (ab)used
to justify lines (cheat a bit) i.e. manual injection of some lead blob
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 9:15 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 [this message]
2020-01-15 10:29 ` Taco Hoekwater
2020-01-15 12:02 ` Arthur Reutenauer
2020-01-15 15:10 ` Thomas Savary
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=c13e4862-3e5f-4fd2-3e4c-d48e98bc4317@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=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).