unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: emacs-devel@gnu.org
Subject: Re: doc-view.el --- View PDF/PostScript/DVI files in Emacs
Date: Sun, 26 Aug 2007 22:38:47 +0200	[thread overview]
Message-ID: <858x7yav54.fsf@lola.goethe.zz> (raw)
In-Reply-To: <87d4xalhqu.fsf@baldur.tsdh.de> (Tassilo Horn's message of "Sun\, 26 Aug 2007 12\:20\:25 +0200")

Tassilo Horn <tassilo@member.fsf.org> writes:

> David Kastrup <dak@gnu.org> writes:
>
> Hi David,
>
>>> I changed doc-view.el so that it uses plain ghostscript (plus dvipdfm
>>> for DVI files) which gives good results and is about ten times faster
>>> than with ImageMagick's convert.
>>>
>>> The only downside is that I don't know how to cut off the margins.
>>> Those waste a lot of buffer space when displaying the image.
>>> converts -trim option was very nice for that cause.  Do you know how
>>> one can do that with ghostview?
>>
>> Well, that is one of the things done in preview-latex.  Do you have
>> the bounding box information for your images (preview-latex takes them
>> from TeX usually)?
>
> No, how should I get it?  I only have PDF/PS or DVI files with no
> sources at all.

I am afraid I can't figure out what you are trying to achieve.  PDF/PS
and DVI files are primarily page-oriented formats.  It does not make
sense to display every page with a different size.  PDF and PS files
can actually change the page format in midstream _if_ that is desired.
Autocropping will complicate the user's handling of page material.
This is different if we are talking about embedded material, graphics
and stuff.  In that case, we will be using PDF (which sets its own
page size) or EPS.  EPS files carry a bounding box comment: extracting
that and using it for setting the rendering bounding box for
Ghostscript should do the trick.

preview-extract-bb in AUCTeX's preview.el can be used for that
purpose.

> If it can be useful if everything I have is the plain document with
> no additional source or infos about included images, then I'll do
> it.
>
> So can it do that?

Can it do what?

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2007-08-26 20:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-24 11:03 doc-view.el --- View PDF/PostScript/DVI files in Emacs Tassilo Horn
2007-08-24 11:47 ` Michaël Cadilhac
2007-08-24 15:24   ` Tassilo Horn
2007-08-24 21:42     ` David Kastrup
2007-08-25 17:26       ` Tassilo Horn
2007-08-25 18:34         ` David Kastrup
2007-08-26 10:20           ` Tassilo Horn
2007-08-26 20:38             ` David Kastrup [this message]
2007-08-27  8:52               ` Tassilo Horn
2007-08-27 10:23                 ` David Kastrup
2007-08-27 14:37                   ` Tassilo Horn
2007-08-27 15:16                     ` David Kastrup
2007-08-27 20:14                       ` Tassilo Horn
2007-08-27 20:31                         ` David Kastrup
2007-08-27 20:17                     ` Stefan Monnier
2007-08-27 20:30                       ` David Kastrup
2007-08-25 20:52     ` Richard Stallman
2007-08-26 10:11       ` Tassilo Horn
2007-08-26 22:46         ` Richard Stallman

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=858x7yav54.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=tassilo@member.fsf.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 public inbox

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

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).