From: Kenji Okamoto <okamoto@granite.cias.osakafu-u.ac.jp>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ghostscript
Date: Mon, 1 Mar 2004 13:36:49 +0900 [thread overview]
Message-ID: <7cc63f70971c9a63a8d3810b269c7a25@granite.cias.osakafu-u.ac.jp> (raw)
In-Reply-To: <b103f44ec731f19fb840eb04418cd6eb@yourdomain.dom>
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
AFPL Ghostscript-8.13 can be find on our web site:
http://basalt.cias.osakafu-u.ac.jp/plan9/gs-8.13.tgz
http://basalt.cias.osakafu-u.ac.jp/plan9/gs-data.tgz.
Why they were removed from sources? Because none is maintaining
it anymore. As you know Russ has been doing it, but he is a graduate
student at MIT which means he must be very busy for his own Ph.D
thema etc. Furthermore, maintaining Ghostscript is not any creative
work which is neccessary to those students. We need Ghostscript for
every day use of Plan 9, and that's all. Ghostscript is not in the main
stream of Plan 9 design way, it uses UTF-8, but Ghostscript(8.x) uses
CID-keyd character etc. To maintain Ghostscript is easy enough even
for like me, which don't need Russ, Dave, Jim, Sape, and of course Rob.
I think that's the reason.
Kenji
[-- Attachment #2: Type: message/rfc822, Size: 2356 bytes --]
From: dbailey27@ameritech.net
To: 9fans@cse.psu.edu
Subject: [9fans] ghostscript
Date: Sat, 28 Feb 2004 11:08:58 -0500
Message-ID: <b103f44ec731f19fb840eb04418cd6eb@yourdomain.dom>
Morning, all
Does anyone know what happened to the 8.x ghostscript
stuff on the labs fs? I'm looking to upgrade so I can view files
from unicode.org. The ghostscript/. directory on the Labs 9fs
is empty, and there is no gs package in contrib or extra.
Don (north_)
next prev parent reply other threads:[~2004-03-01 4:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 16:08 dbailey27
2004-03-01 4:36 ` Kenji Okamoto [this message]
2004-03-01 7:32 ` Kenji Okamoto
2006-01-16 14:13 [9fans] Ghostscript Brantley Coile
2006-01-16 16:16 ` Rob Pike
2006-01-16 16:44 ` Brantley Coile
2006-01-17 2:00 ` Russ Cox
2006-01-17 13:08 ` Brantley Coile
2006-01-17 14:13 ` Charles Forsyth
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=7cc63f70971c9a63a8d3810b269c7a25@granite.cias.osakafu-u.ac.jp \
--to=okamoto@granite.cias.osakafu-u.ac.jp \
--cc=9fans@cse.psu.edu \
/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).