From: "Procházka Lukáš Ing. - Pontex s. r. o." <LPr@pontex.cz>
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:16:28 +0100 [thread overview]
Message-ID: <op.vmp9tqdqtpjj8f@lpr> (raw)
In-Reply-To: <4CEE5728.4010706@elvenkind.com>
... Thanks to both. So -
On Thu, 25 Nov 2010 13:31:36 +0100, Taco Hoekwater <taco@elvenkind.com> wrote:
> On 11/25/2010 01:13 PM, Wolfgang Schuster wrote:
>>
>> Am 25.11.2010 um 12:49 schrieb Procházka Lukáš Ing. - Pontex s. r. o.:
>>
>>> Hello,
>>>
>>> how to determine the current language being used in Ctx source via Lua? I mean soumething like:
>>>
>>> ---
>>> \mainlanguage[cz]
>>>
>>> \starttext
>>> AAA
>>>
>>> \startluacode
>>> if context.mainlanguage == "cz" then -- Do something specific
>>> context("Ahoj!")
>>> elseif context.mainlanguage == "en" then -- Do something specific
>>> context("Hello!")
>>> else
>>> end
>>> \stopluacode
>>> \stoptext
>>> ---
>>>
>>> So is there something like 'context.mainlanguage' or 'context.mainlanguage()' or 'tex.mainlanguage' or ...?
>>
>> \mainlanguage[...] -> \currentmainlanguage
>> \language[...] -> \currentlanguage
>
> For the benefit of the mailing list archive, this means you
> can write in lua:
>
> if "\currentmainlanguage"=="cz" then
>
> Except that that will not work because 'cz' is just an alias for 'cs',
> so you should test for that instead:
>
>
> if "\currentmainlanguage"=="cs" then
> context("Ahoj!")
> elseif "\currentmainlanguage"=="en" then
> context("Hello!")
>
> Best wishes,
> Taco
- In standalone Lua, the "\c" would be read (translated) as "c", as "\c" is not a valid escape sequence. See the test:
---
Microsoft Windows XP [Verze 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Lukas\ConTeXt\Samples\LuaTest>lua
Lua 5.1.4 Copyright (C) 1994-2008 Lua.org, PUC-Rio
> a="\currentmainlanguage"
> =a
currentmainlanguage
> =("\currentmainlanguage"=="currentmainlanguage")
true -- SO "\c" BECOMES "c"
---
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)?
- If so, how to get an internal (Con)TeX(t) value which begins with a valid escape <char>, e.g. 't', so e.g. "\textwidth"? ("\t" should become <tab> in this case, or am I wrong?)
(Where to read about? I've been searching in luatexref-t.pdf...)
Lukas
___________________________________________________________________________________
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:16 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. [this message]
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
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=op.vmp9tqdqtpjj8f@lpr \
--to=lpr@pontex.cz \
--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).