ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan BRASLAU <alan.braslau@cea.fr>
To: Christoph Reller <christoph.reller@gmail.com>
Cc: ntg-context@ntg.nl
Subject: Re: two issues with interactive hyperlinks (please comment)
Date: Tue, 23 Feb 2016 15:24:12 -0700	[thread overview]
Message-ID: <20160223152412.2e580769@cea.fr> (raw)
In-Reply-To: <CAO8LnPHTpiApKo=1ZNaP2w9r-A5kwX-c9+Aoft14_+Ted-KjOQ@mail.gmail.com>

On Tue, 23 Feb 2016 14:30:25 +0000
Christoph Reller <christoph.reller@gmail.com> wrote:

>  (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.

As a reader (of bound books), I very much prefer footnotes (at the
bottom of the printed page) to endnotes. I actually read footnotes so
shuffling back and forth between sections of the book can be a pain.

Of course, this is not the case for on-screen readers.

Reading on a screen one can have two approaches: either it is like
reading a book (in which case I like to use dual mode on a large screen)
or else one is reading a screen document in a continuous scroll mode
(in which case pages including headers and footers make no sense).
Using this second approach, footnotes must be used as endnotes, but
not in the first approach.

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:24 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 ` two issues with interactive hyperlinks (please comment) Christoph Reller
2016-02-23 22:24   ` Alan BRASLAU [this message]
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=20160223152412.2e580769@cea.fr \
    --to=alan.braslau@cea.fr \
    --cc=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).