Re: [NTG-context] Runtime graphics
At 01:34 13/06/2003 -0400, you wrote:
Hi,
I run this simple test file test.tex :
%cont-en
\setupoutput[pdftex]
\runMPgraphicstrue
\starttext
\startMPrun
input graphserieA
\stopMPrun
\externalfigure[mprun.1]
\externalfigure[mprun.2]
%
\startMPrun
input graphserieB
\stopMPrun
\externalfigure[mprun.1]
\externalfigure[mprun.2]
\stoptext
\end .
In the logfile, I got the messages :
figures: figureobject test-mprun.1 is reused
figures: figureobject test-mprun.2 is reused
and twice the figures of graphserieA.mp on test.pdf.
Is there a way to avoid the re-use of test-mprun.1 and test-mprun.2, I mean
a way to overwrite the files test-mprun.1 and test-mprun.2 ?
Or a way to get different names for each metapost output as, for example,
graphserieA-mprun.1, graphserieA-mprun.2 and graphserieB-mprun.1,
graphserieB-mprun.2 ?
I could also give a different number to each of the figures in all of the
*.mp files, but this solution is not pacticable since I have plenty of
metapost files to process, each of it containing a lot of figures already
numbered with almost the same numbers. Moreover, those numbers can not be
modified because the figures are elsewhere referenced by their number and by
the name of the metapost file.
You can redefine:
\def\MPrunfile#1{\bufferprefix mprun.#1}
to for instance
\def\MPrunfile#1{\bufferprefix \MyMpRunFile.#1}
\def\MyMpRunFile{mprun}
and them change the definition of \MyMpRunFile whenever you want
Hans
-
Hans Hagen | PRAGMA ADE | [EMAIL PROTECTED]
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] differences of table modes
At 18:32 12/06/2003 +0200, you wrote: Ahoi! I just reviewed my german ConTeXt tutorial and tried to tell the truth about all the table modes. Please correct me if I'm wrong: * tabulate - can break over several pages - [start|stop]tabulate[head|tail] should define a repeated head/tail, but it doesn't work works here \starttext \starttabulatehead \NC left \NC right \NC \NR \stoptabulatehead \starttabulate[|l|r|] \NC l \NC r \NC \NR \stoptabulate \stoptext - documented in the manual (cont-en[i|p]) - handles (multiple) paragraphs with the p template entry - works well with grids - supports text backgrounds * table - cannot break - based on Wichura's TaBlE (others not) - can be used as float (others not?) all can be used as floats - documentation commercial at pctex.com (39 $), partly docs in ConTeXt - an excursion (m[s|p]-cb-en) * tables - same as table, but can break over several pages - [start|stop]table[head|tail] works - nowhere documented? in my still to be included chapter if the manual it is -) * TABLE - didn't try page breaks yet; should it work? yes, if split is set to yes - [b|e]TABLE works; should [start|stop]TABLE also? no, at least not yet; has to do with grabbing - docs: up-to-date 8 (no link on HP!), enattab * new table mode? I remember Hans wrote about a new enhanced table mode, but can't find the mail. core-ltb: line tables, auto break vertically and horizontally across pages, repeated rows / columns, etc will be documented Hans - Hans Hagen | PRAGMA ADE | [EMAIL PROTECTED] Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com - information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf - ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texexec
At 11:01 12/06/2003 -0400, you wrote:
I've been a debian woody user for a long time, now,
and the conclusion I eventually came to was this:
* debian's strict adherence to directory structure
conventions has made the tetex package difficult
to maintain, since it's split into many parts,
spread all over the filesystem. (This is really
just an inference of mine.)
The nice thing about tex is that it is quite well organized (in its own
tree) and splitting it up over many places makes it a pain to maintain; for
instance, do the debian people offer extensive cleanup-remove scripts? I
wonder how the tex community is supposed to provide support to users if all
redistributers would change the tex tree organization to their needs.
* context has never worked for me in debian, and
submitting a bug report looks hopeless, given the
long length of the bug list. I haven't checked
in a long time, though.
* I wasn't able to use the equivs package to get
the debian packaging system to accept my own tetex
installation, so I could not install, e.g., the
docbook-xsl-st package.
* finally, I settled on this: install the debian
tetex packages but don't use them directly. Also
install teTeX from source in /opt, and set my
PATH so that when I say texexec I get the real
tetex and not debian's broken tetex.
what i do here is the following:
(1) when a new tex live arrives, i copy this to /tex/texmf
(2) i keep my local context + some fonts in /tex/texmf-local
(3) i put all new fonts (mostly commercial) in /tex/texmf-fonts
(4) i put all the binaries in /tex/texmf-linux/bin|web2c
(so, i also have texmf-mswin, texmf-darwin, etc)
if needed in project, i also have a /tex/texmf-project
I have set up texmf.cnf as well as cont-sys.tex set up in the texmf-local
tree to enable metapost processing
Finally I get rid of all the os specific settings and hook these trees into
the whole:
btw 1, in most cases i just use TEXROOT=/tex
btw 2, i also have a minimal 50 meg main texmf tree which makes tex run
much faster
so, i use tex live (tetex,fptex) as basis and not the linux distributers
alternative
# . setuptex
# mktexlsr
# texexec --make --alone
TEXROOT=/usr/local/tex
export TEXROOT
TEXMFMAIN=$TEXROOT/texmf
TEXMFLOCAL=$TEXROOT/texmf-local
TEXMFFONTS=$TEXROOT/texmf-fonts
TEXMFPROJECT=$TEXROOT/texmf-project
TEXMFOS=$TEXROOT/texmf-linux
VARTEXMF=$TEXROOT/texmf-var
export TEXMFMAIN
export TEXMFLOCAL
export TEXMFPROJECT
export TEXMFFONTS
export TEXMFOS
export VARTEXMF
PATH=$TEXMFOS/bin:$PATH
export PATH
HOMETEXMF=
export HOMETEXMF
# the next lines fail on dec alpha os's, so there you need
# to comment them (bug traced down by kees van marle/martin
# corrino)
#
# HOMETEXMF=/nonexist
# export HOMETEXMF
TEXMFCNF=$TEXROOT/texmf{-local,}/web2c
TEXMF='{$TEXMFOS,$TEXMFPROJECT,$TEXMFFONTS,$TEXMFLOCAL,!!$TEXMFMAIN}'
TEXFORMATS=$TEXMFOS/web2c
TEXPOOL=$TEXFORMATS
MPPOOL=$TEXFORMATS
export TEXMFCNF
export TEXMF
export TEXFORMATS
export TEXPOOL
export MPPOOL
-
Hans Hagen | PRAGMA ADE | [EMAIL PROTECTED]
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Improving the Documentation of Context
Matthias Vogel wrote: I think it would be nice to have the manuals improved in the following not very costly way (??? indicates my ignorance): \setuplayout[..,..=..,..] width dimension fit middle .width, ??? and orientation of main text heightdimension fit middle .height of main text backspace dimension topspace dimension margindimension nxnumber. ??? nynumber. ??? dxdimension.. ??? dydimension.. ??? lines number. number of lines on the page [I don't know the relation to height] grid yes no. invoking setting to grit Since the manual doesn't even mention all those options, even a very short hint is much better than just trying around to get an idea what's the idea of an option. I usually find the etexshow mode for Emacs helpful. It gives you easy access to the details of ConTeXt commands. ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
