ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: ecashin@coe.uga.edu (Ed L. Cashin)
Cc: NTG-ConTeXt <ntg-context@ntg.nl>
Subject: Re: put vector fonts in ps document?
Date: 15 Sep 1999 10:00:12 -0400	[thread overview]
Message-ID: <m3zoyol1g3.fsf@kali.coe.uga.edu> (raw)
In-Reply-To: Tobias Burnus's message of "Tue, 14 Sep 1999 22:09:40 +0200"

(This was a thread from the pdftex mailing list.)

Tobias Burnus <burnus@gmx.de> writes:

> Hallo "Ed L. Cashin" wrote:
> > 
> > If I make a pdf document with pdftex, I get the scalable outline
> > (vector) fonts, so it looks great.  If I do tex -> dvi -> ps -> pdf, I
> > get bitmap (raster) fonts, and the pdf looks relatively bad.
>
> That depends on the methode.
> 
> > Is it possible to do it so that I get the scalable vector fonts in the
> > ps document such that when I run ps2pdf (a ghostscript wrapper) I get
> > nice-looking pdf output?
>
> Well you need to include the fonts (as type-1) in your ps file (try
> e.g. dvips -Pcmz) and you need a Ghostscript > 5.89. Current is 5.93
> (+ fix), which lacks in Outline/bookmark support and article support
> (using pdfmarks), but works reasonably well. The disadvantage with
> this Ghostscript is (a) it is beta and (b) it needs to be
> compiled. But a new version (6.0) is due end of September (30), so
> you may want to wait. PDFTeX is able to include the Type-1 fonts,
> but with the new Ghostscript, you can also use figures with embedded
> fonts.

That's interesting to know.  I will probably wait, since my past
experiences with installing ghostscript from the source were... 
spotted with discomfort.

Thanks for the information.

-- 
--Ed Cashin							
  ecashin@coe.uga.edu


      reply	other threads:[~1999-09-15 14:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3906ay28a.fsf@kali.coe.uga.edu>
1999-09-14 20:09 ` Tobias Burnus
1999-09-15 14:00   ` Ed L. Cashin [this message]

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=m3zoyol1g3.fsf@kali.coe.uga.edu \
    --to=ecashin@coe.uga.edu \
    --cc=ntg-context@ntg.nl \
    /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 NNTP newsgroup(s).