all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
Cc: help-gnu-emacs@gnu.org
Subject: Re: dvipdf vs buildt-in converter to pdf??
Date: Sat, 15 Jul 2006 13:37:18 +0200	[thread overview]
Message-ID: <A3258682-74D6-47B7-A195-5E4C83AAE039@Web.DE> (raw)
In-Reply-To: <m2vepzxhz0.fsf@sl392.st-edmunds.cam.ac.uk>


Am 15.07.2006 um 12:47 schrieb Leon:

> Which DVI viewer are you using?

I am on Mac OS X which has no "native" DVI viewer. Xdvi runs, of  
course, as an X11 client. The "Aqua clients" TeXniscope or TeXShop  
(the best PDF viewer you can find) convert DVI to PDF via dvipdfmx or  
dvipdfm (teTeX supports MAP files automatically). TeXShop "sees" that  
the source (at least PDF) has changed and automatically updates. I've  
set TeXShop as viewer application for a few TeX document formats in  
texdoc. So it's texdoc that is used from AUCTeX to display everything  
for which GNU Emacs does not suffice.

There is another problem with dvipdfm (besides it lacks support in  
AUCTeX): it's dead (but not complete; or do you see for example  
support for TTF or OTF fonts?). Development happens in dvipdfmx (and  
xdvipdfmx for XeTeX output), which also supports CJK text (maybe more).

--
Greetings

   Pete

Behold the warranty ... the bold print giveth and the fine print  
taketh away.

  reply	other threads:[~2006-07-15 11:37 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
2006-07-15  9:17       ` David Kastrup
2006-07-15 10:47         ` Leon
2006-07-15 11:37           ` Peter Dyballa [this message]
     [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=A3258682-74D6-47B7-A195-5E4C83AAE039@Web.DE \
    --to=peter_dyballa@web.de \
    --cc=help-gnu-emacs@gnu.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.