From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Ctx & Lua: determination of the language being used
Date: Thu, 25 Nov 2010 14:22:18 +0100 [thread overview]
Message-ID: <4CEE630A.1060407@elvenkind.com> (raw)
In-Reply-To: <op.vmp9tqdqtpjj8f@lpr>
On 11/25/2010 02:16 PM, Procházka Lukáš Ing. - Pontex s. r. o. wrote:
>
> So does it mean that "\<char>" (in the beginning of a string) in Lua for
> ConTeXt is a "hack" which expands a (Con)TeX(t) internal value (in the
> case that <char> is not a valid escape char)?
No, nothing as complicated as that: \currentmainlanguage is an
expandable macro, so it simply expands to its actual content: cs
This also means that my proposed solution will not work if you put
it in a separate lua file: you have to convert it to a lua function
in that case that takes \currentmainlanguage as an argument.
Best wishes,
Taco
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-11-25 13:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 11:49 Procházka Lukáš Ing. - Pontex s. r. o.
2010-11-25 12:13 ` Wolfgang Schuster
2010-11-25 12:31 ` Taco Hoekwater
2010-11-25 13:16 ` Procházka Lukáš Ing. - Pontex s. r. o.
2010-11-25 13:22 ` Taco Hoekwater [this message]
2010-11-25 13:43 ` Procházka Lukáš Ing. - Pontex s. r. o.
2010-11-25 15:13 ` Taco Hoekwater
2010-11-25 15:57 ` Hans Hagen
2010-11-26 9:22 ` Taco Hoekwater
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=4CEE630A.1060407@elvenkind.com \
--to=taco@elvenkind.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).