9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] troff and ps related
Date: Wed,  8 Jul 2009 07:27:09 -0700	[thread overview]
Message-ID: <dd6fe68a0907080727v2527e955gce1ede494ec1f2f5@mail.gmail.com> (raw)
In-Reply-To: <a560a5d00907080449t69db3725q4ce854f743debd3b@mail.gmail.com>

On Wed, Jul 8, 2009 at 4:49 AM, Rudolf Sykora<rudolf.sykora@gmail.com> wrote:
> can anybody tell me why whatever .ps about troff/eqn I print has
> misplaced lines?
> E.g. quite generally, lines that make up tables either don't touch, or
> stick out somewhere...

this is because tbl is using characters to draw lines.
it's not a great strategy.

> Also, should
> .BX something
> make a nice box around 'something' or not? Anywhere I look I see the
> top line be slightly above the side lines, it doesn't touch them.

maybe should be doesn't.  there's a reason no one uses it.
even if it worked, boxes around words are pretty heavy weight.

> Further, is there a way to view .ps files in a graceful way? Neither
> proof nor page quite work for me. There is no comparison to gv in
> linux at all, imho. It can't zoom well, if I manage to zoom in page
> (often it takes infinitely long ---again compared to gv---, often it
> ends with not enough memory; I also quite don't understand how the
> zoom should work) it is not very nice, very unclear.

you can start page with a ppi parameter: page -p 150 file.ps
i have never managed to get gs to let me change that parameter
on the fly during the gs conversation.  if you can, please do,
and then make zoom on postscript files use that mechanism.

russ


  parent reply	other threads:[~2009-07-08 14:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08 11:49 Rudolf Sykora
2009-07-08 12:13 ` erik quanstrom
2009-07-08 14:27 ` Russ Cox [this message]
2009-07-08 15:03   ` Rudolf Sykora
2009-07-08 15:29     ` Russ Cox
2009-07-09 14:53       ` Rudolf Sykora
2009-07-09 16:54         ` hiro
2009-07-09 17:59           ` yy
2009-07-08 16:08     ` Dan Cross

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=dd6fe68a0907080727v2527e955gce1ede494ec1f2f5@mail.gmail.com \
    --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).