Re: The name of the pdfmark mark

[K. H. Man]

Hi all,

Ludovic Courtès wrote:
> On Wed, Sep 17, 2003 at 01:02:09AM +0800, K. H. Man wrote:
> > So, there are three possibilities:
> > * One is in the direction of a generalized meta-information 
> > interface, @DocInfo; [snip]
> > * Alternatively, the interface can be made to be explicitly clear 
> > that it is for a single back end or specification, @PDFMark.
> > * Finally, do it purely in Lout using some @address@hidden@Yield 
> > magic.
>
> From my understanding, bullets 1 and 3 are pretty much the same idea: do
> the things in Lout. [snip]

Bullet 1 is implemented in C while bullet 3 is entirely in Lout.
AFAIK, bullet 1 is really necessary because Lout performs
additional processing on @Link* tags in order to turn them into
pdfmark destinations. It's also not that easy to build a tree in
the form required by pdfmark. Here is an example of a bookmark
tree for those interested in the problem of implementation:

[ /Dest /LOUT... /Title (Bookmark Test) /OUT pdfmark
[ /Count -3 /Dest /LOUT... /Title (Page 1) /OUT pdfmark
     [ /Dest /LOUT... /Title (Page 2) /OUT pdfmark
     [ /Dest /LOUT... /Title (Page 3) /OUT pdfmark
     [ /Dest /LOUT... /Title (Page 4) /OUT pdfmark
[ /Count 3 /Dest /LOUT... /Title (Page 5) /OUT pdfmark
     [ /Dest /LOUT... /Title (Page 6) /OUT pdfmark
     [ /Count -1 /Dest /LOUT... /Title (Page 7) /OUT pdfmark
        [ /Dest /LOUT... /Title (Page 8) /OUT pdfmark
     [ /Dest /LOUT... /Title (Page 9) /OUT pdfmark
[ /Dest /LOUT... /Title (Page 10) /OUT pdfmark
[/PageMode/UseOutlines/Page 1/View[/FitH 846]/DOCVIEW pdfmark

You can generate bookmarks by pasting something like this into the
PostScript output from Lout, then distilling. This will give you
the following outline on an Acrobat Reader:

 [] Bookmark Test
+[] Page 1
-[] Page 5
 |-[] Page 6
 +-[] Page 7
 \-[] Page 9
 [] Page 10

"/LOUT..." are named destinations, and the names are produced by
massaging the given tags. E.g. /LOUT19_4244_pre_hadj_3.
Non-alphanumerics are converted to underscores in the back end.
The structure of the outline is implied in the /Count key pairs
and the order of the pdfmarks.

So, as Michael says, "practically unfeasible". It's a real
nightmare for people used to imperative programming... ;-)

--
Cheers,
Kein-Hong Man (esq.)
Kuala Lumpur, Malaysia