unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
Cc: help-gnu-emacs@gnu.org
Subject: Re: emacs 22 release
Date: Sat, 1 Oct 2005 16:14:07 +0200	[thread overview]
Message-ID: <e94d2de9353e661d6f85458ac7c9caeb@Web.DE> (raw)
In-Reply-To: <853bnlwi2r.fsf@obelix.seki.fr>


Am 01.10.2005 um 14:13 schrieb Sébastien Kirche:

> The key is maybe that I use those settings not to process the 
> postscript
> data  e.g. with  ghostscript but  to send  it directly  to  a 
> postscript
> printer.
>
> Maybe it is what makes the difference ?
>

How? Is there any reason why GNU Emacs should send different PS code to 
the *PostScript* buffer then to the printer queue?

I wouldn't buy a printer without PostScript, so I do not have any need 
to use gs between GNU Emacs or another application and the printer. And 
it's modern enough to be able to print € or ISO 8859-16 glyphs. It's 
CUPS that finally takes care for a good printout, being able to convert 
text to PS too?

There is just one need for gs: to view GNU Emacs' output or to convert 
this output reliably to PDF. Apple's own pstopdf in Mac OS X fails as 
does any other application when made to display this: they all first 
need to convert PS to PDF to make it display (as "Display PDF") in 
Quartz.

--
Greetings

   Pete

"Eternity is a terrible thought. I mean, where's it going to end?"
                                                    - Tom Stoppard

  reply	other threads:[~2005-10-01 14:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-28 13:04 emacs 22 release Olive
2005-09-28 14:43 ` Nurullah Akkaya
2005-09-28 15:22 ` Peter Dyballa
2005-09-28 20:35   ` Kevin Rodgers
2005-09-29 10:14     ` Peter Dyballa
     [not found]     ` <mailman.9069.1127988970.20277.help-gnu-emacs@gnu.org>
2005-09-29 21:18       ` Jason Rumney
     [not found] ` <mailman.8996.1127922118.20277.help-gnu-emacs@gnu.org>
2005-09-29  7:12   ` Jason Rumney
2005-09-29  9:25     ` Peter Dyballa
     [not found]     ` <mailman.9059.1127986983.20277.help-gnu-emacs@gnu.org>
2005-09-29 14:21       ` Johan Bockgård
2005-09-29 19:14         ` Peter Dyballa
2005-10-04  4:48       ` Stefan Monnier
2005-09-29  8:09   ` Sébastien Kirche
2005-09-29 20:43     ` Peter Dyballa
2005-09-30 22:53     ` Peter Dyballa
     [not found]     ` <mailman.9287.1128121742.20277.help-gnu-emacs@gnu.org>
2005-10-01 12:13       ` Sébastien Kirche
2005-10-01 14:14         ` Peter Dyballa [this message]
     [not found]         ` <mailman.9353.1128176131.20277.help-gnu-emacs@gnu.org>
2005-10-03 17:26           ` Sébastien Kirche
2005-10-04  3:57   ` Stefan Monnier
2005-10-04  8:59     ` Peter Dyballa
     [not found]     ` <mailman.9673.1128422429.20277.help-gnu-emacs@gnu.org>
2005-10-04 20:43       ` Harald Hanche-Olsen
2005-10-04 22:25         ` Peter Dyballa
     [not found] <mailman.8988.1127916392.20277.help-gnu-emacs@gnu.org>
2005-09-29 11:19 ` Ralf Resack

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=e94d2de9353e661d6f85458ac7c9caeb@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.
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).