From: pop <asd@asd.com>
Subject: Re: dvipdf vs buildt-in converter to pdf??
Date: Sat, 15 Jul 2006 08:36:04 +0200 [thread overview]
Message-ID: <e9a2ci$2a6$1@news.net.uni-c.dk> (raw)
In-Reply-To: 87y7uvwvfg.fsf@tiger.rapttech.com.au
Tim X wrote:
> "pop" <asd@asd.com> writes:
>
>> Emacs does not use 'dvipdf' when it converts dvi files to pdf.
>>
>> I prefer using 'dvipdf' because I only need to have an .eps version of
>> the images I would like to include in my .tex files.
>>
>> Why does emacs not use 'dvipdf' and is there any flaws to this converter
>> compared to the one emacs use??
>>
>
> Not enough information to provide a concise answer. For example, are
> you using auctex mode to create your documents?
I use auctex. If I use latex built-in 'pdflatex' I need to have my pictures
in a .pdf format. But if I just want to see the dvi output I need to have
them in .eps. So far I have had both a .pdf version and a .eps version of
the pictures and included them like:
\begin{center}
\includegraphics[width=10cm]{pic1}
\end{center}
where pic1.pdf and pic1.eps are located in the same dir as my .tex file.
But now I just found out that if I use dvipdf instead of pdflatex I don't
need to have the .pdf versions of my pictures, which saves me for a lot of
work.
Therefore I would like to know what the difference is between using 'dvipdf'
and 'pdflatex' (besides from the obvious advantage of only using .eps
files).
next prev parent reply other threads:[~2006-07-15 6:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 13:41 dvipdf vs buildt-in converter to pdf?? pop
2006-07-15 0:42 ` Tim X
2006-07-15 6:36 ` pop [this message]
2006-07-15 9:05 ` Peter Dyballa
[not found] ` <mailman.4108.1152954322.9609.help-gnu-emacs@gnu.org>
2006-07-15 9:16 ` Ralf Angeli
2006-07-15 9:17 ` David Kastrup
2006-07-15 10:47 ` Leon
2006-07-15 11:37 ` Peter Dyballa
[not found] ` <mailman.4111.1152960463.9609.help-gnu-emacs@gnu.org>
2006-07-15 11:41 ` David Kastrup
2006-07-15 15:23 ` Tim X
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='e9a2ci$2a6$1@news.net.uni-c.dk' \
--to=asd@asd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).