From: Humm <hummsmith42@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] 9front Programmer's Manual
Date: Sat, 7 Aug 2021 13:37:27 +0200 [thread overview]
Message-ID: <YQ5wd19dkEfRuTQp@beryllium.local> (raw)
In-Reply-To: <41714DC4-F599-485D-9E19-8282E0E4AA33@stanleylieber.com>
> what specific changes did you have in mind, and what is the purpose
> of the exercise?
I had in mind either fixing and updating the means of building big
volumes containing the documents and the man pages or removing them
completely.
Building those big volumes probably wouldn’t actually be too useful,
since it’s easy to read everything on-line. It might help with
reading stuff with, say, an e-book reader (as sirjofri mentioned), but
even then stuff like title pages, a ToC, prefaces, and maybe even the
permuted index wouldn’t have any purpose.
If the manual is to be printed, for whatever reason (like people
finding it easier to read stuff on paper), as you currently do with
one half of it, I like to have the means of building the print edition
(a generic one, without colorful covers and custom page size
adjustments) in the system.
As it is, we have a build system for big volumes somewhat usable for
print, but it refers to Plan 9 4E on the title pages and in the first
preface, doesn’t work well, and produces bad results (mix of troff
default 8.5*11i and ms default 8*11i) without easy means to customize
the page layout and type. Whatever the outcome is, I don’t want to
keep something bad like that.
Updating the documents or adding new ones is not a primary concern of
mine here and can be done either way.
What I have done is create a working version of that, my
/n/tcp!9p.zone!9991/humm/^(print.pdf docs) . No big changes of
content, just the name “9front Programmer’s Manual,” better page
numbering, and easier control of parameters of the final result.
--
Humm
prev parent reply other threads:[~2021-08-07 11:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 12:08 Humm
2021-08-06 13:37 ` qwx
2021-08-06 15:00 ` Humm
2021-08-06 13:49 ` qwx
2021-08-06 15:05 ` ori
2021-08-06 19:30 ` Stuart Morrow
2021-08-07 4:52 ` sirjofri
2021-08-20 11:26 ` Stuart Morrow
2021-08-06 15:06 ` Stanley Lieber
2021-08-06 19:34 ` Stuart Morrow
2021-08-07 11:37 ` Humm [this message]
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=YQ5wd19dkEfRuTQp@beryllium.local \
--to=hummsmith42@gmail.com \
--cc=9front@9front.org \
/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).