From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tim X Newsgroups: gmane.emacs.help Subject: Re: dvipdf vs buildt-in converter to pdf?? Date: Sun, 16 Jul 2006 01:23:56 +1000 Organization: Posted via Supernews, http://www.supernews.com Message-ID: <87odvqsxgz.fsf@tiger.rapttech.com.au> References: <87y7uvwvfg.fsf@tiger.rapttech.com.au> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1152978043 5524 80.91.229.2 (15 Jul 2006 15:40:43 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 15 Jul 2006 15:40:43 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Jul 15 17:40:41 2006 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1G1mFs-0002Yc-Bg for geh-help-gnu-emacs@m.gmane.org; Sat, 15 Jul 2006 17:40:32 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G1mFr-0008P2-Rw for geh-help-gnu-emacs@m.gmane.org; Sat, 15 Jul 2006 11:40:31 -0400 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!newsgate.cistron.nl!xs4all!newsfeed.bit.nl!193.201.147.81.MISMATCH!feed.xsnews.nl!feeder.xsnews.nl!138.199.65.86.MISMATCH!sn-xt-ams-06!sn-xt-ams-05!sn-ams!sn-feed-ams-03!sn-post-ams-02!sn-post-sjc-02!sn-post-sjc-01!supernews.com!corp.supernews.com!not-for-mail Original-Newsgroups: gnu.emacs.help User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.50 (gnu/linux) Cancel-Lock: sha1:PGTIszJdvjolMCzKnYUzx4b4T3E= Original-X-Complaints-To: abuse@supernews.com Original-Lines: 65 Original-Xref: shelby.stanford.edu gnu.emacs.help:140357 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:35982 Archived-At: pop writes: > Tim X wrote: > >> "pop" 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). I guess we have different modes of operation. This is what I do 1. Create the image files - either .eps, .gif, .png etc 2. Create my Latex doc with emacs and auctex 3. Use command similar to yours to embed image 4. Hit C-c C-c to run latex and get a dvi file 5. View with C-c C-c again (using xdvi). All images are visible (at least if they are .eps, can't remember about .gif and .png). 6. If more work required, go back to 2 and repeat until final document looks correct 7. Run dvipdf on dvi file to produce pdf version This works fine for me using tetex as my TeX/LaTeX implementation. I don't understand why the additional process of creating a PDF file just to view it - thats the last step I do prior to printing or sending to someone else. I have no problems viewing files with a fair few images - but on average, the documents I'm working on are around the 20-40 page size and rarely exceed 100 pages. Often, if I'm going to print the document and I am using a postscript or specific device/printer, I may use one of the more specific dvi* as I think you get a more reliable result and it seems to make no sense to go through an additional processing/translation when you are only going to print the file. Tim -- tcross (at) rapttech dot com dot au