ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Christoph Reller <christoph.reller@gmail.com>
To: ntg-context <ntg-context@ntg.nl>
Subject: Reference links with focus=standard
Date: Fri, 13 Apr 2018 13:10:11 +0200	[thread overview]
Message-ID: <CAO8LnPFsMpwJWR8xu9dnocLSvkoER=BSGRfdhjGJbmJx8snD1w@mail.gmail.com> (raw)

On Fri, 13 Apr 2018 10:45:39 +0100,  Lawrence Bell
<lawrence.matthew.bell@gmail.com> wrote:
> On 13/04/18 07:31, Henri Menke wrote:
>>
>> On Fri, 2018-04-13 at 08:13 +0200, Christoph Reller wrote:
>>>
>>> Please, Hans, I kindly ask you to reconsider. I am aware of your
>>> opinion and reasoning about this issue. But I believe that for many of
>>> us users, today's PDFs need to be both, interactive *and* printable.
>>>
>>> If there is any way I can help or motivate you, then please tell me ;-)
>>>
>> The best way to motivate Hans to implement something you need, is by
>> implementing it yourself and sending him updated core files.
>> Works for me every time ;-)
>>

Well, thank you for this hint Henry, but that works only for those who
can afford the time :-/

>
> Dear Christoph,
>
> I take it from your reply that fixing this problem with interactivity
> would likely cause some trouble with the printability? And therefore,
> it's staying as it is to prioritize printability? That's understandable,
> but a bit frustrating, since I still don't have any clue what the actual
> problem is. Could you possibly explain in some more detail or point me
> to a relevant thread?
>
> Kind regards,
>
> Lawrence
>

Dear Lawrence,

(Sorry for changing to bottom posting style.)

This issue is not about a trade-off between print-ability and
inter-activeness. If I understand Hans' position correctly, then at
least part of his reasoning is the following (please correct me if I'm
wrong): It is easy to produce two versions of a document from one
common source, one version for print and one for the screen. The
former needs no interactive links and the latter should best be viewed
fullscreen, i.e., without scrolling, in which case focus=standard is
unnecessary. While I largely agree with this approach, many of the
ConTeXt users (including myself) are not in a position to decide how
their documents should be published. I believe that many of today's
PDF documents still are meant to be both, viewed on screen and
printed. And it's only for this scenario that focus=standard makes
sense.

Kind regards,

Christoph
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

                 reply	other threads:[~2018-04-13 11:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAO8LnPFsMpwJWR8xu9dnocLSvkoER=BSGRfdhjGJbmJx8snD1w@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).