On 7/9/2019 10:37 AM, Taco Hoekwater wrote:
On 8 Jul 2019, at 17:18, mf wrote:
Hello list,
i've played a bit with interfaces.definecommand, that lets you define TeX macros from lua
(see the "ConTeXt Lua Documents", 7.3 User interfacing).
I found that the commands defined by
On 7/8/2019 5:18 PM, mf wrote:
Hello list,
i've played a bit with interfaces.definecommand, that lets you define
TeX macros from lua (see the "ConTeXt Lua Documents", 7.3 User
interfacing).
I found that the commands defined by interfaces.definecommand fail when
you pass string arguments
> On 8 Jul 2019, at 17:18, mf wrote:
>
> Hello list,
> i've played a bit with interfaces.definecommand, that lets you define TeX
> macros from lua (see the "ConTeXt Lua Documents", 7.3 User interfacing).
>
> I found that the commands defined by interfaces.definecommand fail when you
> pass
Thank you. I still don't really understand why can't you have a
"presentational" yaml file and a "content" yaml file (I do it like that...
I have a "variables.yaml" file for content and a "settings.yaml" file for
presentational stuff, and use a "template.context" file with all my mapped
variables
That's another intriguing approach, Andrés, thank you.
The approach faces some hurdles. First, the template file (main.tex) is
written in ConTeXt, so it never sees the YAML variables, nor can it be used
to interpret pandoc's conditional expressions. Second, moving the
\completecontent macro out
The following probably well known minimal example
\starttext
\startregister[index][key1]{an entry}\input knuth\stopregister[index][key1]
\placeindex
\stoptext
produces the index entry "an entry 1--1", where the page range should be
just a single page.
A question (and then two
I'm working on a book that uses tables and figures, but the editors want to
use to diffferent captions for each figure: one as usual, with the float
description and number, and another one with a "Source" for said float.
Something like:
-
|
Dear List,
Warning: The following may be a bug or feature or just my
misunderstanding! It seems that parentheses cause trouble in
references. MNWE:
\starttext
\section[sec:one(two)]{One}
As you see in sec.~\in[sec:one(two)],
\stoptext
The "in sec.~\in[sec:one(two)]" typesets as "in
