meino.cra...@gmx.de wrote: > ...and dont forget to do a > > ls -R . > ls-R > > in the according root directory, from where are all > *.fmt are installed, otherwise kpathsea will fail to find the file.
Oh yeah, forgot about that. > But what was the idea behind "tex" to behave like compiling/texing > for /LaTeX/ instead of plain TeX? This is the first time, when I > have to call virtex to compile/tex for plain tex format... > > Even the manpages say: > > This version of TeX looks at its command line to see what name it > was called under. If they exist, then both initex and virtex are > symbolic links to the tex executable. When called as initex (or > when the -ini option is given) it can be used to precompile macros > into a .fmt file. When called as virtex it will use the plain > format. When called under any other name, TeX will use that name > as the name of the format to use. i > > (But:) > For example, when called as tex the tex format is used, which > is identical to the plain format. The commands defined by > the plain format are documented in The TeX for nroffbook. > Other formats that are often available include latex and > amstex. > > So, there seems something non-standard or my installation git rotten > regarding this... Well, if possible, you could always try this on another system, to see if it's unique to your machine... > Normally initex is used to create *.fmt files. And virtex (from virgin > tex) is the one which does it works without any tex format -- the > way to write in "TeX assembler" so to say... > > Myterious the world we live in, mysterious the way we go... Couldn't agree more. :-) MfG Peter K
