Gnus development mailing list
 help / color / mirror / Atom feed
From: Jost.Krieger+list@ruhr-uni-bochum.de
Cc: ding@gnus.org
Subject: Re: New PostScript manuals generated
Date: 16 Jun 1997 10:09:38 +0200	[thread overview]
Message-ID: <s5k67vft1dp.fsf@hp138.rz.ruhr-uni-bochum.de> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 08 Jun 1997 01:48:45 +0200

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

I've printed (and kinda proofmarked) the A4 edition (again).
Here are my (global) findings:

> I changed the font size to 11pt -- 10pt seemed too small for Bembo and
> 12pt too big.  I use Futura 10pt (which is the same size as Bembo
> 11pt, for some reason) for variable names (etc.) and Adobe Courier
> 11pt for the code examples (etc.).  I was recommended IBM's Courier,
> but we didn't have that one.

The fonts look nice, except that in some places you use an italic font
that's way too large (like in the A4 version on page 205:
*backend*-status-string).

> I've also added Luis' hand-drawn gnu herds for the chapter pages.  I
> blurred them some, since they weren't scanned in that high a
> resolution.  For the back cover I used something I generated
> accidentally -- a washed-out section of the herd pictured with an
> obscenely high smooth factor.  A nice accident, I think.

The chapter gnus are nice, except the Appendices have chapter number
10 and nine gnus in front :-) Should that be an inverted Gnu ?

> So the manual now kinda looks like I want it to look, I think.  Unless
> I change my mind, of course.

My 2 Pfennige:

I think the page gnu should be farther away from the text body, like
under the page number.

The outer margin is quite large. Could we put something sensible in
there (like Notes and Warnings)? Oops. There *are* gnus there, just
not that many. Could those be centered in the margin, or at least be
symmetric for left and right pages ?

Your reference algorithm is broken. External references are horrible,
but rare.  Internal references point to the place before the chapter
or section, typically on the wrong page. If you use LaTeX's reference
mechanism, make sure the "label"s are generated after the chapter
heading. (Could we have a look at your production tools ?)

Contentswise:

I miss something about customize.

The FAQ is so old, it smells. Like

"The latest (and greatest) version is 5.0.10. ..."

There is a *much* newer version online that mentions Quassia instead
of insisting "September gnus is the alpha version ..."



Then there are the typos ... coming later, as always.

Jost

BTW: Thank you for the nice manual, I really like it, even if it doesn't sound so :-)

-- 
Jost Krieger, Postmaster, Rechenzentrum der Ruhr-Universitaet Bochum
Jost.Krieger@ruhr-uni-bochum.de


  reply	other threads:[~1997-06-16  8:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-06-07 23:48 Lars Magne Ingebrigtsen
1997-06-16  8:09 ` Jost.Krieger+list [this message]
1997-06-16 13:10   ` Justin Sheehy
1997-06-16 15:04     ` Hrvoje Niksic
     [not found]     ` <wk4tay1r7i.fsf@peorth.gweep.net>
1997-06-17 16:00       ` Lars Magne Ingebrigtsen
1997-06-17 22:51         ` Steven L Baur
1997-06-20 10:01           ` Per Abrahamsen
1997-06-20 13:20             ` Hrvoje Niksic
1997-06-20 19:33             ` Steven L Baur
1997-06-18  8:09         ` Hrvoje Niksic
1997-06-18 12:06           ` Lars Magne Ingebrigtsen
1997-06-18 19:20             ` Richard Coleman
1997-06-18 20:10             ` Jason R Mastaler
1997-06-18  7:41       ` Steinar Bang
1997-06-18 12:33         ` Robert Bihlmeyer
1997-06-24 10:26           ` Steinar Bang
1997-06-17 15:55   ` Lars Magne Ingebrigtsen
1997-06-19 14:36     ` Jost Krieger
1997-06-20 22:13       ` Lars Magne Ingebrigtsen

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=s5k67vft1dp.fsf@hp138.rz.ruhr-uni-bochum.de \
    --to=jost.krieger+list@ruhr-uni-bochum.de \
    --cc=ding@gnus.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).