lain,generic,latex,}//
TEXINPUTS.platex-ng = $TEXMFDOTDIR;$TEXMF/tex/{uplatex,platex,latex,generic,}//
% (e)up(La)TeX, and for upmpost
TEXINPUTS.uplatex =
$TEXMFDOTDIR;$TEXMF/tex/{uplatex,platex,latex,generic,}//
TEXINPUTS.uplatex-dev =
$TEXMFDOTDIR;$TEXMF/tex/{latex-dev,uplatex,platex,lat
context table mechanisms don't use & (and never used it)
so ther ei sno reason to make & special. The _ and ^ are also normal
characters. For now we keep the $ for math (and in math mode the & ^ _
work as expected).
Although we're to some extend plain compatible it's no
h we're to some extend plain compatible it's not our aim, just
like we're not amstex, latex, lamstex or anytex compatible.
Ok. Thanks for the explanation. I wrote to Peter that developer context
to have a reason, and certainly it would from an ordinary whim not done.
Even so
tible it's not our aim, just
like we're not amstex, latex, lamstex or anytex compatible.
Ok. Thanks for the explanation. I wrote to Peter that developer context
to have a reason, and certainly it would from an ordinary whim not done.
Even so, I am very satisfied with the degree of compat
we keep the $ for math (and in math mode the & ^ _
work as expected).
Although we're to some extend plain compatible it's not our aim, just
like we're not amstex, latex, lamstex or anytex compatible.
Hans
--
omputer modern and math; also there is some math
setup, some register management, some structure commands and a bit of
tabular stuff
at that time i think that the general idea was that one would write a
style for each book (or series) and that a plain like package can be
used as basis
context is (like
Aditya Mahajan wrote:
> Yes, I meant, why Context's defaults are different from latex's (and
> plain tex)
because i hardly used, plain, only used latex for one document, then
moved on to lamstex, inrstex and then started making a package that was
configurable nd and could hand
/base/spec-fdf.mkiv))
specials: fdf loaded
)
specials: fdf,tpd loaded
systems : begin file luatexref-env.tex at line 11
(./luatexref-env.tex
system : module abr-02 loaded
(/opt/texlive/ContextMKiv/tex/texmf-local/tex/context/base/s-abr-02.tex
system : mod
: message:: duplicate tag file in library setup of interface en
glish
debugger: message:: duplicate tag reference in library setup of interfa
ce english
[EMAIL PROTECTED]@\setuptext=\count212
) (/opt/texlive/2005-test/texmf-dist/tex/context/interface/cont-en.xml))
system : modul
on file tpd
> (e:\isoimage\usr\local\context\tex\texmf-local/tex/context/base/spec-tpd.tex
> specials: loading definition file fdf
> (e:\isoimage\usr\local\context\tex\texmf-local/tex/context/base/spec-fdf.tex)
> specials: fdf loaded
> )
> specials: fdf
ile fdf
(e:\isoimage\usr\local\context\tex\texmf-local/tex/context/base/spec-fdf.tex)
specials: fdf loaded
)
specials: fdf,tpd loaded
)
\openout0 = `test2-mpgraph.mp'.
\openout0 = `mpgraph.mp'.
systems : system commands are enabled
system : module abr-01
-02.tex
system : module abr-01 loaded
(/usr/local/teTeX/share/texmf.local/tex/context/base/s-abr-01.tex
check : logo AMSTEX replaces a macro, use CAPITALS!
check : logo CONTEXT replaces a macro, use CAPITALS!
check : logo ETEX replaces a macro, use CAPITALS!
chec
aleph = .;$TEXMF/tex/{plain,generic,}//
% Context macros by Hans Hagen:
TEXINPUTS.context = .;$TEXMF/tex/{context,plain,generic,}//
% odd formats needing their own paths
TEXINPUTS.lamstex = .;$TEXMF/tex/{lamstex,plain,generic,}//
TEXINPUTS.lollipop = .;$TEXMF/tex/{lollipop,plain,generic,}//
TEXINPU
feTeX.
TEXINPUTS.pdfelatex = .;$TEXMF/{pdfetex,pdftex,etex,tex}/{latex,generic,}//
TEXINPUTS.pdfetex = .;$TEXMF/{pdfetex,pdftex,etex,tex}/{plain,generic,}//
% Omega.
TEXINPUTS.lambda = .;$TEXMF/{omega,tex}/{lambda,latex,generic,}//
TEXINPUTS.omega = .;$TEXMF/{omega,tex}/{plain,generic,}//
% Cont
read: amstex and latex were pushed by user groups
in favor of for instance lamstex, inrstex, etc) ;
You are right: and I hope ConTeXt will becomme the standard (:-)
For this, one need:
1 - a clear polilical objective for context,
hm, i'm not going to promise context-2 (like latex-3), but here are
ex were pushed by user groups in
favor of for instance lamstex, inrstex, etc) ;
concerning contribution: context itself is not that unfinished; also,
there *are* contributions, take for instance the area of fonts and
languages
For this, one need:
1 - a clear polilical objective for context,
hm,
//
% MLTeX
TEXINPUTS.mltex = .;$TEXMF/{mltex,tex}/{plain,generic,}//
TEXINPUTS.mllatex = .;$TEXMF/{mltex,tex}/{latex,generic,}//
% odd formats needing their own paths
TEXINPUTS.lollipop = .;$TEXMF/tex/{lollipop,generic,plain,}//
TEXINPUTS.lamstex = .;$TEXMF/tex/{lamstex,generic,plain,}//
% Earlier en
17 matches
Mail list logo
