From: rudolf.sykora@gmail.com (Rudolf Sykora)
Subject: [9fans] p9p troff/ps problem, comparison with heirloom
Date: Fri, 11 Nov 2011 19:38:56 +0100 [thread overview]
Message-ID: <CAOEdRO39Bdh7+X0XA+hhX1ipa0mE39vROjSoF2rxi0M8uSLkpQ@mail.gmail.com> (raw)
In-Reply-To: <CAOEdRO2GLwvQqYMk4OQ+nqJ2pLM51DqaGaBNJf=9n+Qn7r3aLQ@mail.gmail.com>
> The problems I have described exist in plan9port and heirloom
> software. I haven't yet tried to what extent it also applies to plan9
> proper. And it seems you are suggesting some changes to the latter
> software.
As I have tried, I really don't see any of the mentioned problems when
using my plan9 machine directly; I only see the problems in the p9p
and heirloom troff.
Further, when I take the directory /sys/lib/postscript/font from plan9
and copy it to (replace with it) the contents of p9p's
$PLAN9/postscript/font I get a result quite similar to the previously
shown output of the heirloom suite, i.e., everything is present,
however the square-root sign is wrongly placed.
If you know any reason why the square-root symbol is ok on p9 and
wrong on p9p (or also how to get it right), please tell...
Thank you,
Ruda
PS.: The story shows that even when using Times Roman, some (quite
usual) letters (like em-dash, dagger,...) are taken from Lucida Sans.
This isn't particularly nice.
next prev parent reply other threads:[~2011-11-11 18:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOEdRO1pfX6XwACtt7NXw1UMcnNuzJ3egzD899c_qZDi6+mBBA@mail.gmail.c>
2011-11-11 15:56 ` erik quanstrom
2011-11-11 16:33 ` Rudolf Sykora
[not found] ` <CAOEdRO2GLwvQqYMk4OQ+nqJ2pLM51DqaGaBNJf=9n+Qn7r3aLQ@mail.gmail.com>
2011-11-11 18:38 ` Rudolf Sykora [this message]
2011-11-11 19:06 ` Rudolf Sykora
2011-11-11 20:02 ` Gorka Guardiola
2011-11-12 20:11 ` Rudolf Sykora
2011-11-19 16:50 ` Rudolf Sykora
[not found] ` <CAOEdRO3Gg7=rap_kUXPdO0jMjfSFebBpNGyCYz+9S5Tki2vnjA@mail.gmail.c>
2011-11-11 17:30 ` erik quanstrom
2011-11-11 10:11 Rudolf Sykora
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=CAOEdRO39Bdh7+X0XA+hhX1ipa0mE39vROjSoF2rxi0M8uSLkpQ@mail.gmail.com \
--to=rudolf.sykora@gmail.com \
/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).