From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] docfonts problem
Date: Sun, 12 Sep 2010 14:17:10 -0400 [thread overview]
Message-ID: <AANLkTi=uDgt9pMx1rWb4_Wj=0eBdua19pmHhDc-DOn5N@mail.gmail.com> (raw)
In-Reply-To: <24b6a153e443aa375714b80fe48294de@swcp.com>
> Now for the problem behind all this. I am basically required to use troff
> for formatting the iwp9 paper submissions. I have asked repeatedly for the
> a TeX macros, or the source for an acceptable macro.ms equivalents. All of
> these requests have been greeted with silence because someone, and I would
> have to guess who, is discouraging the use of TeX for these submissions.
> Frankly troff has been a pain, and I do not use it for anything else, and
> will not except for necessary plan9 related documentation. Thanks for the
> work around BTW, but next time I rebuild plan9port it will be blown away
> unless I add these dance steps to the ebuilds. See the chicken ant the egg
> problem?
It's just not that hard to use the iwp9 macros with plan9port.
They work fine, and if you put .FP luxisans at the top of your
ms file you can get a nice-looking B&H-designed sans serif font too.
And then when you submit the source to them you or they
can delete that one line. It's easy.
Or you can run 9vx pointed at a real Plan 9 ISO image
and run Plan 9 in all its glory. That's easy too.
You're making things a lot harder than they need to be.
Russ
next prev parent reply other threads:[~2010-09-12 18:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 16:14 erik quanstrom
2010-09-11 22:10 ` Russ Cox
2010-09-12 5:03 ` EBo
2010-09-12 15:42 ` Russ Cox
2010-09-12 16:57 ` EBo
2010-09-12 18:17 ` Russ Cox [this message]
2010-09-12 18:40 ` EBo
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='AANLkTi=uDgt9pMx1rWb4_Wj=0eBdua19pmHhDc-DOn5N@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).