From: Ralf Angeli <dev.null@caeruleus.net>
Subject: Re: dvipdf vs buildt-in converter to pdf??
Date: Sat, 15 Jul 2006 11:16:43 +0200 [thread overview]
Message-ID: <44b8b27a$0$15786$14726298@news.sunsite.dk> (raw)
In-Reply-To: mailman.4108.1152954322.9609.help-gnu-emacs@gnu.org
* Peter Dyballa (2006-07-15) writes:
> Am 15.07.2006 um 08:36 schrieb pop:
>
>> 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:
>
> Have you thought of a PDF viewer as substitute for xdvi? There are
> free ones that work better then commercial products. When you have
> teTeX you can use texdoc as universal script to view teTeX
> documentation or as tex-dvi-view-command.
>
> IMO the route with DVI output is out-dated. PDF is the way today.
Unless you want an extraordinarily fast previewer which supports
forward and inverse search as well.
> You could try to set tex-dvi-print-command to a script that uses
> dvipdfm to convert DVI to PDF -- and in the end it should print the
> PDF file (or use tex-alt-dvi-print-command for this purpose).
>
> Or, set *tex-run-command(s) to scripts that do two things: invoking
> some *TeX engine (plain tex, latex, xetex, xelatex, slitex, ...) +
> upon success dvipdfm.
Those variables are totally unrelated to AUCTeX which the OP is using
as mentioned above.
--
Ralf
next prev parent reply other threads:[~2006-07-15 9:16 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
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 [this message]
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='44b8b27a$0$15786$14726298@news.sunsite.dk' \
--to=dev.null@caeruleus.net \
--cc=angeli@caeruleus.net \
/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).