Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: New PostScript manuals generated
Date: 17 Jun 1997 17:55:47 +0200	[thread overview]
Message-ID: <m2wwntjkak.fsf@proletcult.slip.ifi.uio.no> (raw)
In-Reply-To: Jost.Krieger+list@ruhr-uni-bochum.de's message of 16 Jun 1997 10:09:38 +0200

Jost.Krieger+list@ruhr-uni-bochum.de writes:

> 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).

Yeah, that looked ugly.  It's not an italic font -- it's a slanted
sans serif thing.  I've no idea why it ended up bigger than the
surrounding text.  I've now made it smaller explicitly.

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

I'm going to drop two of the chapters ("Composing Messages" and "The
Article Buffer" -- they'll be moved to "Various".  They're rather
small.) and add a new "Introduction to Gnus" chapter that'll explain
the main points without using any big words, and lots of screenshots.
And Custom screenshots.

That should give us 9 chapters, if one can count "Appendices" as a
chapter.  

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

Ah, yes, that might be nice.  I'll give it a try and see how it
looks. 

> 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 ?

Yup.

There'll also be toolbar icons (if somebody would make those large
versions, that is.  Pleeeeeze!) and X-Faces and smilies and picons and
stuff in the margins.  Where they belong, of course.

The screenshots will also occupty the margins as well as the body.
That is, they'll be as wide as that line on the top of the page.

> 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.

I run LaTeX on the output thrice, but I guess that isn't enough.  :-)

First I run LaTeX to get the indices and stuff, and then it's run to
include the table of contents, and then one would think the third run
should get the page references right, but perhaps the length of the
page references skew things, so that I'll have to run it again to get
the page references right.

> (Could we have a look at your production tools ?)

<URL:http://www.ifi.uio.no/~larsi/rgnus/texi/> is where it all
happens. 

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen


  parent reply	other threads:[~1997-06-17 15:55 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
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 [this message]
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=m2wwntjkak.fsf@proletcult.slip.ifi.uio.no \
    --to=larsi@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).