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
___________________________________________________________________________________
