ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Paul Isambert <zappathustra@free.fr>
Subject: Re: Using \pdfnames and friends.
Date: Tue, 25 Jan 2011 17:26:20 +0100	[thread overview]
Message-ID: <4D3EF9AC.3030701@wxs.nl> (raw)
In-Reply-To: <4D3ED1BF.5080801@free.fr>

On 25-1-2011 2:35, Paul Isambert wrote:
> Answering myself: I should use:
>
> \ctxlua{lpdf.addtonames("EmbeddedFiles", lpdf.reference(22))
> \ctxlua{lpdf.addtocatalog("PageMode", lpdf.constant("UseOutlines"))}
>
> (Apparently I can't do that directly with \pdfbackendsetname/catalog,
> the second argument is taken as a string.)
> I hope that's the correct answer and not a hack.

There are mechanisms for embedding files, like

   backends.codeinjections.embedfile(filename)

However, a nametree is not constructed (as with forms these are not 
mandate, but with forms they are better be there due to initialization). 
Anyhow, I added this now:

local function flushembeddedfiles()
     if next(filestreams) then
         local e = pdfarray()
         for name, reference in next, filestreams do
             if reference then
                 e[#e+1] = pdfstring(name)
                 e[#e+1] = reference -- already a reference
             else
                 -- we can issue a message
             end
         end
 
lpdf.addtonames("EmbeddedFiles",pdfreference(pdfflushobject(pdfdictionary{ 
Names = e })))
     end
end

lpdf.registerdocumentfinalizer(flushembeddedfiles,"embeddedfiles")

As with most of these things, it's best to use the interface and not 
push things in the file directly as it might render existing 
functionality ineffective. Examples are color related resources.

In a similar fashion Pagemode is not to be set directly. There is

   \setupinteractionscreen

for this (with a low level lua setupcanvas variant). As some of the 
parameters influence each other they are dealt with at another moment. 
Also, some of the parameters are ignored or overloaded when a chosen 
pdf/x standard has rules that concern them.

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
___________________________________________________________________________________


  parent reply	other threads:[~2011-01-25 16:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25 11:29 Paul Isambert
2011-01-25 13:35 ` Paul Isambert
2011-01-25 13:38   ` luigi scarso
2011-01-25 14:52     ` Paul Isambert
2011-01-25 15:15       ` Aditya Mahajan
2011-01-25 16:07       ` luigi scarso
2011-01-25 16:26   ` Hans Hagen [this message]
2011-01-25 20:32     ` Paul Isambert

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=4D3EF9AC.3030701@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    --cc=zappathustra@free.fr \
    /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).