From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Overriding pdfview
Date: Thu, 27 Jun 2013 10:13:50 +0200 [thread overview]
Message-ID: <51CBF43E.2000903@wxs.nl> (raw)
In-Reply-To: <CAG5iGsAkhrPe6G3OdNW1iSg6R92vqKEe6=_G4gp2OcBeO=3p1A@mail.gmail.com>
On 6/27/2013 9:35 AM, luigi scarso wrote:
>
>
>
> On Thu, Jun 27, 2013 at 4:21 AM, <hwitloc@gmail.com
> <mailto:hwitloc@gmail.com>> wrote:
>
>
> I likewise find the Sumatr pdf viewer better. Besides the benefits
> already mentioned, it also has the proper quality of being
> non-intrusive. Adobe readers are quite happy to bloat your memory
> and take control or otherwise intrude on your system's normal
> operations.
>
> I don't use Adobe's reader at all.
>
> Adobe Reader/Acrobat is the reference: is you see and print a pdf with
> Acrobat under Windows 8 you are on the right side.
> Otherwise you are on the wrong side.
> For javascript, if the pdf works under Acrobat under Windows 8 it's ok,
> otherwise no.
>
> If Reader/Acrobat doesn't complain the question if the pdf is valid or
> not is not important for and end user (ok, it's not true for pdf/a).
indeed, it's the final reference
> Until now I have found the sumatrapdf is (very) good, but it cannot be
> used as reference.
but okay and convenient for edit/view cycles (my second choice is
okular, also available for windows)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2013-06-27 8:13 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 13:53 Bill Meahan
2013-06-26 14:20 ` luigi scarso
2013-06-26 15:17 ` Bill Meahan
2013-06-26 16:11 ` luigi scarso
2013-06-26 19:29 ` Hans Hagen
2013-06-26 20:22 ` luigi scarso
2013-06-26 20:36 ` Siep Kroonenberg
2013-06-26 21:09 ` luigi scarso
2013-06-26 20:50 ` Philipp Gesang
2013-06-26 20:58 ` Hans Hagen
2013-06-26 21:16 ` luigi scarso
2013-06-26 21:34 ` Philipp Gesang
2013-06-27 15:15 ` Sietse Brouwer
2013-06-27 15:44 ` Mica Semrick
2013-06-27 17:25 ` Aditya Mahajan
2013-06-27 19:39 ` Arthur Reutenauer
2013-06-27 18:18 ` Hans Hagen
2013-06-26 21:27 ` Bill Meahan
2013-06-26 22:24 ` Hans Hagen
2013-06-26 23:02 ` Bill Meahan
2013-06-27 7:21 ` luigi scarso
2013-06-27 2:21 ` hwitloc
2013-06-27 7:35 ` luigi scarso
2013-06-27 8:13 ` Hans Hagen [this message]
[not found] <mailman.1497.1372359752.2084.ntg-context@ntg.nl>
2013-06-27 19:43 ` Pavneet Arora
2013-06-27 22:44 ` luigi scarso
2013-06-27 23:46 ` Sietse Brouwer
2013-06-27 23:53 ` Gareth Jones
2013-06-28 8:56 ` Keith J. Schultz
2013-06-28 10:34 ` Hans Hagen
2013-06-28 13:16 ` Keith J. Schultz
2013-07-01 2:31 ` David Rogers
2013-06-28 8:28 ` Hans Hagen
2013-06-28 2:29 ` Arthur Reutenauer
2013-06-28 6:23 ` luigi scarso
2013-06-28 8:29 Keith J. Schultz
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=51CBF43E.2000903@wxs.nl \
--to=pragma@wxs.nl \
--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).