I ran sudo ctxtools --updatecontext about one hour ago and all this
that you write here can't be found (s-pre-63.tex is the latest) ...
Where did you mean should I grep the sources for definefontfeature ??
Steffen
Am 06.12.2007 um 17:35 schrieb Mojca Miklavec:
On Dec 6, 2007 5:09 PM
20.11.2007 um 01:57 schrieb Mojca Miklavec:
On 11/19/07, Joel C. Salomon wrote:
Guess I asked for too much at once.
I've downloaded the Gentium Basic/Basic Book set of fonts from
http://scripts.sil.org/Gentium_basic, and I'd like to use them with
ConTeXt. I ran texfont (with the command
On Nov 22, 2007 1:31 PM, Wolfgang Schuster
[EMAIL PROTECTED] wrote:
The following works for me with LuaTeX and XeTeX. I had my test
file in the same directory as the fonts, can you try this or you
forgot to call fc-cache -v -r.
I ran fc-cache -v -r, and that typescript worked for me, but I
Guess I asked for too much at once.
I've downloaded the Gentium Basic/Basic Book set of fonts from
http://scripts.sil.org/Gentium_basic, and I'd like to use them with
ConTeXt. I ran texfont (with the command line texfont
--fontroot=c:\users\chesky\programs\context\tex\texmf-local
--sourcepath
Joel C. Salomon wrote:
Guess I asked for too much at once.
I've downloaded the Gentium Basic/Basic Book set of fonts from
http://scripts.sil.org/Gentium_basic, and I'd like to use them with
ConTeXt. I ran texfont (with the command line texfont
--fontroot=c:\users\chesky\programs\context
On 11/19/07, Joel C. Salomon wrote:
Guess I asked for too much at once.
I've downloaded the Gentium Basic/Basic Book set of fonts from
http://scripts.sil.org/Gentium_basic, and I'd like to use them with
ConTeXt. I ran texfont (with the command line texfont
--fontroot=c:\users\chesky
by doing:
texexec --make --all
To check I had the correct version, I ran, on the commandline, these two:
texexec --check
and:
ctxtools --contextversion
Both gave me 2007.09.28 16:52, which seems quite correct.
However, when I try to compile a document (with the --xtx option), I
get
didn't work. A problem with the
paths. First red flag, but I went on manually.
I got the newest cont-tmf.zip and unzipped it in /usr/share/texmf and
regenerated the formats by doing:
texexec --make --all
To check I had the correct version, I ran, on the commandline, these two:
texexec
Hi Pascal,
I adjusted it to my own situation (AGaramondPro, not the Premier
version). And I ran it succesfully. However, I can't see where the files
have gone?
They end up in a directory called texmf in the local directory, unless
you have given the command line to change this directory (see
and named it texlua and put it in the
texmf-linux/bin
directory.
Then after reading the MyWay on MKIV I did a texexec --make --all --luatex
to generate the formats and ran succesfully the following tex script and
produced a pdf file.
% engine=luatex
\starttext
Hello from luatex
\blank
LUA
\startlua
standalone installation, unzipped it, and ran
texexec --lua file. With pdftex this used to work because the formats
were located in the texmf tree. However, AFAIU, mkiv wants the
standards to be in the TEXMFCACHE directory (which is mapped to the
TEMP directory). So, simply getting the zip files
Aditya Mahajan wrote:
I noticed similar problem (texexec --lua fails without any useful
message) when I tried to install context on a new machine. I simply
downloaded context standalone installation, unzipped it, and ran
texexec --lua file. With pdftex this used to work because the formats
boldGaramondPremrPro-Bd.otf
italic GaramondPremrPro-It.otf
bolditalic GaramondPremrPro-BdIt.otf
--
I adjusted it to my own situation (AGaramondPro, not the Premier
version). And I ran it succesfully. However, I can't see where
from you. I just ran:
% hans-prob.tex
\starttext
I used to place references to figures and tables in the following way:
\placefigure[][fig:myfig]{Title}{Content}
\in{figure}[fig:myfig]
This however printed a dot instead of the expected figure .
Changing to \at{figure}[fig:myfig] again printed
Ok, I saw I have asked the same thing before on the list, and I'm
having the same problems, but cannot reconstruct the whole process.
(As soon as I end up, I'll wikify the infos)
Now, I'm always runnin texexec --make --all
Doesn't it make also metafun?
I also ran texexec --make metafun
, apparently it gives an error
I also ran texexec --make metafun but I'm getting the same error.
Are you sure it is the exact same error? (it shouldn't be).
Can you cut and paste the complete output of
texexec --make --verbose metafun
please?
Best wishes, Taco
I comment out the following line, compiles fine, and get what I want,
\Topics, \Topic seems not work here, but it's fine.
\overcomePDFpagefalse
I ran it under Debian/unstable.
Thanks, Hans and Zhichu
regards,
Lingyun
On 5/9/07, Hans Hagen [EMAIL PROTECTED] wrote:
Lingyun Yang wrote:
Thank
Hi Hans,
I ran into the following problem.
\startfiguretext ... \stopfiguretext generates an error about
undefined controlsequence \stopfiguretext -\dostoptextfloat.
ConTeXt ver: 2007.03.19 11:20 MKII fmt: 2007.3.29 int: english/
english
Willi Egger
[EMAIL PROTECTED
Willi Egger wrote:
Hi Hans,
I ran into the following problem.
\startfiguretext ... \stopfiguretext generates an error about
undefined controlsequence \stopfiguretext -\dostoptextfloat.
\startfiguretext
{caption}
{\externalfigure[dummy]}
\input tufte
\stopfiguretext
works
version is 2007.01.12.
Then I ran ctxtools which installed an updated ConTeXt in texmf-local
(besides the folder 2007). Now the pdfTeX engine still works fine.
However, XeTeX complained about the wrong format files. So I remade
them with texexec --make --xtx en nl. Later XeTeX spills out
Dear folks,
I'm afraid I'm facing the XeTeX problem again after I updated ConTeXt
to version 2007.02.21 :-(
On a freshly installed MacTeX-2007 (which is TeXLive 2007 up to minor
modifications) everything is fine. The ConTeXt version is 2007.01.12.
Then I ran ctxtools which installed
.
Then I ran ctxtools which installed an updated ConTeXt in texmf-local
(besides the folder 2007). Now the pdfTeX engine still works fine.
However, XeTeX complained about the wrong format files. So I remade
them with texexec --make --xtx en nl. Later XeTeX spills out the
following:
---
TeXExec
As I ran into the same problem I followed your instructions ...
running the ctxtools command doesn't resolve it I'm afraid.
$ kpsewhich lm-math.map
/usr/local/gwTeX/texmf.texlive/fonts/map/dvips/lm/lm-math.map
You should try that with --engine=dvipdfm , because dvipdfmx
will find different
/
20070130.082837.4bc51f61.en.html
As I ran into the same problem I followed your instructions ...
running the ctxtools command doesn't resolve it I'm afraid.
$ kpsewhich lm-math.map
/usr/local/gwTeX/texmf.texlive/fonts/map/dvips/lm/lm-math.map
So I issued
$ ctxtools --dpx --force /usr/local/gwTeX
with the xetex engine, during the xdvipdfmx
processing, I got the following message, and all the math symbols are
missing:
Please see this thread:
http://archive.contextgarden.net/message/
20070130.082837.4bc51f61.en.html
As I ran into the same problem I followed your instructions
As I ran into the same problem I followed your instructions ...
running the ctxtools command doesn't resolve it I'm afraid.
$ kpsewhich lm-math.map
/usr/local/gwTeX/texmf.texlive/fonts/map/dvips/lm/lm-math.map
So I issued
$ ctxtools --dpx --force /usr/local/gwTeX/texmf.texlive
CtxTools
Hi,
once again I ran into a dead-end where I never dreamt it could be a
problem: using footnotes in tables.
For my current project I have to use 16 tables, spread over the whole
text (about 400 pages).
Some of these tables also need footnotes (sometimes quite large). But
they should
.texmf-config into
/var/lib/texmf/web2c and ran texhash. Things seem to be OK.
But now, whenever I do texexec filename, I get a PDF with many mathematical
symbols missing. So, I do this:
texexec --dvi ee03b091.tex
dvips ee03b091.dvi
ps2pdf ee03b091.ps
Now, this seems to work, but the fonts
code 1 is texexec's normal failure code, usually from an undefined
cseq. Exit code 5 is from the run-it.py wrapper, which is saying that
time (60 sec) ran out, before the texexec process had to be killed. And
exit code 6 says that the logfile grew too big (currently, beyond 1MB)
before the texexec
just ran the
above example in Context.
I use whatever tool gets the job done.
--
John Culleton
Able Indexing and Typesetting
Precision typesetting (tm) at reasonable cost.
Satisfaction guaranteed.
http://wexfordpress.com
___
ntg-context mailing list
On 1/19/07, John R. Culleton [EMAIL PROTECTED] wrote:
Has anyone put together a typescript for some or all of the Nimbus family? I
have the font referenced above and ran it through texfont. It is specified by
a customer's designer for a book I am working on. I can of course do the old
plain
Has anyone put together a typescript for some or all of the Nimbus family? I
have the font referenced above and ran it through texfont. It is specified by
a customer's designer for a book I am working on. I can of course do the old
plain TeX \font thing but I would like to do it a more
not to strip the binaries, and ran it
with debugging libraries and valgrind, like so:
LD_LIBRARY_PATH=/usr/lib/debug: valgrind pdfetex -fmt=cont-en b.tex
and the output is included below. Here is the chunk from it, where
the problem is first detected by valgrind:
==27710== Invalid write of size
}
\chapter{C}
\dorecurse{100}{\input tufte\par}
\stoptext
I ran it with the attached Makefile, which produced this output:
ctxtools --purge --all /dev/null
rm -f q.pdf
texexec --verbose --fast --final q.tex run.log
Total runs: 4
\par}
\stoptext
I ran it with the attached Makefile, which produced this output:
ctxtools --purge --all /dev/null
rm -f q.pdf
texexec --verbose --fast --final q.tex run.log
Total runs: 4 (counted by grepping run.log for running: pdfetex
Ok. As for the strange things happening I was able to hunt them down
and prepare a simple example (still with the standard
\startquotation):
We are looking into this. All footnotes in vertical mode are
behaving oddly.
Thanks!
I tried that one but ran into several problems unfortunately
the reference before the
closing marks, and moving \cite out of the \start \stop block makes
the reference appear on a new line ...
The next solution is a bit rude, but works:
...
I tried that one but ran into several problems unfortunately. If
\cite inserts anything but a tiny string
pusillanimous sesquipedalian longwinded
\stopcitedquotation
\stoptext
I tried that one but ran into several problems unfortunately. If
\cite inserts anything but a tiny string these words won't be wrapped
properly onto a new line. Also if I replace \cite[#1] by \footnote
{\cite[#1
Hi Taco, any progress?
- Matthias
On 24.10.2006 15:13, Taco Hoekwater wrote:
Hi Matthias,
I goofed somewhere, that's for sure. Are you in a real hurry, or can
I take a day or two staring at it?
Taco
Matthias Wächter wrote:
Hi Taco,
I ran into the following problems:
1. see
Hi Taco,
I ran into the following problems:
1. see attached files. Three bib entries with different authors, but the resulting references are the same for two of them (!).
Appearantly, without sorting the bib entries, the extra label numbering does not work correctly. Changing \setupbibtex
Hi Matthias,
I goofed somewhere, that's for sure. Are you in a real hurry, or can
I take a day or two staring at it?
Taco
Matthias Wächter wrote:
Hi Taco,
I ran into the following problems:
1. see attached files. Three bib entries with different authors, but the
resulting references
On Tue, Oct 10, 2006 at 07:21:54PM +0100, Sanjoy Mahajan wrote:
I ran it here (ver: 2006.10.05). With just \placetable[here], it
doesn't split. With \placetable[here,split], it splits it into two
parts with Table 1.a on one page and Table 1.b on the other page.
With my version (of Debian
2006/10/11, Gerhard Kugler [EMAIL PROTECTED]:
On Tue, Oct 10, 2006 at 07:21:54PM +0100, Sanjoy Mahajan wrote: I ran it here (ver: 2006.10.05
).With just \placetable[here], it doesn't split.With \placetable[here,split], it splits it into two parts with Table 1.a on one page and Table 1.b
I have at the moment no ConTeXt where I can test your example file
but you should try to change the first line of your float from
\placetable[here]...
to
\placetable[here,split]...
I hope it works for you and I also try to run your file till tomorrow.
I ran it here (ver
even if it is working now for some reason.
I ran into the same issue a few days ago and eventually found my to
the same solution. About the 'some reason': I noticed that without
the fix, sometimes it worked, sometimes it didn't. The answer is the
damn database file (the ls-R). kpathsea searches
Now that \sometxt works with static figures (thanks!), I'm converting
from using btex..etex to using \sometxt, to avoid MPenvironments
(instead put it in the general .tex environment).
But I ran into an error with macro arguments and static figures. Let me
know if it's not worth fixing in view
versions. 4.log says
that write18 ran
texmfstart --ifchanged=4-fig.mp texexec --mpstatic 4-fig.mp
I ran it by hand omitting the --ifchanged:
$ texmfstart texexec --mpstatic 4-fig.mp
/home/sanjoy/texmf/scripts/context/ruby/texexec.rb:101:in `mpstatic'TeXExec |
option 'randomseed' is set to '1131
Sanjoy Mahajan wrote:
Wolfgang,
Thanks for the pointer. I don't have a cont-sys.tex, but cont-sys.rme
has these lines
% \runMPgraphicstrue
% \runMPTEXgraphicstrue
The .rme extension meant I'd missed it when I ran grep on the .tex
files. I'll uncomment them.
Oh, that's not a good idea
Wolfgang,
Thanks for the pointer. I don't have a cont-sys.tex, but cont-sys.rme
has these lines
% \runMPgraphicstrue
% \runMPTEXgraphicstrue
The .rme extension meant I'd missed it when I ran grep on the .tex
files. I'll uncomment them.
Oh, that's not a good idea, because the next context
On Sat, 23 Sep 2006 17:46:56 +0100
Sanjoy Mahajan [EMAIL PROTECTED] wrote:
Wolfgang,
Thanks for the pointer. I don't have a cont-sys.tex, but cont-sys.rme
has these lines
% \runMPgraphicstrue
% \runMPTEXgraphicstrue
The .rme extension meant I'd missed it when I ran grep on the .tex
).
Thanks for checking it both ways. Now I'm really puzzled because I
also use Firefox (on Linux). I just ran the file below at
contextgarden (same one as before but with the MPTEX addition), and it
gives 'undefined' in a square where the figure should be. And on my
Ubuntu laptop with context 2006.08.08
too (using Firefox).
Thanks for checking it both ways. Now I'm really puzzled because I
also use Firefox (on Linux). I just ran the file below at
contextgarden (same one as before but with the MPTEX addition), and it
gives 'undefined' in a square where the figure should be. And on my
Ubuntu
On 9/16/06, Alan Bowen wrote:
I have not been able to get Greek hyphenation to work. To make sure
that my set up was right (?),
I ran
texfmstart ctxtools --pat
and put the pattern files in /usr/local/teTeX/share/texmf.local/tex/
context/patterns
The log file shows
CtxTools
Mojca—
Many thanks for your suggestions. Over the weekend, at Thomas’
suggestion, I
• deleted and re-stalled teTeX
• unzipped cont-tmf.zip into /usr/local/teTeX/share/texmf.local
• copied lang-agr.pat (fr0m Thomas) into /usr/local/teTeX/share/
texmf.local/tex/context/patterns
• ran sudo
, Johan
2006/9/17, Sanjoy Mahajan [EMAIL PROTECTED]:
path = run(--expand-path=\\\$#{varname}) rescue ''
to
path = run(--expand-path=\$#{varname}) rescue ''
I also ran into this (a few weeks ago on the list) and the patch I
sent Hans after testing it on my Ubuntu Linux laptop
Johan Sandblom wrote:
I also ran into this (a few weeks ago on the list) and the patch I
sent Hans after testing it on my Ubuntu Linux laptop was to use two
backslashes:
run(--expand-path=\\$#{varname})
My suggestion would be:
run(--expand-path='$#{varname}')
Taco
Yes, that works.
Johan
2006/9/17, Taco Hoekwater [EMAIL PROTECTED]:
Johan Sandblom wrote:
I also ran into this (a few weeks ago on the list) and the patch I
sent Hans after testing it on my Ubuntu Linux laptop was to use two
backslashes:
run(--expand-path=\\$#{varname})
My suggestion
and testing my TestFile.
While creating different examinations this weekend for my students I
ran again in trap using tables. But this time I did not use any macro.
Just two simple tables.
The example works with context : ver: 2005.01.31
but not with ConTeXt ver: 2006.08.22
The main problem
Taco Hoekwater wrote:
Johan Sandblom wrote:
I also ran into this (a few weeks ago on the list) and the patch I
sent Hans after testing it on my Ubuntu Linux laptop was to use two
backslashes:
run(--expand-path=\\$#{varname})
My suggestion would be:
run(--expand-path
Hi,
After switching to `XeConTeXt' my file with MP graphics (which ran fine
before) results in errors. I include a .mp-file like:
\startuseMPgraphic{dia1}
input Diagram1 ;
\stopuseMPgraphic
\placefigure{Comment}{\externalfigure[Diagram1.1]}
When I run ConTeXt a file test-mprun.mp is created
Alex Lubberts wrote:
Hi,
After switching to `XeConTeXt' my file with MP graphics (which ran fine
before) results in errors. I include a .mp-file like:
\startuseMPgraphic{dia1}
input Diagram1 ;
\stopuseMPgraphic
\placefigure{Comment}{\externalfigure[Diagram1.1]}
When I run ConTeXt
On 9/16/06, Hans Hagen wrote:
Alex Lubberts wrote:
Hi,
After switching to `XeConTeXt' my file with MP graphics (which ran fine
before) results in errors. I include a .mp-file like:
\startuseMPgraphic{dia1}
input Diagram1 ;
\stopuseMPgraphic
\placefigure{Comment
path = run(--expand-path=\\\$#{varname}) rescue ''
to
path = run(--expand-path=\$#{varname}) rescue ''
I also ran into this (a few weeks ago on the list) and the patch I
sent Hans after testing it on my Ubuntu Linux laptop was to use two
backslashes:
run(--expand-path=\\$#{varname})
so
Thomas A. Schmitz wrote:
I just ran into the same question. When using a citation style that
doesn't quote the year (like refcommand=num), it seems more logical
to drop the maybeyear letter. It seems to work setting
\def\maybeyear{\gobbleoneargument}
I haven't seen any side
I have not been able to get Greek hyphenation to work. To make sure
that my set up was right (?),
I ran
texfmstart ctxtools --pat
and put the pattern files in /usr/local/teTeX/share/texmf.local/tex/
context/patterns
The log file shows
CtxTools | processing language agr
CtxTools
time since I looked at this problem. It is
not totally unsolvable, but definately not simple either.
Taco,
I just ran into the same question. When using a citation style that
doesn't quote the year (like refcommand=num), it seems more logical
to drop the maybeyear letter. It seems to work
(ran
pdftex anyway and produced pdf).
--nobackend
Thanks, that switch was news to me.
-Sanjoy
`Never underestimate the evil of which men of power are capable.'
--Bertrand Russell, _War Crimes in Vietnam_, chapter 1.
___
ntg-context mailing
\dorecurse{50}{
\input tufte
}
\stoptext
Then I ran 'texexec --pdfarrange --paper=a5a4 p5.pdf' (the --2up
doesn't change the error below) and got this error:
! Missing number, treated as zero.
to be read again
a
\@@ppoffset -a
5a4
\calculatepaperoffsets ...lue
texexec --pdfarrange --paper=a5a4 --2up yourfile.pdf
I tried a few experiments with no luck. Not sure if it's a context or
texexec problem, or my confusion. I made the multi-page p5.pdf from
\setuppapersize[A4][A4]
\starttext
\dorecurse{50}{
\input tufte
}
\stoptext
Then I ran 'texexec
of output, and you will probably
see an expansion loop occuring (if not, then it may be a ruby issue).
i just ran into the loop as well,
it has to do with a change in load order of modules, i'll fix it (i'm trying to
get rid of funny dependencies and this alpha/beta release was actually
) has already been loaded. Here is a minimal min.tex to show
what I mean:
I remember I ran into that as well (more than a year ago) and I ended
up renaming my figures to figure1-1.pdf etc. It actually turned out
to be easier for me, because that way I could use the figure filename
, and you will probably
see an expansion loop occuring (if not, then it may be a ruby issue).
i just ran into the loop as well,
it has to do with a change in load order of modules, i'll fix it
It works fine with the new version.
(i'm trying to get rid of funny dependencies and this alpha
Taco sez:
Sanjoy sez:
The figure searching code gets confused if a file of the same
basename (but in a different directory) has already been loaded.
I remember I ran into that as well (more than a year ago) and I
ended up renaming my figures to figure1-1.pdf etc. It actually
turned out
it for ConTeXt
experiments if needed.
-Sanjoy
Sanjoy—
Since I use the teTeX distribution on my Mac, I ran
TEXMFLOCAL=/usr/local/teTeX/share/texmf.local sudo texmfstart
ctxtools --updatecontext
in Terminal (bash) and the update went perfectly.
Many thanks!
Alan
a symlink in my private texmf tree (ec.enc - lm-ec.enc) and ran
texhash, and after that it was all the same. Anyway, this would not
explain why I have the same symptom with the texnansi encoding, too.
Maybe it helps debugging that dvips gives different error messages:
This is dvips(k) 5.95a
the date when you ran texmfstart texexec
--make --all. If that is older, the format file wasn't written to the
right place.
You seem to use Ubuntu. I don't know how things are configured there,
but I had numerous problems under MikTeX. The reason was that texexec
--make --all didn't have any
typeset on the upper half of the page.
Suddenly about halfway the page the columns are not put side by
side but
below each other!
Can you give an example that shows the problem?
Aditya
I ran the next code on the Live Context site and it gave me first
column on the first page and second
, or taking public transit...but I dream.
can you try: ...
I ran this ruby script (on Linux):
def locatedlocaltree
tree = `kpsewhich --expand-path $TEXMFLOCAL`.chomp rescue nil
unless tree FileTest.directory?(tree) then
tree = `kpsewhich --expand-path $TEXMF`.chomp rescue
thought I
had avoided this issue on my previous laptop, which ran Debian
testing/unstable and got reincarnated as an Ubuntu laptop. And I had
fixed it, by installing the 'lmodern' package. But Ubuntu lmodern is
v0.92, at least as of Ubuntu 6.06, and Debian unstable uses v1.00,
which
$@)
According to the bash man entry:
@ Expands to the positional parameters, starting from one. When
the expansion occurs within double quotes, each parameter
expands to a separate word. That is, $@ is equivalent to $1
$2 ...
So if you ran
) Ack, it's the dreaded lmodern problem. I thought I
had avoided this issue on my previous laptop, which ran Debian
testing/unstable and got reincarnated as an Ubuntu laptop. And I had
fixed it, by installing the 'lmodern' package. But Ubuntu lmodern is
v0.92, at least as of Ubuntu 6.06
The Wizard wrote:
All -
I downloaded and installed ruby 1.8.4 from sunfreeware.com, and now
I can at least use the texmfstart command. I ran texmfstart texexec
--check and get this back:
TeXExec | current distribution: web2c
TeXExec | context source date: 2006.07.14 12:08
TeXExec
Taco,
Not sure what you mean here, so I ran:
latex useemp.tex
And got:
No file useemp.aux.
emp: File useemp.1 not found:
emp: Process useemp.mp with MetaPost and then reprocess this file.
[1] (./useemp.aux) )
Output written on useemp.dvi (1 page, 400 bytes).
Transcript written on useemp.log
David Arnold wrote:
Taco,
Not sure what you mean here, so I ran:
latex useemp.tex
And got:
correct output
And now I am lost as well. Nothing useful in the mpxerr.log, I assume?
Taco
___
ntg-context mailing list
ntg-context@ntg.nl
http
, 2006, at 9:04 AM, Taco Hoekwater wrote:
David Arnold wrote:
Taco,
Not sure what you mean here, so I ran:
latex useemp.tex
And got:
correct output
And now I am lost as well. Nothing useful in the mpxerr.log, I assume?
Taco
___
ntg-context
Aditya Mahajan wrote:
setuptex just sets some system variables (TEXMF, TEXMFMAIN, TEXMFLOCAL
and so on) and modifies the PATH, so you will not get any immediate
feedback on whether it ran correctly or not. Depending on your shell
you may have to source setuptex path-to-setuptex or just
, but it was the only one that I found to be working. (An
alternative would surely be a smart copy of contents of setuptex to
.bashrc.)
Then I changed the path to point to
/usr/local/cont/tex/texmf-linux/bin and ran mktexlsr.
If setuptex was executed properly, it should already be in your PATH.
If not, other
I just ran: texexec dblarrow.tex
tmp $ texexec dblarrow.tex
TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005
fixing engine variable : pdfetex
executable : pdfetex
format : cont-en
inputfile : dblarrow
output : standard
to
/usr/local/cont/tex/texmf-linux/bin and ran mktexlsr. It followed
the new path. I ran texexec --make --alone and it seemed to be
successful. Ran mktexlsr again. Then I ran a test program in
another directory. It could not find cont-en.fmt. In fact this
file or anything similar to this file does
executable and executed it with no apparent
effect. Then I changed the path to point to
/usr/local/cont/tex/texmf-linux/bin and ran mktexlsr. It followed
the new path. I ran texexec --make --alone and it seemed to be
successful.
Just a guess: since you used the --alone switch, is there a path
directory. I made the
the setuptex file executable and executed it with no apparent
effect. Then I changed the path to point to
/usr/local/cont/tex/texmf-linux/bin and ran mktexlsr. It followed
the new path. I ran texexec --make --alone and it seemed to be
successful.
setuptex just sets some
of unpredictable side effects (apart from bugs - i just ran out of mem
again)
figure [num1] . [num2] . [num3]
should come out as
[num3] . [num2] . [num1] erugif
depending on when an otp decides that it should stop we get something else In
any case, the num snippets needs to be otp'd in order
are generated from a previous run
(from your testing). That is, if you purge all temporary files and
rerun texexec, do you still get the correct output?
No, impossible since I ran the file for the first time. And yes, I
deleted everything and rerun and it was OK again.
If not, what magic setting do you
the first post I ran updmap-sys, and then suddenly the dvi
file is as expected; but with the pdf option I get something unexpected:
instead of blank for accented letters (when I posted first) there are now
sometimes other characters than those I type (I'll send the pdf file if it
can help).
Thanks
text and you use ec or
texnansi in cont-sys.tex, the problem is not encoding-related.
...
It can help if you send the output messages of texexec...
Jean Magnan de Bornier a écrit :
(just a viewer for dvi files, does it matter?)
Well, since the first post I ran updmap-sys, and then suddenly
] A. Aamport},
title = {The {\it Gnats\/} and Gnus Document Preparation System},
journal = {\mbox{G-Animal's} Journal},
year = 1986,
}
and it ran without any trouble.
Cheers, Taco
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl
you put the file
It's in chap/1/ (along with the eps figure)
- where did you run it
I ran 'texexec onebook' in the ./ directory.
Running the component works fine (if I cd to its directory first),
because abc-1.eps is easy to find.
-Sanjoy
`Never underestimate the evil of which men of power
, uninstalled it. I verified that
texmfstart.exe is in the path and ran texmfstart newtexexec --mptex
and get the same error.
2. check that texexec is a synonym (for example texexec.bat under
windows or an executable) for running texmfstart [new]texexec
I did check that. texexec is a synonym
terribly, fundamentally wrong with format generation in
newtexexec. I just dlded the latest version and ran
texmfstart newtexexec --make --all
That is absolutely bizarre! :(
So I also just downloaded the latest, just now, but I have no such
problem (sorry). I have run
$ texmfstart newtexexec
terribly, fundamentally wrong with format generation in
newtexexec. I just dlded the latest version and ran
texmfstart newtexexec --make --all
from within the directory where the format files should be written.
After completion, I double-checked, and I did not get a new version
or format file. I
901 - 1000 of 1192 matches
Mail list logo
