From: "Andrej Borsenkow" <borsenkow.msk@sni.de>
To: <mason@primenet.com.au>, <zsh-workers@math.gatech.edu>
Subject: RE: print texinfo doubleside?
Date: Tue, 22 Dec 1998 15:00:22 +0300 [thread overview]
Message-ID: <000f01be2da2$a71a8ec0$21c9ca95@mowp.siemens.ru> (raw)
In-Reply-To: <slrn77u2qn.jjs.mason@coral.primenet.com.au>
>
> ``@afourpaper'' is there too. And what size paper are you trying to
> print on?
A4. The margins are O.K. for this side, assuming I print on one side only
:-) Odd pages have large left margins for binding and relatively small right
margins. The problem is, on even pages these right margins fall on binding
side. Basically, double side formatting should exchange margines for even
pages.
Thanks to all who cared to answer :-)
... after some digging in texinfo.tex ...
- texinfo.tex has support for double side :-)
- '@setchapternewpage odd' only makes chapters start on odd pages
and modifies page numbers layout
- '@afourpaper' sets page dimensions to A4 page but does not care
about double side story. I even suspect, dimesions are wrong.
I remember something about that in README of texinfo, that they
deliberately set page width for letter size even when printing on
A4.
- additional macro '@afourlatex' does exactly what I want !
It appears, that you still need afourpaper to set some defaults properly. I
added afourlatex just after afourpaper in zsh.texi and got almost perfect
result (the margins are about 3-4mm off) with much better margins overall -
now right text side does not stick to right paper side.
Now, if I new how to make this automatically ...
/andrej
prev parent reply other threads:[~1998-12-22 12:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-21 15:30 Andrej Borsenkow
1998-12-21 16:00 ` Bruce Stephens
1998-12-21 17:36 ` Andrej Borsenkow
1998-12-21 19:10 ` Phil Pennock
1998-12-22 3:00 ` Geoff Wing
1998-12-22 12:00 ` Andrej Borsenkow [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='000f01be2da2$a71a8ec0$21c9ca95@mowp.siemens.ru' \
--to=borsenkow.msk@sni.de \
--cc=mason@primenet.com.au \
--cc=zsh-workers@math.gatech.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).