ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: language specifics
Date: Fri, 07 May 2010 11:19:04 +0200	[thread overview]
Message-ID: <4BE3DB08.2040000@wxs.nl> (raw)
In-Reply-To: <20100507072532.GB3537@gaston.couberia.bzh>

On 7-5-2010 9:25, Peter Münster wrote:
> On Thu, May 06 2010, Hans Hagen wrote:
>
>> in mkiv we don't have (want) language specifics ... why do yoi need them?
>
> Hello Hans,
>
> What is now the right mechanism, to trigger some setting when a specific
> language is activated and cancel this same setting, when this language is
> deactivated?
>
> Example: when entering French language, I want to execute
> "\setcharacterspacing[frenchpunctuation]" and when leaving French I want to
> execute "\setcharacterspacing[reset]".
>
> (today the file
> http://dl.contextgarden.net/modules/t-french/tex/context/third/french/t-french.tex
> is broken, because I don't know how to do it right... :(

you can then probably just enable it as i cannot imagine a document 
which uses mixed typographical habits that still looks right

anyway, there will be some mechanism but probably more at the level of 
the features itself (i.e. as part of setcharacterspacing) as there have 
to be ways to turn on/off specific language bound features. The mkii 
language specifics were mostly meant for encoding issues and those 
trigger points have disappeared as encodings are gone now.

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | 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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2010-05-07  9:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-03 18:43 mistake in lang-cjk.mkiv Tomáš Pustelník
2010-05-06 20:16 ` Hans Hagen
2010-05-07  7:25   ` language specifics (was: Re: mistake in lang-cjk.mkiv) Peter Münster
2010-05-07  9:19     ` Hans Hagen [this message]
2010-05-09  8:30   ` mistake in lang-cjk.mkiv Tomáš Pustelník
2010-05-09  8:47   ` Wolfgang Schuster
2010-05-09 10:02     ` Hans Hagen
  -- strict thread matches above, loose matches on Subject: below --
1999-11-16 19:26 language specifics Berend de Boer
1999-11-16 19:24 Berend de Boer
1999-11-16 18:18 Karsten Tinnefeld
1999-11-16 20:20 ` Tobias Burnus
1999-11-17  9:10   ` Hans Hagen
1999-11-16 17:20 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=4BE3DB08.2040000@wxs.nl \
    --to=pragma@wxs.nl \
    --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).