Complete issue 30:3 as one pdf - 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$

E12 MAPS 39 Kees van der Laan Knuthforecastedthefuture bysayingthathewoulduse TEXahundredyearsafterthebirthofTEXwiththesame qualityasthat ofthe beginning days. Using paradigms in macro writing will increase readability. One needs time and courage to invest in the use of plain TEX and MetaPost, which will serve a lifetime, and will enrich your insight. Learning just a little bit of PostScript will not harm. You will be surprised by what youcanachievebyit,withAdobePhotoshopasnishing touchfor(interactive)coloringorremovinghiddenlines. OntheotherhandifthemajorityoftheTEXcommunity spends time and energy on L ATEX, ConTEXt, LuaTEX, in general on successors of TEX, . . .it is hard to stay with plain TEX, to stay with Knuth, which means without development. However, if one thinks a little deeper, it is an ill-posed rhetoricalsuggestion. TEX is a xed point, only the environment changes Adaptation to PS is for example taken care of by the driverdvi(2)psandilks,andpdfoutputcanbeobtained by Distiller or Acrobat (not tested though by me for a document), or just one of the various pstopdfs. TEX commands for handling colors and inclusion of graphics are dictated by the drivers and have to be included in \specials. I have no problems at all to leave MetaFont for MetaPost, because. . . well, again an ill-posed suggestion. I don’t leave MetaFont, I just don’t use it for graphics any longer, I’m not a font designer.Well,. . .againpartiallytrue:I’llcontinuetouse MetaFontasmypoorman’slimitedMetaPostpreviewer. MetaFont and MetaPost have dierent purposes: the rst one is aimed at bitmap font design, the second at creating PS graphics for inclusion in AnyTEX or troff. TheMetaFontbookisstillneededbecauseoftheunusual concepts suffix, vardef, primarydef, secondarydef, and tertiarydef, which MetaPost has taken over from MetaFont, andwhichIdon’t graspcompletely, yet. A middle road is provided by ConTEXt, which also comes with a wealth of documentation and is actively supported by its author Hans Hagen and colleagues, for exampleTacoHoekwater. ArealbreakthroughwouldbeaninteractiveTEX, whichIwoulduseimmediately. OnecanlookuponthisaswhatAppledid.Theyadopted UNIX as the underlying OS, and built their nice GUI on top. ComesTEXshop close? Minimal markup As said in my PWT guide, I favor to start with just text in a WYSIWYG way. Once you have your contents more or less right, have it spell-checked, andonlytheninsertasfewmarkuptagsaspossible.The resultiswhatIcallaMinimal Marked up script. But... do you have the patience to work along these lines? In reality this is my logical way of working. In practice IinsertalreadymarkuponceIhaveareasonableversion. Or, do you favor to rush into code and start with \begindocument...etc, without having written a word of the contents yet? Marvin Minsky drew attention to this already in his Turing Award lecture of long ago ‘Form versusContent.’Thisapproach,tomarkupattheendand useaslittleaspossibleofTEX,isnextbestto WYSIWYG- TEX, andmy main reason to practise Minimal Markup. BelowtheessentialsofmyMinimalMarkedupscript, obeying the 20%-80% adage, forthispaper isgiven. \input adhocmacros \author ... \abstract ... \keywords ... \head Script ... \subhead
TEX Education EUROTEX 2009 E13 ... \jpgD ... ...\ftn ... \bye In order to mark up in the above spirit, I have borrowed from BLUe the followingmacros 11 \def\keywords#1\par{...} \def\abstract#1\par{...} \def\((sub)sub)head#1\par{...} \def\ftn#1{...}%#1 footnote tekst \def\beginverbatim \def\endverbatim \def\beginquote \def\endquote while \jpgD was just created for the occasion. Handy is the \ftn macro, which takes care of the automatic numbering of the footnotes. While working on this note,whicha.o.emphasizestheuseofMinimalMarkup, I adapted the \ftn macro, such that the curly braces around the footnote text are no longer needed: just end thefootnotebyablanklineora\par,implicitorexplicit. Also convenient is the functionality of a Mini-ToC. Forthe latter allyouneed isto insert %In \head \immediate\write\toc{#1} %In subhead \immediate\write\toc{\noexpand\quad#1} %In subsubhead \immediate\write\toc{\noexpand\qquad#1} Of course \newwrite\toc \immediate\openout\toc=\jobname.toc must be supplied in the adhoc macros as well. Reuse on the y! But... A L ATEXie would shrug shoulders, because (s)he has got it allalready. True! But... at the loss of minimal markup. A BLUe user has both themacrosandtheminimalmarkup.Amatterofchoice, choose whatyoufeel comfortablewith. If you like to concentrate on contents, clean scripts, abhor the curly braces mania, to err less andless,thenMinimal Markupisforyou. Knuth’s approach What astonishes me most is that Knuth’s plain.tex is notembracedbythemajority.Hisbasicapproachshould be taught, because in TEX, well in automated digital typesetting, there are so many subtle things, where you will stumble upon sooner or later, which cannot be shielded away from you by AnyTEX, completely. Just pushing the buttons—inserting by an IDE prompted markuptags—isnot enough. HowcomethatusersdidnotadoptKnuth’splain.tex? Is it impatience, because mastering the TEXbook with plain.tex embodied takes time, and much more when not guided by askilfulteacher? History has it, that rst gains were preferred by adopting L ATEX, which dares to explain less, keeps you unaware, which emphasizes the structure of documents, though not so rigorous as SGML, in a time when structuring whatever was en vogue. I’m not saying that structuringiswrong, not at all. But... oneshouldnotoverdoit,oneshouldnotsuggestitisthe one and only. Keep eyes open, be on the alert for other aspects. On the other hand L ATEX comes with a lot of packages, nowadays. Whentheminimalmarkupattitudeisadopted,onedoes notneedthatmanymarkupinstructions!Thestructureis alreadythere,inwhatyouhavetosay,noneedtooverdo it. For this note I used basically a handful of structural macros, well... a few more, to be replaced by the ones used by the editor. Knuth was right from the very beginning, though... not completely! JohnPlaice commented onmypresentation ‘... that it was not possible to praise Dijkstra and Knuth in the same sentence as the two held completely opposite points of view with respect to programming languages. When Dijkstra published his ‘Go to considered harmful’(CACM 11(3):147-148, 1968), Knuth defended the goto statement with his ‘Structured Programming with go to Statements’ (Computing Surveys 6(4):261–301, 1974). AccordingtoPlaice,Knuthconsistentlysupportedthe use of low-level languages for programming. In writing his TAOCP series of books, Knuth used his own assembler, the MIX, which he updated to a RISC machine, the MMIX, for the latest edition. HisTEX: The Programbook regularlymakesuseofgotos.Theregistermodelusedin TEXprogrammingisthatofanassemblerandthesyntax is COBOLish. Knuth’s TEX macro language has been criticized publiclybyLeslieLamport,whostatedthatifhehadknown thatTEXwouldhavesurvivedforsolong,thathewould
Page 1 and 2: Proceedings MAPS 39 • TUGboat 30:
Page 3: Table of Contents EuroTEX 2009, Han
Page 8 and 9: E4 MAPS 39 TUG 2010 TEX’s 2 5 ann
Page 10 and 11: E6 MAPS 39 Kees van der Laan What T
Page 12 and 13: E8 MAPS 39 Kees van der Laan andthe
Page 14 and 15: E10 MAPS 39 Kees van der Laan I hav
Page 18 and 19: E14 MAPS 39 Kees van der Laan have
Page 20 and 21: E16 MAPS 39 Kees van der Laan I mus
Page 22 and 23: E18 MAPS 39 Kees van der Laan First
Page 24 and 25: E20 MAPS 39 Kees van der Laan The p
Page 26 and 27: E22 MAPS 39 Kees van der Laan drawa
Page 28 and 29: E24 MAPS 39 Kees van der Laan Synta
Page 30 and 31: E26 MAPS 39 Kees van der Laan Essen
Page 32 and 33: E28 MAPS 39 Kees van der Laan NaumG
Page 34 and 35: E30 MAPS 39 Kees van der Laan The a
Page 36 and 37: E32 MAPS 39 Kees van der Laan 19. M
Page 38 and 39: E34 MAPS 39 Luigi Scarso LuaTEX lun
Page 40 and 41: E36 MAPS 39 Luigi Scarso It’s bet
Page 42 and 43: E38 MAPS 39 Luigi Scarso So we must
Page 44 and 45: E40 MAPS 39 Luigi Scarso luatex-sna
Page 46 and 47: E42 MAPS 39 Luigi Scarso it’s bou
Page 48 and 49: E44 MAPS 39 Luigi Scarso ghost.appe
Page 50 and 51: E46 MAPS 39 Luigi Scarso andimport
Page 52 and 53: E48 MAPS 39 Luigi Scarso \externalf
Page 54 and 55: E50 MAPS 39 Luigi Scarso %% \startl
Page 56 and 57: E52 MAPS 39 Luigi Scarso [8] http:/
Page 63 and 64: Willi Egger EUROTEX 2009 E59 Decora
Page 65 and 66: Decorating CD-ROMs and DVDs EUROTEX
Page 67 and 68:
Decorating CD-ROMs and DVDs EUROTEX
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
The language mix EUROTEX 2009 E73 S
Page 79 and 80:
The language mix EUROTEX 2009 E75 \
Page 81 and 82:
The language mix EUROTEX 2009 E77 T
Page 83:
E16 & DEtool: typesetting language
Page 87:
E16 & DEtool: typesetting language
Page 90 and 91:
E86 MAPS 39 Siep Kroonenberg A netw
Page 92 and 93:
E88 MAPS 39 Siep Kroonenberg machin
Page 94 and 95:
E90 MAPS 39 Siep Kroonenberg Additi
Page 96 and 97:
E92 MAPS 39 Jean-Michel Hufflen Usi
Page 98 and 99:
E94 MAPS 39 Jean-Michel Hufflen fun
Page 100 and 101:
E96 MAPS 39 Jean-Michel Hufflen (de
Page 102 and 103:
E98 MAPS 39 Jean-Michel Hufflen Not
Page 104 and 105:
E100 MAPS 39 A.-M. Aebischer, B. Ae
Page 106 and 107:
Page 108 and 109:
Page 111 and 112:
Stanislav Jan Šarman EUROTEX 2009
Page 113 and 114:
Writing Pitman shorthand with Metaf
Page 115 and 116:
Writing Pitman shorthand with Metaf
Page 117 and 118:
Optimizing PDF output size of TEX d
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Taco Hoekwater EUROTEX 2009 E131 Ge
Page 137 and 138:
Generating PDF for e-reader devices
Page 139 and 140:
Generating PDF for e-reader devices
Page 141 and 142:
LuaTEX says goodbye to Pascal EUROT
Page 143 and 144:
LuaTEX says goodbye to Pascal EUROT
Page 145 and 146:
Taco Hoekwater EUROTEX 2009 E141 Th
Page 147 and 148:
Hans Hagen & Taco Hoekwater EUROTEX
Page 149 and 150:
John Trapp EUROTEX 2009 E145 Using
Page 151 and 152:
Using L ATEX as a computing languag
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Experiences typesetting mathematica
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Abstracts without papers UsingTEXFo
Page 185 and 186:
Abstracts without papers EUROTEX 20
Page 187:
The information here comes from the
show all

Complete issue 30:3 as one pdf - TUG

Create successful ePaper yourself

Delete template?

Save as template?