From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] anyone attempted to build ghostscript recently?
Date: Fri, 3 May 2013 18:20:39 +0200 [thread overview]
Message-ID: <20130503162039.GA557@polynum.com> (raw)
In-Reply-To: <64e57b5cc889082953a7f022f534b833@quintile.net>
On Fri, May 03, 2013 at 03:18:40PM +0100, Steve Simon wrote:
> Thinking of tackeling ghostscript again but failed at the first hurdle,
> it needs autotools to build...
Plan A, create a SmallScript borrowing the rasterizing routines of
METAFONT and not aiming to be a full PostScript interpreter.
Plan B, get rid of PostScript altogether and use TeX and METAFONT and/or
fonts available with the glyphes, and render directly from dvi to pdf,
dvi to raw (image), dvi to pcl; even using virtual fonts to render
approximately fonts not present with glyphes definition for
previsualisation, and using dvips for direct printing to real
PostScript interpreters (with embedded compliant PostScript standard
fonts).
Isn't there a sentence about "wanting a banana, and being forced to
have a Gorilla handing the banana with the whole jungle around"?
--
Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
next prev parent reply other threads:[~2013-05-03 16:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 14:18 Steve Simon
2013-05-03 14:22 ` erik quanstrom
2013-05-03 14:34 ` Kurt H Maier
2013-05-03 15:53 ` David du Colombier
2013-05-03 20:08 ` Steve Simon
2013-05-04 7:43 ` tlaronde
2013-05-03 16:20 ` tlaronde [this message]
2013-05-03 16:26 ` a
2013-05-03 16:48 ` tlaronde
2013-05-03 17:14 ` Jack Johnson
2013-05-03 17:16 ` erik quanstrom
2013-05-03 17:24 ` pmarin
2013-05-03 17:27 ` Jeff Sickel
2013-05-03 17:50 ` tlaronde
2013-05-03 18:10 ` Aram Hăvărneanu
2013-05-03 18:34 ` tlaronde
2013-05-03 18:38 ` erik quanstrom
2013-05-03 18:53 ` Jack Johnson
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=20130503162039.GA557@polynum.com \
--to=tlaronde@polynum.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).