blob: 0686895efca811d43491a08f1ee03710e3329aba (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
|
<PRE>
Last Modified: Dec 1 1994, 10:47
PDF (Portable Document Format) is a format defined by Adobe and
describes a page description language that supports hyperlinks. The
adobe product `distill' can create PDF documents from postscript ones
by translating the page description. In addition, it allows the
postscript file to specify the hyperlinks through a new postscript
operator, pdfmark.
This
<A HREF="http://nqcd.lanl.gov/people/tanmoy/hypertex/ghostview-1.5-hacked.tar.gz">alpha release</A>
of the changed version of ghostview is a first
attempt to make ghostview pdfmark aware. It recognizes the pdfmark
operator, and tries to cretae `hotlinks' on the display. A key click
on the link follows the link.
The companion products, the modifications to dvips by Mark Doyle and
the set of macros comprising hypertex (as described at
<A HREF="http://xxx.lanl.gov/hypertex/">xxx</A>)
facilitates the generation of these ps
files from TeX documents. The modified dvips actually uses a
postscript procedure pdfm (which translates to an appropriate call to
pdfmark if pdfm is undefined) to describe the linkage structure. As
the translation of pdfm to pdfmark is lossy, ghostview should ideally
understand pdfm directly: see the TODO list.
All keys work as in the standard release of ghostscript: except
1) any key-click inside a link follows link instead of magnifying
it.
2) b or B goes back in link history if history is non-null: goes to
previous page (default behaviour) otherwise. (delete, backspace
etc. are still bound to previous_page) does nothing on first page
if link history empty.
3) page menu has an extra entry for back which works as in (2).
Here is what it never plans to do:
1) Support SRCPAGE option of pdfmark.
2) Support pdfmarks in non-DSC structured documents.
Here is the TODO list. (can also be considered BUG list)
1) Handle pdfmarks of kinds other than /LNK (/ANNOT etc. should be
very easy) (currently ignores them)
2) Handle pdfmarks called in non-default coordinate system.
3) Handle /LNK to other documents.
4) Look at target view specification as well (currently it only looks
at target page)
5) Check if communication with ghostscript possible through means
other than the stdout.
6) Do a proper job of parsing pdfmark parameters.(easy but tedious)
7) Use the rx and ry parameters of the /Border specification of
pdfmark. (easy)
8) Support forward/backward navigation or menu-oriented navigation in
link history.
Here is the TODO list for processing pdfm (in addition to pdfmark).
1) Allow initial jump to arbitrary target.
2) Allow user specified jump to arbitrary target.
3) Take into account target coordinate.
4) Allow network URL's.
5) Make middle click open a smaller window with the target properly
centered.
</PRE>
|
