From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: checking mainlanguage setup
Date: Wed, 1 Jun 2011 14:54:43 +0200 [thread overview]
Message-ID: <4B25E72F-6649-4200-8708-0821BE063516@googlemail.com> (raw)
In-Reply-To: <03D02E6E-2F85-442E-ABE8-FB63D8BC1614@me.com>
Am 01.06.2011 um 09:45 schrieb Jeong Dalyoung:
> I summerize it as a test file. The first 5 methods are working well, but the last one using \noexpand cause the error.
What exactly do you plan to do with the language check, for simple texts your method is overkill and labeltexts are better suited, even a command which prints a text can be written in TeX without problems:
\def\LangOne
{\doifelse{\currentmainlanguage}{en}
{English 1}
{\doifelse{\currentmainlanguage}{nl}
{Dutch 1}
{Unknown 1}}}
\def\LangTwo
{\processaction
[\currentmainlanguage]
[ en=>English 2,
nl=>Dutch 2,
unknown=>Unknown 2]}
\setuplabeltext[en][langthree=English 3]
\setuplabeltext[nl][langthree=Dutch 3]
\setuplabeltext [langthree=Unknown 3]
\starttext
\LangOne:\LangTwo:\labeltext{langthree}:\translate[en=English 4,nl=Dutch 4]
\mainlanguage[nl]
\LangOne:\LangTwo:\labeltext{langthree}:\translate[en=English 4,nl=Dutch 4]
\mainlanguage[fr]
\LangOne:\LangTwo:\labeltext{langthree}:\translate[en=English 4,nl=Dutch 4]
\stoptext
Wolfgang
___________________________________________________________________________________
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:[~2011-06-01 12:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1275.1306911210.4231.ntg-context@ntg.nl>
2011-06-01 7:45 ` Jeong Dalyoung
2011-06-01 12:54 ` Wolfgang Schuster [this message]
[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.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
[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=4B25E72F-6649-4200-8708-0821BE063516@googlemail.com \
--to=schuster.wolfgang@googlemail.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).