From: "John A. Murdie" <john@cs.york.ac.uk>
To: 9fans@cse.psu.edu, john@cs.york.ac.uk
Subject: [9fans] Re: psutils et al
Date: Fri, 16 Feb 2001 10:31:15 +0000 [thread overview]
Message-ID: <E14TiAY-00019z-00@minster.cs.york.ac.uk> (raw)
"Douglas A. Gwyn" <gwyn@arl.army.mil> wrote:
>"John A. Murdie" wrote:
>> ... On Unix and Plan 9, I'd say that was probably
>> at the ditroff output level. ...
>
>Unfortunately, troff "knows" physical characteristics of the
>device when it preforms the formatting. Certainly, ditroff
>output can be manipulated by filters and device interpreters
>(e.g. there is often a "landscape" switch), but the language
>is a little too close to the hardware to expect good results.
Thanks, this is interesting. So, if I am writing an application
program for Plan 9 which requires to produce graphical output,
what document description language do I use? I think I'd probably
write pic/eqn/tbl etc. Is that your solution too? Where then
should one do any N-upping, page rotation etc that is required,
given that doing it at the PostScript level invites people similarly
to post-process bad PostScript? What should the Plan 9 solution be?
John A. Murdie
Department of Computer Science
University of York
England
next reply other threads:[~2001-02-16 10:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-16 10:31 John A. Murdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-16 11:36 John A. Murdie
2001-02-19 9:58 ` Douglas A. Gwyn
2001-02-15 17:47 nemo
2001-02-15 17:44 nemo
2001-02-15 13:28 John A. Murdie
2001-02-15 9:44 John A. Murdie
2001-02-15 9:43 John A. Murdie
2001-02-15 17:53 ` Douglas A. Gwyn
2001-02-16 9:52 ` Douglas A. Gwyn
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=E14TiAY-00019z-00@minster.cs.york.ac.uk \
--to=john@cs.york.ac.uk \
--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).