[NTG-context] Using \pdfnames and friends.
Hello,
I'm trying to use \pdfnames with MkIV, but I can see from the sources
that it's a no-op and should be replaced with \pdfbackendsetname.
So I use \pdfbackendsetname{EmbeddedFiles}{22 0 R}, trying to achieve
the same thing as \pdfnames{/EmbeddedFiles 22 0 R}, but 22 0 R is
surrounded by parentheses, as if it were a PDF string, so that I end up
with the useless /EmbeddedFiles (22 0 R).
Similarly, \pdfbackendsetcatalog{PageMode}{/UseOutlines} produces
/PageMode (/UseOutlines).
What am I doing wrong?
Best,
Paul
___
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
___
Re: [NTG-context] Using \pdfnames and friends.
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.
Best,
Paul
___
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
___
Re: [NTG-context] Using \pdfnames and friends.
Thanks Luigi (don't know why your answer doesn't show up above.)
But now I have another question. When I do:
\ctxlua{lpdf.addtoinfo(Title, My work)}
The Title field in the Info dictionary is correctly set, but not in the
xml Metadata, which uses jobname instead. Hence, Acrobat shows jobname
as the document's title (even though other viewers, which don't
understand metadata, display My work).
So: how do I set the title correctly both in Info and Metadata?
Best,
Paul
___
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
___
Re: [NTG-context] Using \pdfnames and friends.
Le 25/01/2011 17:26, Hans Hagen a écrit :
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.
Thank you very much for your answers, Luigi, Aditya, and Hans.
Actually, I'm finishing up a package with PDF support. As usual, I
wanted it to work with all formats. I suspected it wouldn't be very
interesting for ConTeXt, since you probably have all you need, but I
thought if it works for plain it'll work for ConTeXt. I also suspected
conflicts might arise, though, and what Hans says convinces me I'd
better drop support for ConTeXt, because at best it'll just add an
interface on top of the existing one, and at worst it'll break things up
(not to mention the extra coding for me). I'll provide the wrapper file
for ConTeXt anyway, because who knows, but I won't make any special
effort nor cause trouble.
Thanks again,
Paul
___
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
___
Re: [NTG-context] [texhax] Choosing TeX um ... stuff
Selon Philip Taylor (Webmaster, Ret'd) p.tay...@rhul.ac.uk: Peter Davis wrote: 2. True or False: plain TeX and LaTeX(2e) are warhorses ... been around for decades, quirks well known, lots of documentation, etc. Yes, except that while Plain TeX has more-or-less remained static (modulo essential bug fixes by Don), LaTeX2e has continued to evolve. I have heard rumours that this particular evolutionary branch may have come to an end, but I have no definite knowledge of this. And plain TeX doesn't have a lot of documentation. Anyway there isn't much to document. Basically using plain TeX means you need a very good knowledge of the engine, and you'll write tons of macros (in a way there are no plain TeX users, only users of personal formats based on plain). 3. True or False: ConTeXt is newer, with a lot of built-in features, but still changing quite a bit from build to build. Context is a L O T newer : it has many devotees, but is still something of an outside to mainstream TeX usage. Philip, plain TeX isn't exactly mainstream anymore, and ConTeXt probably beats it on this point. And ConTeXt is already more than 15 years old, so it's not so new, although it does keep moving. Paul ___ 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 ___
