cygwin latex problem: latex.exe points to pdfetex.exe and not to tex.exe , why?

cygwin latex problem: latex.exe points to pdfetex.exe and not to tex.exe , why?

Post by Nasser Abb » Thu, 14 Jul 2005 15:03:22


hi;

I think my PC is possessed with some spirit that is playing tricks on
me.

2 days ago I made complete new fresh installation of cygwin 1.5.18
(latest) which includes complete tex installation. I always select to
install everything.

now, when I run the command latex, it invokes pdfetex instead:

-----------------------
$ which latex
/usr/bin/latex

$ ls -l /usr/bin/latex
lrwxrwxrwx 1 win Users 11 Jul 11 23:33 /usr/bin/latex -> pdfetex.exe
---------------------------

when I go to the earlier cygwin installation (I copied that to the
side before), I see it was pointing to tex.exe instead:

-----------------------
$ cd /cygdrive/c/cygwin.BAD/bin

$ ls -l latex
lrwxrwxrwx 1 win Users 7 Aug 6 2004 *** -> tex.exe
-------------------------

The only problem I see now is that when build the .ps document, the
fonts look really bad. (and it takes much longer to convert .tex to
.dvi)

However, when I convert the .ps file to pdf using ps2pdf, the fonts in
the pdf document looks good.

This is how I currently build things

$ cat build.sh
latex mim
latex mim
dvips mim -o mim.ps
ps2pdf mim.ps mim.pdf

The file mim.ps contain bad looking fonts now (thet are not as sharp
as before).

My question is: why did *** installation decide to point ***
command to pdfetex.exe when before it was pointing to tex.exe?

I could actually forget about building the .PS file anyway, it is so
much larger than the PDF file, and Iam not sure .PS is needed anyway
since a .pdf file exist and is much smaller. Currently I build it just
to convert it to .pdf.

The strange thing is that pdfetex does not generate .pdf file, only
.dvi file? In addition, now since *** points to pdfetex, compiling
the .tex file takes much longer time than before.


$ which tex
/usr/bin/tex
$ tex -v
TeX 3.141592 (Web2C 7.5.4)
kpathsea version 3.5.4
Copyright (C) 1997-2004 D.E. Knuth.
Kpathsea is copyright (C) 1997-2004 Free Software Foundation, Inc.
There is NO warranty. Redistribution of this software is
covered by the terms of both the TeX copyright and
the GNU General Public License.
For more information about these matters, see the files
named COPYING and the TeX source.
Primary author of TeX: D.E. Knuth.
Kpathsea written by Karl Berry and others.

$ which latex
/usr/bin/latex
$ *** -v
pdfeTeX 3.141592-1.21a-2.2 (Web2C 7.5.4)
kpathsea version 3.5.4
Copyright (C) 1997-2004 Peter Breitenlohner (eTeX)/Han The Thanh
(pdfTeX).
Kpathsea is copyright (C) 1997-2004 Free Software Foundation, Inc.
There is NO warranty. Redistribution of this software is
covered by the terms of both the pdfeTeX copyright and
the GNU General Public License.
For more information about these matters, see the files
named COPYING and the pdfeTeX source.
Primary author of pdfeTeX: Peter Breitenlohner (eTeX)/Han The Thanh
(pdfTeX).
Kpathsea written by Karl Berry and others.


thanks,
Nasser
 
 
 

cygwin latex problem: latex.exe points to pdfetex.exe and not to tex.exe , why?

Post by Ulrike Fis » Thu, 14 Jul 2005 20:05:00

"Nasser Abbasi" < XXXX@XXXXX.COM > schrieb:


pdfetex is able to make pdf and dvi (one only needs to set \pdfoutput
to 0 or 1. Nowadays most TeX-Systems use pdfetex to make dvi.




--
Ulrike Fischer
e-mail: zuszlich meinen Vornamen vor dem @ einfen.
e-mail: add my first name between the news and the @.

 
 
 

cygwin latex problem: latex.exe points to pdfetex.exe and not to tex.exe , why?

Post by Ralf Stubn » Thu, 14 Jul 2005 20:47:00

"Nasser Abbasi" < XXXX@XXXXX.COM > writes:


,----[ TETEXDOC.dvi ]
| 4.6 pdfetex: the new default TEX engine
|
| teTEX uses pdfetex for all formats except ``good-old'' tex. So, if you
| run latex, the underlying engine will be pdfetex. Some (broken) TEX
| macros assume that pdfTEX is running in PDF generation mode if they
| detect primitives that pdfTEX has introduced (e.g. \pdfoutput). This is
| wrong, since pdfTEX can also be used (and is used) to gen- erate DVI
| output. A reliable way of detecting PDF output mode is implemented in
| ifpdf.sty which works for plain TEX as well as LATEX.
`----

cheerio
ralf
 
 
 

cygwin latex problem: latex.exe points to pdfetex.exe and not to tex.exe , why?

Post by Nasser Abb » Thu, 14 Jul 2005 21:43:21


I did not know about \pdfoutput=1

Now when I did this, *** is looking for .png files for each graphic
file I have. The graphic files I have are in .eps format. pdf wants
.png format. So *** failes now.

This is below an example of how I include the graphic files ( I do not
use the file extension)

\usepackage{graphicx}
...

\includegraphics{image}

So, I guess I must generate .ps and then convert it to pdf using
ps2pdf, right? otherwise I have to convert all the .ps files I have to
png. which do you think would produce better output?

thanks
Nasser
 
 
 

cygwin latex problem: latex.exe points to pdfetex.exe and not to tex.exe , why?

Post by Ulrike Fis » Thu, 14 Jul 2005 22:54:55

"Nasser Abbasi" < XXXX@XXXXX.COM > schrieb:



When you set pdfoutput=1, pdftex makes pdf, it is now "pdfLaTeX" and
pdfLaTeX can't use eps.

When you set pdfoutput=0, pdftex makes dvi, it is now "LaTeX" and ***
can use eps (or better dvips can use it) but not png or pdf.


I would convert the .eps to .pdf with eps2pdf. Then the output should
be the same. The pdfLaTeX-way is shorter than the LaTeX+dvips+ps2pdf
way. But if you use pstricks the second way is often easier to handle.


--
Ulrike Fischer
e-mail: zuszlich meinen Vornamen vor dem @ einfen.
e-mail: add my first name between the news and the @.
 
 
 

cygwin latex problem: latex.exe points to pdfetex.exe and not to tex.exe , why?

Post by Heiko Ober » Fri, 15 Jul 2005 00:08:20


You don't need to know it. Your TeX distribution should be configured
in such a way that
*** --> calls pdfeTeX compiler in DVI mode (\pdfoutput=0)
pdflatex --> calls pdfeTeX compiler in PDF mode (\pdfoutput=1)

Yours sincerely
Heiko < XXXX@XXXXX.COM >