[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: facing pages in PDF browsers
From: |
Karl Berry |
Subject: |
Re: facing pages in PDF browsers |
Date: |
Wed, 26 Jun 2013 22:44:14 GMT |
from what you say I deduce that you don't use Adobe Reader,
That is true. Not in many years.
Nevertheless, I'm afraid your logic escapes me. As far as I can see,
your description is that AR currently starts in one-page mode on Texinfo
documents, and with the change it will start in two-page mode (and full
screen?!), with no way for users to override it. If I used AR, I would
be very unhappy with such a change; indeed, my world would become
unusable if my PDF viewer decided to suddenly occupy twice as much
screen real estate, let alone the whole thing.
Whereas in the current situation of texinfo.tex, people can manually
switch to facing pages if they want. At least I remember doing so in
early Acrobat versions, before there was any other PDF version.
Since the texinfo.tex behavior has been like this forever, and no one
before you has said anything, I can't believe it's all that big of a
problem ...
What do others think?
Sure, but "@setchapternewpage odd" makes only sense for two-page
layouts.
Yes, but just because there is an even/odd layout does not mean one
wants to preview two pages at once. I don't. It takes up too much of
the screen.
The further point is that the vast majority of existing Texinfo
documents use @setchapternewpage odd, even though they don't "need" to.
I can't ignore that reality. So making the change for HEADINGSdouble is
tantamount to making the change (nearly) globally.
If one-page-mode is preferred, it has to be stated in the texinfo
config file anyway because otherwise you get unnecessary blank pages
when you send the PDF file to a printer.
That is true. People put up with the wasted blank pages, or delete the
setchapternewpage, or whatever. And few people print PDF files anyway,
compared to viewing them.
k