From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Ctx & Lua: determination of the language being used
Date: Thu, 25 Nov 2010 16:57:52 +0100 [thread overview]
Message-ID: <4CEE8780.9060505@wxs.nl> (raw)
In-Reply-To: <4CEE7D30.4090405@elvenkind.com>
On 25-11-2010 4:13, Taco Hoekwater wrote:
> On 11/25/2010 02:43 PM, Procházka Lukáš Ing. - Pontex s. r. o. wrote:
>> ... And using this in a separate file is also what I'd need. So do I
>> have to do something like:
>
> Something like that, yes. But it depends a little on what you
> want to do: because \currentmainlanguage expands, you will
> get the value that is active during the first scan of the
> lua code block, which may not be what you want, but it is hard
> to judge without the actual use case.
>
>> (Suggestion: Wouldn't be nice to have function(s) or variable(s) like
>> e.g. 'context.environment["currentmainlanguage"]' or something like
>> this?)
>
> Yes, agreed, something like that would be useful. The same applies to
> some other things, like color and active modes. Some of these are
> probably there already, but it would be nice if they were documented.
it's not so hard to interface that but we need to pick up the current value
\ctxlua{tex.sprint(languages.numbers[1])}
however, tex does not privide access to the current language so i'd have
to introduce an extra counter at the tex end
anyhow, for the moment you can use
languages.numbers[tex.count.mainlanguagenumber]
which probably gives you wat you want: en
-----------------------------------------------------------------
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-11-25 15:57 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
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 [this message]
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=4CEE8780.9060505@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
--cc=taco@elvenkind.com \
/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).