Dear Thomas,
Thank you for your reply.
XeTeX+ ConTeXt is working after adding a command as you said.
(customize-variaable)
But Lua + ConTeXt is not working.
If I do mtxrun --script context ..., then it complains.
%%%
Running `Other' on `test-lua' with ``mtxrun --script context %t''
MtxRun
Le 17 mai à 10:11:13 Dalyoung Jeong [EMAIL PROTECTED] écrit notamment:
| However, the same command worked well in a terminal.
| Maybe the system setup of yours is different from mine.
| Usually I run source .luatex first before running luatex.
| So my guess is that emacs couldn't know the
On May 17, 2008, at 10:53 AM, Jean Magnan de Bornier wrote:
Le 17 mai à 10:11:13 Dalyoung Jeong [EMAIL PROTECTED] écrit notamment:
| However, the same command worked well in a terminal.
| Maybe the system setup of yours is different from mine.
| Usually I run source .luatex first before
Thomas A. Schmitz wrote:
Yes, you're both right. What I do (and what I find the easiest way):
start emacs from the same terminal where you have issued
source .luatex with the command open -a emacs. That way, emacs
should know about path variables.
Emacs has a setenv command, so you
Taco Hoekwater wrote:
luigi scarso wrote:
In
\starttext
\startTEXpage
\startlua
metapost.process(metafun,{beginfig(1);,
a=.7in; b=0.5in;,
z0=(0,0); z1=(a,0); z2=(0,b);,
z0=.5[z1,z3]=.5[z2,z4];,
draw z1..z2..z3..z4..cycle;,
drawarrow z0..z1;,
drawarrow z0..z2;,
label.top(btex $a$
Taco Hoekwater wrote:
Peter Rolf wrote:
hi,
i'm still trying to make my code run with mkiv. here are two minor
problems. the first one is easy to deal with, but the second one
currently breaks my testbed.
% engine=luatex
\setupcolors[state=start]
\starttext
\startMPcode
label(no
On May 17, 2008, at 11:28 AM, Taco Hoekwater wrote:
Emacs has a setenv command, so you could do the whole setuptex
in elisp with commands like this in your emacs startup script:
(setenv TEXMF
{$TEXMFOS,$TEXMFPROJECT,$TEXMFFONTS,$TEXMFLOCAL,$TEXMFEXTRA,!!
$TEXMFMAIN})
Maybe that is an
Aditya Mahajan wrote:
Hi,
While using oldstyle features with mkiv, -- in a typing environment comes
out as a endash. I would consider this a bug.
For example:
\setfontfeature{oldstyle}
\starttext
\starttyping
-- A comment 123
\stoptyping
\stoptext
Another interesting feature
On May 17, 2008, at 6:58 PM, Hans Hagen wrote:
Another interesting feature is that numbers in the typing
environmnet come
out in oldstyle (they look nice, BTW). This is expected, and can be
avoided by using a complete typescript and loading tt fonts with
fefault
features, and other
Ok.
In next example, f0 is hide
\starttext
\startTEXpage\startMPcode
%beginfig(2);
h=2in; w=2.7in;
path p[], q[], pp;
for i=1.5,2,4:
ii := i**2;
p[i] = (w/ii,h){1/ii,-1}...(w/i,h/i)...(w,h/ii){1,-1/ii};
endfor
for i=.5,1.5:
q[i] = origin..(w,i*h) cutafter p1.5;
endfor
pp =
Thomas A. Schmitz wrote:
On May 17, 2008, at 6:58 PM, Hans Hagen wrote:
Another interesting feature is that numbers in the typing
environmnet come
out in oldstyle (they look nice, BTW). This is expected, and can be
avoided by using a complete typescript and loading tt fonts with
On May 17, 2008, at 9:06 PM, Hans Hagen wrote:
in node-ini ... you can play with this change ...
function nodes.process_characters(head)
--~ if status.output_active then
if false then
return head, false -- true
else
Great! Yes, this seems to take
Hi,
I am trying to parse a xml file with mkiv to process a list of invoices
(factuur in dutch).
The xml file looks like this
?xml version='1.0 standalone='yes' ?
factuur
nummer123456789/nummer
datum1 januari 2008/datum
medewerker/medewerker
regels
omschrijvingOmschrijving geleverde dienst
13 matches
Mail list logo
