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$

Jonathan Kew Figure 2: TEXworks running on Mac OSX: using the Preferences dialog to configure a typesetting tool. 4 Future plans After the release of version 0, several major additional features are planned; some ideas high on the priority list include: • intelligent handling of TEX errors • assistance with graphics inclusion and format conversions • text search and copy in the PDF preview • support rich PDF features such as transitions, embedded media (sound, video), annotations, etc. • customizable palettes of symbols, commands, etc. • TEX documentation lookup/browser • interaction with external editors and other tools • additional support for navigating in the source, e.g., “folding” sections of text, recognizing document structure tags such as \section, etc. I expect development priorities to be guided by user feedback as well as developer interest, once the initial version 0 release is available. 5 Invitation to participate TEXworks is a free and open source software project, and all are welcome to participate and contribute to its development. This does not necessarily mean writing code; many other roles are equally important. Some possible ways to participate include the following. • Use the prototype for some real work, and give feedback on what’s good, what’s bad, what’s broken: – if there’s a current binary download available for your platform, try that; – get the code and try building it on your platform; provide bug reports (and fixes!) for whatever problems show up. Figure 3: TEXworks running on a typical GNU/Linux system (Ubuntu). • Dig in to the code, and submit patches to implement your favorite missing features. • Write on-line help, documentation and tutorials for newcomers to TEXworks and TEX. • Review and enhance the command completion lists available for the integrated editor. • Provide well-commented templates for various types of documents. • Design icons for the toolbars, etc.; TEXworks has some nice icons from Qt and the Tango project, but others are merely rough placeholders. • Use the Qt Linguist tool to localize the user interface for your language. • Package TEXworks appropriately for your favorite GNU/Linux or BSD distribution, or create an installer for Windows or Mac OSX. There is a TEXworks mailing list for questions and discussions related to the project; see http:// lists.tug.org/texworks/ to subscribe, for the list archives, etc. The TEXworks source itself is maintained in a Google Code project at http://code.google.com/ p/texworks/. Resources available through this site include the Subversion source repository, precompiled binaries for Windows and Mac OSX, and an issue tracker for bug reports and feature suggestions. 6 Thanks The TEXworks project arose out of discussions at several recent TEX Users Group meetings, and has received generous support from TUG’s TEX development fund and its contributors, and from UK-TUG. Special thanks to Karl Berry for his encouragement and support, and to Dick Koch for showing us the potential of a clean, simple TEX environment for the average user. 364 TUGboat, Volume 29 (2008), No. 3 — Proceedings of the 2008 Annual Meeting
Direct and reverse synchronization with SyncTEX Jérôme Laurens Département de mathématiques Université de Bourgogne 21078 Dijon Cedex FRANCE jerome (dot) laurens (at) u-bourgogne (dot) fr http://itexmac.sourceforge.net/SyncTeX.html Abstract We present a new technology named SyncTEX used to synchronize between the TEX input and the output. 1 What is synchronization? Creating documents with the TEX typesetting system often requires two windows, one for entering the text, the other one for viewing the resulting output. In general, documents are too long to fit in the visible frame of a window on screen, and what is really visible is only some part of either the input or the output. We say that the input view and the output view are synchronized if they are displaying the “same” portion of the document. Forwards or direct synchronization is the ability, for an output viewer, to scroll the window to a part corresponding to a given location in the input file. Backwards or reverse synchronization is the ability, for a text editor, to scroll the text view to a part corresponding to a given location in the output file. Figure 1 is a screenshot illustrating SyncTEX supported in iTEXMac2, the TEX front end developed by the author on Mac OS X. The top window is a text editor where an extract of the “Not so short introduction to L ATEX 2ε” is displayed. The word “lscommand” has been selected and the viewer window at the bottom automatically scrolled to the position of this word in the output, highlighting it with a small red arrow. The grey background was added afterwards in the bottom window for the sake of visibility on printed media. 2 What is SyncTEX? This is a new technology embedded in both pdfTEX and XE TEX, available in the 2008 TEX Live and corresponding MiKTEX distributions. When activated, it gives both text editors and output viewers the necessary information to complete the synchronization process. It will be available in LuaTEX soon. In order to activate SyncTEX, there is a new command line option: pdftex -synctex=1 foo.tex Figure 1: Synchronization in iTEXMac2 based on SyncTEX technology with text analysis. (or --synctex=1) and the same for xetex. With this option, a new informational line is printed at the end of the command output and reads SyncTeX written on foo.synctex.gz. The new (compressed) auxiliary file named foo.synctex.gz is used by applications for the synchronization process; this is the SyncTEX output file. Setting the synctex option to -1 creates an uncompressed foo.synctex auxiliary file, more suitable for certain operations. Setting it to 0 definitively prevents SyncTEX activation. There is also an eponymous new TEX primitive that you can set to 1 for SyncTEX activation from the source file: \synctex=1. It can be used, for example, to temporarily disable SyncTEX operations for some input file by properly using \synctex=0. This primitive has no effect if the -synctex=0 command line option was given, or if the first page has already been shipped out (it is then too late to activate SyncTEX). TUGboat, Volume 29 (2008), No. 3 — Proceedings of the 2008 Annual Meeting 365
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: TEXworks: Lowering the barrier to e
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 and 122:
Advanced features for publishing ma
Page 123 and 124:
Page 125 and 126:
— — — — — — — — Fig
Page 127 and 128:
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?