Hi,
the JSON parser handles backslash escapes improperly. Example:
local data = [[ { "escapes" : "(\")(\\)(\b)(\f)(\n)(\r)(\t)",
"invalid" : "\'\v" } ]]
local stuff = utilities.json.tolua (data)
inspect(stuff)
Currently it chokes on double quotes and treats the
Am 06.07.2013 um 12:33 schrieb Sanjoy Mahajan :
> Wolfgang,
>
> Thank you for all your solutions!
>
>> 2. You can omit the \usetypescript line.
>
> Good to know. Does the "palatino" keyword in \setupbodyfont
> automatically do that now (in Mark IV)?
>
> Should I wikify that bit of informatio
Hi,
in the following example the markings are wrong.
\setupheadertexts
[{\getmarking[section][both]}]
[{\getmarking[section][first]\space\emdash\space
\getmarking[section][last]}]
\starttext
\def\aa#1{\section{#1}\input knuth}
\processcommacommand [A, B, C, D, E] \aa
\stoptext
I expe
Hi Wolfgang,
I already tried using \setuphead[…][prefix=+], this are my definitions:
\setuphead [chapter][command=\ChapterCmd, style={\ss\bfc}, page=right,
number=yes, frame=off, placehead=yes, align=left, before={},
after={\blank[3*line]}, header=nomarking, prefix=+]
\setuphead [section][style
Metapost now has double precision arithmetic, so one no longer needs to
use the string arithmetic macros. However, it may be necessary to use
scantokens as in
clearxy;
z = (scantokens v1, scantokens v2);
augment.p(x,0);
augment.p(x,y);
x := x + 0.4 ;
augment.p(x,y);
augment.p(x,0);
Alan
On Sat