ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jeong Dalyoung <haksan@me.com>
To: ntg-context@ntg.nl
Subject: Re: checking mainlanguage setup
Date: Wed, 01 Jun 2011 10:16:32 +0900	[thread overview]
Message-ID: <5C1C3C5A-E630-4900-8B0B-7DB91C35EDA1@me.com> (raw)
In-Reply-To: <mailman.1266.1306859874.4231.ntg-context@ntg.nl>

Dear Lukas,

Thank you for the explanation.

> 
> I guessed that your original
> 
> [[\\def\\lang{English}]]

No errors message, but it's not working as the way as  I want. It just print "def langEnglish".

> 
> [[\def\lang{English}]]
> 

This cause the error message and halt the compiling.

Best regards,

Dalyoung

metapost > loading 'metafun.mp' (experimental metapost version two)
! Undefined control sequence.
system > tex > error on line 84 in file test-font.tex: Undefined control sequence ...
74
75
76 \startluacode
77 if languages.current() == "kr" then
78 -- context.setvalue("lang","한글")
79 context([[\def\lang{한글}]])
80 else
81 -- context.setvalue("lang","English")
82 context("\\def\\lang{English}")
83 end
84 >> \stopluacode
85
86 currentlanguage: \lang
87
88 \section{one.two}
89
90 \doifelse\currentmainlanguage{en}{\def\lang{English}}{\def\lang{영어가 아님}}\par
91
92 currentlanguage: \lang
93 %currentmainlanguage:
94 %\doifelse\currentmainlanguage{kr}{Korean}{Not Korean}\par
\lang #1->\edef \biblanguage
{#1}\ifcsname \??pb \s!language #1\endcsname \l...
<argument> ...,"한글")
context([[\def \lang {
한글}]])
else
-- conte...
\dodostartluacode ...and \directlua \zerocount {#1
}}
l.84 \stopluacode
? 
___________________________________________________________________________________
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
___________________________________________________________________________________

       reply	other threads:[~2011-06-01  1:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1266.1306859874.4231.ntg-context@ntg.nl>
2011-06-01  1:16 ` Jeong Dalyoung [this message]
2011-06-01  1:32   ` Aditya Mahajan
     [not found] <mailman.1275.1306911210.4231.ntg-context@ntg.nl>
2011-06-01  7:45 ` Jeong Dalyoung
2011-06-01 12:54   ` Wolfgang Schuster
     [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=5C1C3C5A-E630-4900-8B0B-7DB91C35EDA1@me.com \
    --to=haksan@me.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).