The Communications of the TEX Users Group Volume 29 ... - TUG

More documents

Recommendations

Info

$E-m: Guidelines for Future TEX Extensions - TUG$

$TUG 2001: A TEX Odyssey PROGRAM$

$LATEX Sophisticated professional typesetting for business and ...$

$TEX and Scripting Languages - TUG$

$Geometric Diversions with TEX, METAFONT and METAPOST - TUG$

$Writing Gregg Shorthand with mEtaFoNt and LATEX - TUG$

$Generating LaTeX documents through Matlab - TUG$

Ross Moore for building buttons to show and hide the pop-up images. Now when a float is encountered, the full contents of the environment is written out into a file, named according to the figure or table number, as part of a new L ATEX job which includes a preamble loading most of the same packages as in the main job. This subsidiary job is run, using L ATEX followed by dvips/ps2eps/epstopdf to get a single-page PDF with correct bounding box. The file is loaded back into the main job using \pdfrefximage within a \setbox, and its PDF object reference number is recorded for later use in placing the image on a JavaScript button field, when an appropriate \ref occurs. The object reference is also written into the .aux file as the expansion of a macro having its name derived from the figure number. This allows the reference to be used on the next run, with any \ref command that occurs before the float has been encountered, and also allows checking to see whether the reference number has changed, in which case a message is written to the .log file warning that another L ATEX run is required. Finally, the tokens for the float environment are recovered and processed normally. On subsequent L ATEX runs, the image files do not need to be rebuilt, but are loaded from the PDF images created on an earlier run. If editing of the main document source changes the order of floats, the toggle buttons may become associated with the wrong images. Simply delete those images from the current directory; the correct ones should be generated afresh on the next L ATEX run. In case the content of a float contains \ref and \eqref commands or citations, the subsidiary job that creates an image also loads a copy of the .aux file from the main job, which copy was made at the end of the previous run. It’s possible that cross-references have not fully stabilised, so simply delete any affected image; after two more runs it will have been regenerated and included. If browser software had a ‘cross-reference spyglass’ feature (as suggested in the first paragraph of this item), then not only would there be no need for the PDF to contain JavaScript coding for the extra buttons, but also there would not be doubling-up of the information contained in figure and table floats. Furthermore, such a pop-up-like feature would ‘just work’ also for cross-references to section headings, numbered equations, etc., as well as to the floats, and perhaps also for citations and ‘back-references’ from the bibliography (see Figure 7, for example). This is surely the way that such a feature ought to be implemented; ideally it should not be nec- essary for a scientific document to include explicit programming which controls how its content be displayed, but just have declarations of which browsersupplied functions are to be used. The implementation presented here is mainly to demonstrate the usefulness and practicality of such a ‘pop-up’ feature for cross-referenced material, so that browser vendors might be encouraged to incorporate a similar feature within their own publicly-available software. However, there are certainly other, simpler uses for pop-ups to show extra images that are not found elsewhere among the usual pages of a document. c. Extended use of bookmarks (see Figure 3), ... Use of bookmarks is quite common for the major sections of a document; this is automatic when using \usepackage{hyperref} with a L ATEX document. This is here extended further to creating bookmarks for definitions, Theorems, Lemmas, etc., and also for figures, tables, and some equation displays. To avoid the bookmark window becoming too cluttered, only those equations that have actually been crossreferenced within the document are given their own bookmark. 8 Having such bookmarks means that there are named destinations with the PDF at all the important places for the structure and content of the document. Furthermore these names are available in a separate file, so potentially this can be used to construct hyperlinks directly to these important places. This could be extremely useful in the context of a digital archive. For figures and tables, a meaningful string to be the textual anchor in the ‘Outline’ window is obtained as the first sentence in the caption. This is obtained by reading the caption from the .lof or .lot file and parsing to locate the first full stop (‘.’). With Theorems, Lemmas, Propositions, etc., the anchortext uses the appropriate numbering, as seen in Figure 3. The limiting of bookmarks to only those referenced is achieved by patching the \@setref internal macro to implement a ‘memory’ of referenced labels. A line is written into the .aux file; this defines a macro, with name derived from the label. The coding for placing equation numbers is patched so that \df@tag now also places an anchor, and a bookmark for this anchor when the memory indicates that the equation has been referenced—which is known on the 2 nd and subsequent L ATEX runs. 8 It can be argued that if an equation is not referenced then it doesn’t need an equation number. However, many articles have been written where the author has not followed this maxim. For creation of bookmarks, this maxim has been programmed-in. 468 TUGboat, Volume 29 (2008), No. 3 — Proceedings of the 2008 Annual Meeting
Advanced features for publishing mathematics, in PDF and on the Web Figure 3: Bookmarks: these three images, taken from different articles, illustrate various aspects of the automatically created ‘bookmarks’. These provide easy access to the important parts of the document, including front-matter as well as sections of the mathematical article itself; such as definitions, theorems, proofs, remarks and figures. The middle image shows that mathematical symbols can be used within bookmarks, while from the lower one it can be seen that a bookmark is not produced for every numbered equation, but only for those that are cross-referenced within the article itself. TUGboat, Volume 29 (2008), No. 3 — Proceedings of the 2008 Annual Meeting 469
Page 1 and 2:
The Communications of the TEX Users
Page 3 and 4:
TUG2008 Proceedings University Coll
Page 5 and 6:
TUG 2008—program Monday, July 21
Page 7 and 8:
At the reception. Around the front
Page 9 and 10:
Taco Hoekwater, inside the Beamish
Page 11 and 12:
Another, equally large, disadvantag
Page 13 and 14:
This “saves” the original \text
Page 15 and 16:
Figure 5: Macro result pushed back
Page 17 and 18:
TEXworks: Lowering the barrier to e
Page 19 and 20:
Direct and reverse synchronization
Page 21 and 22:
The TEXnical terms used to describe
Page 23 and 24:
6.2 An orthogonal implementation On
Page 25 and 26:
In fact, the text editors and the v
Page 27 and 28:
albanian greek norwegian belarusian
Page 29 and 30:
input manually, but are generated b
Page 31 and 32:
1.2 Commercially available software
Page 33 and 34:
If L ATEX can fit the snippet into
Page 35 and 36:
Pascal MetaPost, but using CWEB as
Page 37 and 38:
The TEX-Lua mix Hans Hagen Pragma A
Page 39 and 40:
\setbox0=\hbox{x}\the\wd0 In Lua we
Page 41 and 42:
start.char = uc return true end end
Page 43 and 44:
stream-based approach, this time th
Page 45 and 46:
example is support for OpenType fon
Page 47 and 48:
typesetting system is TEX [4] creat
Page 49 and 50:
13. Image conversion from various f
Page 51 and 52:
the mapping file example.paraStyleN
Page 53 and 54:
The second author accepts or reject
Page 55 and 56:
Languages for bibliography styles J
Page 57 and 58:
@STRING{srd = {Stephen Reeder Donal
Page 59 and 60:
# # standard footnote format (latex
Page 61 and 62:
. , \bbled \bbleds .
Page 63 and 64:
Languages for bibliography styles (
Page 65 and 66:
References [1] James C. Alexander:
Page 67 and 68:
Vistas for TEX: liberate the typogr
Page 69 and 70:
- even direct formatting instructio
Page 71 and 72: e that quick, simple and clear rend
Page 73 and 74: see that there are slight differenc
Page 75 and 76: Creating cuneiform fonts with MetaT
Page 77 and 78: Definition of encoding (Unicode) Pl
Page 79 and 80: epresentation with proper path dire
Page 81 and 82: When it came to implementing the T1
Page 83 and 84: 4.3 OpenType math in new TEX engine
Page 85 and 86: However, there have always been exc
Page 87 and 88: [2] Nelson Beebe: Character set enc
Page 89 and 90: Meta-designing parameterized Arabic
Page 91 and 92: on the pen direction at each point
Page 93 and 94: % Description for isolated ’alif
Page 95 and 96: Figure 15: Tracing a word from left
Page 97 and 98: Table 1 shows the MOS scores for in
Page 99 and 100: P3 P3 P3 Q2 Q2 Q2 � � W3 W3 W3
Page 101 and 102: abridged form, it looks like this:
Page 103 and 104: with extensions is still somewhat m
Page 105 and 106: local rx, ry = second.y_coord - ty,
Page 107 and 108: \startreusableMPgraphic{name}... \s
Page 109 and 110: the macro \testengine sees two argu
Page 111 and 112: and exhyph-uk.tex, respectively. Th
Page 113 and 114: stand for markers of semiconsonants
Page 115 and 116: y finite state transducers (FSTs).
Page 117 and 118: local p = hpack(copy(h.list)) lastl
Page 119 and 120: with PDF documents. Several new tec
Page 121: Advanced features for publishing ma
Page 125 and 126: — — — — — — — — Fig
Page 127 and 128: Advanced features for publishing ma
Page 129 and 130: telegraph. The relatively recent di
Page 131 and 132: 1: [ type: unichar, code: 0073 ] ]
Page 133 and 134: 5 Conclusions The model introduced
Page 135 and 136: 4 Why TEX files and not other marku
Page 137 and 138: The galley Module or: How I Learned
Page 139: TUGboat, Volume 29 (2008), No. 3 48
Page 142 and 143: 488 TUGboat, Volume 29 (2008), No.
Page 144 and 145: TUGBOAT Volume 29 (2008), No. 3 Tab
show all

The Communications of the TEX Users Group Volume 29 ... - TUG

Create successful ePaper yourself

Delete template?

Save as template?