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: checking mainlanguage setup
Date: Wed, 01 Jun 2011 10:22:51 +0200	[thread overview]
Message-ID: <4DE5F6DB.6040305@wxs.nl> (raw)
In-Reply-To: <4DE5F4FD.6040907@wxs.nl>

On 1-6-2011 10:14, Hans Hagen wrote:

> [[ ]] vs " " is a lua thing ... but when you pass things from within
> tex, expansions happens the same in both; you can try
>
> context("\detokenize{...}")

Sorry, that should have been

\ctxlua{"\detokenize{...}"}

which takes care of things at the tex end. When at the lua end, you need 
to use \\ (or indeed [[with regular \'s]].

Anyhow, it does not hurt to always to take good look at \'s because 
commands might end up in cycles (or for instance can end up in auxiliary 
files). This is why many commands are defined using \unexpanded.  Even 
if you pass something using context at the lua end. You can see what 
gets passed to tex using:

\enabletrackers[context.trace]

What you see there should look like regular context.

(btw, context.setvalue{"Lang","English") also works well and has no 
backslashes)

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:[~2011-06-01  8:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1306836001.18520.ntg-context@ntg.nl>
2011-05-31 10:45 ` Jeong Dalyoung
2011-05-31 14:33   ` Procházka Lukáš Ing. - Pontex s. r. o.
2011-06-01  8:14     ` Hans Hagen
2011-06-01  8:22       ` Hans Hagen [this message]
     [not found] <mailman.1275.1306911210.4231.ntg-context@ntg.nl>
2011-06-01  7:45 ` Jeong Dalyoung
2011-06-01 12:54   ` Wolfgang Schuster
     [not found] <mailman.1266.1306859874.4231.ntg-context@ntg.nl>
2011-06-01  1:16 ` Jeong Dalyoung
2011-06-01  1:32   ` Aditya Mahajan
     [not found] <mailman.1.1306576802.24208.ntg-context@ntg.nl>
2011-05-28 12:26 ` Jeong Dalyoung
2011-05-28 13:45   ` Hans Hagen
2011-05-31  6:48   ` Procházka Lukáš Ing. - Pontex s. r. o.
     [not found] <mailman.1220.1306501767.4231.ntg-context@ntg.nl>
2011-05-28  2:41 ` Jeong Dalyoung
2011-05-28  3:04   ` Aditya Mahajan
2011-05-27  9:49 Jeong Dalyoung
2011-05-27 10:11 ` Pontus Lurcock
2011-05-27 10:22 ` Marco
2011-05-27 10:41 ` Peter Münster

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=4DE5F6DB.6040305@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).