From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: two issues with interactive hyperlinks (please comment)
Date: Wed, 24 Feb 2016 10:25:09 +0100 [thread overview]
Message-ID: <56CD76F5.10407@gmx.es> (raw)
In-Reply-To: <20160223150720.3dcae9df@cea.fr>
On 02/23/2016 11:07 PM, Alan BRASLAU wrote:
> Just speculating, could one distribute a PDF that would be like a book
> with many parts? I know that Hans is not a fan of part, but I wonder
> how this is handled? I doubt that any viewers handle prefixed page
> numbers properly. I just tried looking at a document were pagenumbers
> are reset way=bychapter and evince at least starts each chapter with a
> page number=1 in its navigation bar.
>
> How would readers (people) deal with a PDF structured as:
> Part I - print/A4
> Part II - print/letter
> Part III - screen
> ?
Well, I don’t dare to post such a PDF document on the net. Most people
won’t be able to even know how to handle that in years. And they
probably don’t have to.
As a matter of fact, thanks to
http://wiki.contextgarden.net/PDF_Print_Options, I only have to press
Ctrl+P and Enter using Acrobat > 9.
In all copyshops, I have to say: please, don’t touch page scaling when
is set to None. And to avoid a too rational (or too rude) reasoning, I
show them the Advanced tab in the document properties from Acrobat
(Ctrl+D
[https://cloud.githubusercontent.com/assets/209434/12230087/1167cab0-b84e-11e5-81c5-6d6798d9244f.png,
sorry it’s in German]).
Then I also explain that this is read from the document and that it
won’t change the default from Adobe.
If they do that for a living, I guess that your proposal would be too
complex for most of the users.
Of course, PDF experts will know how to handle that. But they are a
minority. (I cannot consider myself an expert, because I don’t fully
understand the PDF specification [I cannot code :-(].)
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-02-24 9:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-21 19:54 Pablo Rodriguez
2016-02-22 19:08 ` Hans Hagen
2016-02-22 23:21 ` Pablo Rodriguez
2016-02-23 8:33 ` Hans Hagen
2016-02-24 9:01 ` Pablo Rodriguez
2016-02-24 9:50 ` Wolfgang Schuster
2016-02-25 6:55 ` Pablo Rodriguez
2016-02-25 18:19 ` Hans Hagen
2016-02-25 6:51 ` Pablo Rodriguez
2016-02-25 10:20 ` Hans Hagen
2016-02-22 19:13 ` Hans Hagen
2016-02-22 20:40 ` Alan BRASLAU
2016-02-22 22:54 ` Martin Schröder
2016-02-23 22:07 ` Alan BRASLAU
2016-02-24 9:25 ` Pablo Rodriguez [this message]
2016-02-22 23:32 ` Pablo Rodriguez
[not found] <mailman.1.1456225201.14598.ntg-context@ntg.nl>
2016-02-23 14:30 ` Christoph Reller
2016-02-23 22:24 ` Alan BRASLAU
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=56CD76F5.10407@gmx.es \
--to=oinos@gmx.es \
--cc=ntg-context@ntg.nl \
/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).