Just out of curiosity: what exactly do the following messages mean?
I'm experiencing a strange problem on the garden: some things that
work in "live" fail on the wiki.
(/opt/local/texmf/tex/context/cont-sys.texpdfetex: Not writing to
../type-exa (openin_any = p).
pdfetex: Not writing to ../../type-exa (openin_any = p).
(/opt/context/current/texmf/tex/context/base/type-exa.tex)pdfetex: Not
writing to ../type-syn (openin_any = p).
pdfetex: Not writing to ../../type-syn (openin_any = p).
(/…
[View More]opt/context/current/texmf/tex/context/base/type-syn.tex)pdfetex: Not
writing to ../type-enc (openin_any = p).
pdfetex: Not writing to ../../type-enc (openin_any = p).
(/opt/context/current/texmf/tex/context/base/type-enc.tex)pdfetex: Not
writing to ../type-siz (openin_any = p).
pdfetex: Not writing to ../../type-siz (openin_any = p).
(/opt/context/current/texmf/tex/context/base/type-siz.tex)pdfetex: Not
writing to ../type-map (openin_any = p).
pdfetex: Not writing to ../../type-map (openin_any = p).
(/opt/context/current/texmf/tex/context/base/type-map.tex)pdfetex: Not
writing to ../type-spe (openin_any = p).
pdfetex: Not writing to ../../type-spe (openin_any = p).
To be more specific, I was testing Hans's example:
\definefontsynonym [MathGamma] [prodint]
\definefamilysynonym [default] [xop] [mc]
\startmathcollection [default]
\definemathsymbol [prodi] [op] [xop] [80]
\definemathsymbol [Prodi] [op] [xop] [82]
\definemathsymbol [PRODI] [op] [xop] [84]
\stopmathcollection
\loadmapfile[prodint]
\starttypescript [math] [modern,computer-modern,latin-modern,ams] [size]
\definebodyfont
[17.3pt,14.4pt,12pt,11pt,10pt,9pt,8pt,7pt,6pt,5pt,4pt] [mm] [mc=prodint]
\stoptypescript
\definetypeface [modern] [mm] [math] [modern]
[computer-modern][encoding=default]
\setupbodyfont[reset,modern,10pt]
\enablemathcollection[prodint]
$\prodi$
Thanks,
Mojca
[View Less]
Hi Patrick,
Occasionally, while browsing sources at source.contextgarden.net, I
feel the need of seeing the pdf copy of that file. I wonder how
difficult will it be to add a link, say "View pdf" with each file
listing, so that if I click that link, I see the output of
texexec --module filename.tex
I do not know if the perl scripts support this. From what I remember,
in perl texutil kept care of generate module listing.
Maybe, the pdf files can be cached (no idea how) so that they are …
[View More]not
regenerated, or maybe they can be autogenerated each time the source
files are updated.
Do not spend too much time on this, I can always do it on my own
machine :-)
Aditya
[View Less]
Seems to be a bug in the ruby code that works properly in the perl. Try:
----
\starttext
\index{Knuth}\input knuth \par
\seeindex{Knuth}{Tufte}\input tufte \par
\blank\placeindex
\stoptext
----
With the perl scripts it's right:
Knuth 1
see Tufte
but with the new ruby scripts it's wrong:
Knuth
see Tufte, 1
I don't know if it's relevant but the difference between the two .tuo
files seems just to be reversal of two lines; the perl run shows:
\registerentry{index}{k}
\registerentrya{…
[View More]index}{Knuth}
\registerpage{index}{,}{1}{2--0-0-0-0-0-0-0--1}{1}
\registersee{index}{,}{Tufte}{2--0-0-0-0-0-0-0}
while the ruby run shows:
\registerentry{index}{k}
\registerentrya{index}{Knuth}
\registersee{index}{,}{Tufte}{2--0-0-0-0-0-0-0}
\registerpage{index}{,}{1}{2--0-0-0-0-0-0-0--1}{1}
[I discovered this by trying out the code on live.contextgarden, and I
couldn't understand why I was getting different output from apparently
the same beta - but then I noticed that the live server is still using
the old texexec script. Perhaps this ought to be fixed (though it was
very useful in this case!).]
Duncan
[View Less]