From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Support for Optional Content Groups
Date: Thu, 03 Jul 2014 19:54:27 +0200 [thread overview]
Message-ID: <53B598D3.4050202@wxs.nl> (raw)
In-Reply-To: <1111725488.140309.1404402933094.JavaMail.zimbra@pentandra.com>
[-- Attachment #1: Type: text/plain, Size: 1901 bytes --]
On 7/3/2014 5:55 PM, Chris Chapman wrote:
> I am new to ConTeXt (coming from LaTeX), and am really impressed. Great work!
>
> I am working on a document that has layers that I want to be screen-only, similar in approach to this:
> http://tex.stackexchange.com/questions/167846/implementing-full-page-screen-only-print-only-in-pdf
>
> I am assuming that Optional Content Groups would be the best way to do this. How would I set something up like this in ConTeXt/LuaTeX? I know I could make a screen-only version and a print version of the output pdf, but I want to have my cake and eat it too ;)
(also see wolfgangs mail)
I tried this in acrobat:
\defineviewerlayer[visibleandprint] [printable=yes,state=start]
\defineviewerlayer[visibleandnotprint] [printable=no, state=start]
\defineviewerlayer[notvisibleandprint] [printable=yes,state=stop]
\defineviewerlayer[notvisibleandnotprint][printable=no, state=stop]
\setupinteraction[state=start]
\starttext
\startviewerlayer[visibleandprint] visible and print
\stopviewerlayer \blank
\startviewerlayer[visibleandnotprint] visible and not print
\stopviewerlayer \blank
\startviewerlayer[notvisibleandprint] not visible and print
\stopviewerlayer \blank
\startviewerlayer[notvisibleandnotprint] not visible and not print
\stopviewerlayer \blank
\stoptext
and found out that we need an extra piece of info for acrobat to be
happy. I'll upload a beta with that addition.
I wonder if other viewers handle layers well.
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
-----------------------------------------------------------------
[-- Attachment #2: print-001.pdf --]
[-- Type: application/x-pdf, Size: 6475 bytes --]
[-- Attachment #3: 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:[~2014-07-03 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <947663393.140271.1404401839314.JavaMail.zimbra@pentandra.com>
2014-07-03 15:55 ` Chris Chapman
2014-07-03 16:33 ` Wolfgang Schuster
2014-07-03 17:54 ` Hans Hagen [this message]
2014-07-03 18:08 ` Chris Chapman
2016-05-22 9:22 ` Meer, Hans van der
2016-05-22 9:36 ` Framing multiline equations L.S.-Soc&Gam
2016-05-22 15:56 ` Hans Hagen
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=53B598D3.4050202@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).