From: Sebastian Rahtz (sebastian.rahtz@computing-services.oxford.ac.uk)
Date: Wed Jan 08 2003 - 04:03:20 PST
> Any chance we can use common names for processing instructions?
maybe. currently I'd say something like
<?xmltex \pdfcatalog { /ViewerPreferences << /FitWindow true >>} ?>
(untested!), ie we have a TeX primitive to add things to
the PDF catalog. Having a PI pdfcatalog might do, so
one could say
<?pdfcatalog /ViewerPreferences << /FitWindow true >> ?>
But I realize the link style thing is harder, as it is
set per link. so I end up calling a TeX command as follows:
\pdfstartlink
attr{%
/Border[\@pdfborder]%
/H\@pdfhighlight
/C[\@filebordercolor]%
}%
user {%
/Subtype/Link%
/A<<%
/F(#2)%
/S/GoToR%
\ifHy@newwindow /NewWindow true \fi
\ifx\\#3\\%
/D[0 \@pdfstartview]%
\else
/D(#3)%
\fi
>>%
}%
where things like bordercolor and style are TeX macros
which have been set somewhere. I'm not sure how to generalize
this so that it could be portable. But I'm sure you'll
want all this in XEP sooner rather than later, eg setting a
link to force opening a new window.
we wont even talk about PDF forms :-}
-- Sebastian Rahtz <sebastian.rahtz@computing-services.oxford.ac.uk> OUCS ------------------- (*) To unsubscribe, send a message with words 'unsubscribe xep-support' in the body of the message to majordomo@renderx.com from the address you are subscribed from. (*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/tos.html
This archive was generated by hypermail 2.1.5 : Wed Jan 08 2003 - 05:01:17 PST