From: Rik Kabel <context@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: starttexdefinition error in standalone, works in TL2013
Date: Wed, 26 Feb 2014 23:08:56 -0500 [thread overview]
Message-ID: <530EBA58.3020703@rik.users.panix.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1946 bytes --]
The following code processes cleanly under TL2013 and fails with
ConTeXt ver: 2014.02.14 17:07 MKIV beta fmt: 2014.2.16 int:
english/english. I suspect a regression, but I am also open to being
told that I am doing things incorrectly.
I also notice that it fails (even under TL2013) if a space is inserted
after [#SETUP] in the doTrans intro. I thought that spaces should be
allowed in \starttexdefinition -- is this only in the body and not the
parameter description?
% macros=mkvi
\showframe
\let\EndTranslation\relax
\starttexdefinition Trans
\dosingleempty\doTrans
\stoptexdefinition
% The following should work, but fails with current beta
\starttexdefinition doTrans [#SETUP]#TRANSLATION\EndTranslation
\language[en]
\doifsomething{#1}{\getparameters[TR][setup=,#SETUP]\TRsetup}
\noindentation\blank[halfline]
(\,\ignorespaces#TRANSLATION\removeunwantedspaces\,)
\stoptexdefinition
\starttexdefinition Translation
\dosingleempty\doTranslation
\stoptexdefinition
% This version works with both Texlive and current standalone beta
\def\doTranslation[#SETUP]#TRANSLATION\EndTranslation%
{\language[en]%
\doifsomething{#SETUP}%
{\getparameters[TR][setup=,#SETUP]\TRsetup}%
\noindentation\blank[halfline]%
(\,\ignorespaces#TRANSLATION\removeunwantedspaces\,)%
}
\starttext
Translation using \tex{def}{\tex{doTranslation}} works both with
TL2013 and current beta.
\Translation[language=en]
It betrays a slow-witted mentality to pursue the streams, but not
to see the sources of things.
\EndTranslation
\blank
Translation using \tex{starttexdef doTrans} fails with current beta.
\Trans[language=en]
It betrays a slow-witted mentality to pursue the streams, but not
to see the sources of things.
\EndTranslation
\stoptext
--
Rik Kabel
[-- Attachment #1.2: Type: text/html, Size: 3035 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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 reply other threads:[~2014-02-27 4:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 4:08 Rik Kabel [this message]
2014-02-27 15:13 ` Rik Kabel
2014-03-01 12:32 ` Wolfgang Schuster
2014-03-01 17:01 ` Rik Kabel
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=530EBA58.3020703@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).