ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan BRASLAU <alan.braslau@cea.fr>
To: "Martin Schröder" <martin@oneiros.de>, "Hans Hagen" <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: two issues with interactive hyperlinks (please comment)
Date: Tue, 23 Feb 2016 15:07:20 -0700	[thread overview]
Message-ID: <20160223150720.3dcae9df@cea.fr> (raw)
In-Reply-To: <CAP7DCDcxezHtMc+Hai7mDO8CqQOWTRg6ckJkWJZQUGt7OozqAg@mail.gmail.com>

On Mon, 22 Feb 2016 23:54:00 +0100
Martin Schröder <martin@oneiros.de> wrote:

> 2016-02-22 21:40 GMT+01:00 Alan BRASLAU <alan.braslau@cea.fr>:
> > This makes me think: Is there some "standard" way for a PDF to
> > contain both versions?  
> 
> Adobe introduced something called "portfolios" in PDF 1.7 or later,
> but I doubt that they work with non-Adobe viewers.

Yes, I know about this non-standard extension. In fact, I struggled
recently with a PDF using portfolios that could not be read using Adobe
reader 9. The provider of the pdf insisted, and continues to insist,
that one needs Adobe "version 9 or greater" and suggests that I have a
problem with my web browser (which has nothing to do with it), and of
course that I need Adobe flash (which is true for the latest Adobe
under Windows, but this too is irrelevant).

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
?

Alan
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2016-02-23 22:07 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 [this message]
2016-02-24  9:25         ` Pablo Rodriguez
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=20160223150720.3dcae9df@cea.fr \
    --to=alan.braslau@cea.fr \
    --cc=martin@oneiros.de \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).