9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: 9fans@9fans.net
Subject: Re: [9fans] TeX - Plan 9 model
Date: Wed, 12 Mar 2008 12:18:32 -0400	[thread overview]
Message-ID: <20080312161943.A07651E8C59@holo.morphisms.net> (raw)
In-Reply-To: <6EBE4BD8-A3B6-4EBD-9876-7FC924A1558B@corpus-callosum.com>

> I'd highly recommend going the pdftex route instead
> http://www.tug.org/applications/pdftex/)
> .  Pdftex generates much more compatible PDF files that the dvips
> route--aka, dvips output prints to paper fine, looks horrid on most
> PDF viewers.

Whether the files generated by dvips look okay in PDF viewers
depends on whether they embed bitmap or vector versions of
the fonts.

On Plan 9, if you run

	dvips file.dvi >file.ps
	ps2pdf file.ps file.pdf

then you will get a PDF that looks as good on screen as
anything generated by pdftex.

The PostScript file.ps itself may not be too portable, because it
will refer to PostScript versions of the TeX fonts, which are
installed as part of the Plan 9 TeX package but not so
common elsewhere.  To embed full copies of the fonts
in the output, creating a larger PostScript file, use

	dvips -Ppsfonts file.dvi >file.ps

If you want to embed crappy-looking bitmap fonts
that could take a long time to generate (the default
on most Unix TeX installations), you can use

	dvips -Pbitmapfonts file.dvi >file.ps

All this isn't to say that a pdftex port wouldn't be nice;
it's just not necessary to create screen-readable PDFs.

Of course, even with the default Unix TeX installations,
you can avoid this problem by using PostScript fonts
like Times-Roman instead of the Computer Modern fonts.

Russ



  parent reply	other threads:[~2008-03-12 16:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11 17:28 lucio
2008-03-11 18:03 ` erik quanstrom
2008-03-11 18:29   ` lucio
2008-03-11 18:58     ` erik quanstrom
2008-03-12  4:40       ` lucio
2008-03-12 11:47         ` Robert Raschke
2008-03-12 12:09           ` lucio
2008-03-12 15:02             ` Jeff Sickel
2008-03-12 16:04               ` Hongzheng Wang
2008-03-12 16:18               ` Russ Cox [this message]
2008-03-12 18:17               ` Joel C. Salomon
2008-03-13 22:12                 ` Paweł Lasek
2008-03-14  3:22                   ` Hongzheng Wang
2008-03-14  4:51                   ` lucio
2008-03-12 10:20       ` lucio

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=20080312161943.A07651E8C59@holo.morphisms.net \
    --to=rsc@swtch.com \
    --cc=9fans@9fans.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 NNTP newsgroup(s).