From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Rendering differences between PDF viewers
Date: Tue, 17 Apr 2012 10:05:45 +0200 [thread overview]
Message-ID: <CAG5iGsAV5_4ft5Z4nMZQEQs+wFiGK6guHsx2229gutNEU+Qm7g@mail.gmail.com> (raw)
In-Reply-To: <4F8D1ED2.8080209@wxs.nl>
On Tue, Apr 17, 2012 at 9:42 AM, Hans Hagen <pragma@wxs.nl> wrote:
> I use acrobat (prof) as reference viewer from the editor and okular (kde
> windows version) on a second screen as handy constantly open one; I tried a
> few more but stuck to these two.
For MFLua I need to show 2 pages with thousand of MP points and look
on how the curves of the glyph join together.
With ctrl-r and magnification of 6400% AdobeReader is the only one
that is able to show the pdf without need to take an italian coffe at
every refresh.
When I need to typeset black&white or not-critical-colors document,
emacs+xpdf+ two_rows_of_workspace_in_gnome is ok --- no need another
monitor: the bottom row has the editor, the top rows has the viewer.
Maybe a wide 16:9 screen and the latest Emacs (which can render a pdf
into a buffer) are also ok: just split an emacs windows vertically in
two, left side is the editor, right side the viewer. I use the shell
buffer, so another split is needed.
Moving between buffers is not agile but the advantage is to minimize
the use of the mouse.
Anyway with a laptop it's not a problem to have another monitor, and
I use this configuration if I'm under Windows,especially with the
sumatra pdf or the ReaderX.
For all the rest (critical colors, interactive features, flash into
pdf..) the latest AcrobatProfessional is a must.
--
luigi
___________________________________________________________________________________
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:[~2012-04-17 8:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 6:00 Kip Warner
2012-04-15 9:07 ` Mojca Miklavec
2012-04-16 23:43 ` Kip Warner
2012-04-15 16:00 ` Hans Hagen
2012-04-16 23:44 ` Kip Warner
2012-04-17 6:54 ` Hans Hagen
2012-04-17 6:57 ` Kip Warner
2012-04-17 9:53 ` Peter Rolf
2012-04-17 10:12 ` Hans Hagen
2012-04-17 10:48 ` Peter Rolf
2012-04-18 0:49 ` Kip Warner
2012-04-18 6:47 ` Martin Schröder
2012-04-18 7:19 ` luigi scarso
2012-04-18 10:58 ` Martin Schröder
2012-04-19 18:26 ` Hans Hagen
2012-04-18 22:54 ` Kip Warner
2012-04-18 7:38 ` Hans Hagen
2012-04-18 11:12 ` Peter Rolf
2012-04-19 18:25 ` Hans Hagen
2012-04-20 7:50 ` Peter Rolf
2012-04-24 12:42 ` Hans Hagen
2012-04-24 13:37 ` Peter Rolf
2012-04-25 16:08 ` Peter Rolf
2012-04-24 23:34 ` Kip Warner
2012-04-28 15:52 ` Peter Rolf
2012-04-28 18:25 ` Kip Warner
2012-04-18 22:58 ` Kip Warner
2012-04-18 0:26 ` Kip Warner
2012-04-17 7:12 ` Alan BRASLAU
2012-04-17 7:31 ` luigi scarso
2012-04-17 7:42 ` Hans Hagen
2012-04-17 8:05 ` luigi scarso [this message]
2012-04-18 0:24 ` Kip Warner
2012-04-17 18:57 ` Kip Warner
[not found] ` <CAPm68ZimT3cbuhwqTgG+OXXiA_RHaA2snOT05rO-J_iWjodCQA@mail.gmail.com>
2012-04-18 0:21 ` Kip Warner
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=CAG5iGsAV5_4ft5Z4nMZQEQs+wFiGK6guHsx2229gutNEU+Qm7g@mail.gmail.com \
--to=luigi.scarso@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).