From: Christoph Reller <christoph.reller@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: two issues with interactive hyperlinks (please comment)
Date: Tue, 23 Feb 2016 14:30:25 +0000 [thread overview]
Message-ID: <CAO8LnPHTpiApKo=1ZNaP2w9r-A5kwX-c9+Aoft14_+Ted-KjOQ@mail.gmail.com> (raw)
In-Reply-To: <mailman.1.1456225201.14598.ntg-context@ntg.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2415 bytes --]
Hi Hans,
First and foremost: Thank you for uploading the Beta! This solves the
problem I have reported with \reference and focus=standard:
https://www.mail-archive.com/ntg-context%40ntg.nl/msg79620.html
On Tue, Feb 23, 2016 at 12:00 PM Hans Hagen <pragma@wxs.nl> wrote:
>
> On 2/23/2016 12:21 AM, Pablo Rodriguez wrote:
>
> > I think that (futhermore not being a default) ConTeXt should implemente
> > what is an ISO standard nowadays.
>
> well, i have been quite active in implementing what pdf provided and
> constantly had to adapt to what acrobat finally implemented (often the
> standard was ahead) and
>
...
>
I agree with you and Pablo: the ISO standard is what counts. And I believe
that named destinations, their use, and viewer behavior is described there
clearly.
... so one handicap for me is that i won't make test docs for it
>
I will try to provide minimal examples that I believe are so common that
the viewer behavior should be clear.
...
> > And sorry, not being the default, why is wrong reading pages in fit to
> > width mode?
>
> that one still has to make sure that there is a reasonable view area (so
> that one sees what went and comes) ... i'm not sure how you handle it
> but esp jumping from page to page in a fit width mode is quite annoying;
> fit width actually makes sense when one makes each chapter (or section)
> into one long page and i actually played with it but i found no viewer
> capable to keep the same scale each page
>
I believe that many people have to make compromises, e.g., cannot afford
the time or money to produce both a screen version and a print version of a
document. I believe that the fit-width mode is a good compromise - as long
as it is viewed in "continuous" viewing mode.
...
> > Is there anything that I can do to help? I’m especially interested in
> > this feature.
>
> small few page examples with predictable positioning and predictable
> spacing (btw, footnotes will always be sort of a pain as they are
> rendered in special ways, but footnotes should be forbidden anyway; if
> a doc is also for screen endnotes are way better)
>
I agree with you about footnotes. And, as mentioned above, I will try to
come up with decent example documents. There are still cases in my
documents that don't work and i will try to minimize these.
Thanks again for your effort!
Christoph
[-- Attachment #1.2: Type: text/html, Size: 3475 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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-23 14:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1456225201.14598.ntg-context@ntg.nl>
2016-02-23 11:49 ` right to left direction for itemize columns Jeong Dal
2016-02-23 14:01 ` Mohammad Hossein Bateni
2016-02-23 14:41 ` Hans Hagen
2016-02-23 14:30 ` Christoph Reller [this message]
2016-02-23 22:24 ` two issues with interactive hyperlinks (please comment) Alan BRASLAU
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
2016-02-22 23:32 ` Pablo Rodriguez
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='CAO8LnPHTpiApKo=1ZNaP2w9r-A5kwX-c9+Aoft14_+Ted-KjOQ@mail.gmail.com' \
--to=christoph.reller@gmail.com \
--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).