From: Rik Kabel <context@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: Re: starttexdefinition error in standalone, works in TL2013
Date: Sat, 01 Mar 2014 12:01:36 -0500 [thread overview]
Message-ID: <53121270.1090702@rik.users.panix.com> (raw)
In-Reply-To: <4FDA647E-AA4E-4619-88EE-65DE254BA093@gmail.com>
On 2014-03-01 07:32, Wolfgang Schuster wrote:
> Am 27.02.2014 um 05:08 schrieb Rik Kabel <context@rik.users.panix.com>:
{useful information on TL2013 and starttexdefinition skipped}
> BTW: It’s better to follow contexts rules and use start/stop for environments, this way you can make use of the buffer mechanism to store text.
>
> \unexpanded\def\startTranslation
> {\begingroup
> \dosingleempty\dostartTranslation}
>
> \def\dostartTranslation[#1]%
> {\iffirstargument
> \getrawparameters[Translation][setups=,language=en,#1]%
> \fi
> \grabbufferdata[Translation][startTranslation][stopTranslation]}
>
> \def\stopTranslation
> {\language[\Translationlanguage]%
> \Translationsetups
> (\,\getbufferdata[Translation]\removeunwantedspaces\,)%
> \endgroup}
>
> \starttext
>
> \startTranslation[language=nl]
> It betrays a slow-witted mentality to pursue the streams, but not to see the sources of things.
> \stopTranslation
>
> \stoptext
>
Thank you for the excellent example. The only problem I see is that it
fails if no optional argument is present (in which case the keyval
settings \TranslationXXX never get defined). This is easily remedied by
removing the \iffirstargument and \fi wrapping the \getrawparameters.
--
Rik
___________________________________________________________________________________
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:[~2014-03-01 17:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 4:08 Rik Kabel
2014-02-27 15:13 ` Rik Kabel
2014-03-01 12:32 ` Wolfgang Schuster
2014-03-01 17:01 ` Rik Kabel [this message]
2014-03-12 19:49 ` Movable code, was " Rik
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=53121270.1090702@rik.users.panix.com \
--to=context@rik.users.panix.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).