LYX Branches” – a Case Study in Open Source and Development of Teaching Materials

Total Page:16

File Type:pdf, Size:1020Kb

LYX Branches” – a Case Study in Open Source and Development of Teaching Materials “LYX Branches” – a case study in Open Source and development of teaching materials Martin Vermeer May 7, 2020, originally March 8, 2004 1 Describing the problem The number of students without a command of Finnish is always small in my courses, but 1.1 Multilinguality in education a solution has to be found. This situation will become only more urgent as European policies Finland is a bilingual nation. Our university, in support of facilitating international student Helsinki University of Technology (HUT), is exchange take hold, which will position us on in reality multilingual and very international. an international market for attracting the best The presence of many foreign students implies and brightest to Helsinki. the need to be able to provide eduation, and I applied for funding for this translation work educational materials, in English in addition to from the HUT’s funds for teaching develop- Finnish and Swedish. ment, under the name Verkkodesia (a word play: I have on several occasions had to produce verkko means “network” in Finnish; desia comes exam question sets both in Finnish and in from geodesia == geodesy). Most of my applied- Swedish, sometimes also in English. Also lec- for funds were granted and the work could ture note sets and other teaching materials are start. sometimes needed in more than one language: in 2001, I was lecturing for the first time the course “Methods of Navigation”, which be- 1.2 The translation work longs to the major “Positioning and Naviga- tion”. Among the students were several grad- In spring 2002 I hired a student to translate uate students, one of which was a foreigner the lecture notes into English. She had spent a unable to read Finnish. The lecture notes were training period in Canada and thus managed however only available in Finnish. reasonably well in English, but by no means perfectly. I ended up making numerous correc- In 2001 I solved the problem by providing tions to the text, especially where professional the student with pages from an English text- terminology was concerned. Nevertheless, do- book, which contained more or less the same ing it in this way saved a substantial amount things. I decided however there and then, of my time. that I wouldn’t be caught again with my pants down. in 2003, the next time I lectured this This translation work was done using the LYX course, an English version of the lecture notes document processor, which is installed for use was available. And as it happened, there was on the HUT’s local area network’s UNIX and again a foreign student. Linux work stations. The student worked at 1 home using her own home Windows PC and a 2 A short description of Open Secure Shell as well as an “X server” (UNIX’s Source, LATEX and L X graphic user interface) installed onto it under Y the HUT’s campus licences for these packages. 2.1 What is Open Source? In this work, the existing standard version of LYX was used with a little “kludge” (ugly, im- provised solution) added to it. The basic idea Open Source, or in an older but more appropri- was however great: there was to be a single ate terminology free software, is currently best source document containing both the Finnish known because of the Linux operating system. and the English version in such a way, that cor- It comprises however much more than that. responding pieces of Finnish and English text The movement was started somewhere in the would show together in the same on-screen 1980’s out of frustration with the inflexibility of view. Changes could then be made simultane- proprietary software that was distributed with- ously in both languages, thus eliminating the out its source code, and that thus could not be synchronisation and jumping back and forth modified or adapted by its users. problems that occur when editing two separate The defining property of Open Source or free documents in their own editing windows. software is, that not only can it be freely dis- On the screen, the Finnish text was painted in tributed, but so can its source code, the original blue and the English text in magenta. Sepa- programming language code that is human- rate Finnish and English language PDF docu- readable and from which binary, executable ments could be output with the aid of a spe- applications are built. And this source is freely cially crafted LATEX code stanza in the docu- modifiable and redistributable. That is how the ment preamble, in which only a single number software grows and improves progressively in needed to be changed from 1 to 2 in order to the hands of an loosely organized, international get English instead of Finnish output. development community counting thousands, the Open Source/Free Software Movement. It must be clear that the invention of the Inter- 1.3 Developing the new feature net was the best thing that could ever have happened to free software. this is where the Encouraged by this experience, I decided that community lives. the “official” LYX sources should support this feature, i.e., editing two different language ver- Through the years, many useful applications sions within the same document. To my knowl- were produced, including several operating edge no other word processor offers this facil- systems, like FreeBSD and Linux. It is only now, ity. however, that the threads are coming together: I called the feature by the name of “Branches”. today a functionally reasonably complete work- Each branch can be a language or, e.g., in the station, operatable by somewhat knowledgable case of technical documentation, the slightly users, can be built based completely on Open different documentation texts for different Source software. Also more and more com- product versions. Or, when writing student mercial applications running on these freely exercises, the version including the answers or distributable systems are beginning to appear “teacher’s version” could be one branch; and so as use of free software is spreading in both cor- on. porate and public service environments. A second advantage of using branches is, that Free software has a community ethos that is those parts of a document that are the same in somewhat similar to that of the scientific com- both languages — formulas, figures, tables —, munity. There are in fact many close connec- need to be written only once. tions between the two. It is no coincidence that 2 the Unix operating system is popular in sci- An entirely different approach to document cre- entific circles and that Linus Torvalds chose it ation is offered by mark-up language, of which as his model when starting up Linux develop- the most well-known specimen is the HTML ment. Peer review, building on past achieve- or Hypertext Mark-up Language used for Web ments, and free exchange of ideas. pages. The principle, however, is much older. And the internet is a Unix network. The earliest UNIX systems included a program called troff, that was able to beautifully print to It has been argued that Open Source software paper a text into which suitable mark-up codes is more secure than proprietary software, due had been embedded. Of more recent origin is to its availablility for public inspection, and un- TEX, a computer mark-up language created by doubtedly there is truth in this. It has also be ar- the Californian math professor Donald KNUTH. gued, that part of this security advantage is sim- This language is still today in extensive use for ply due to its smaller installed base and more typesetting mathematics-heavy texts for scien- knowledgable users, and thus its unattractive- tific journals. ness as a target for crackers and malware writ- ers; undoubtedly that is partly true as well. A popular variant of TEX is LATEX, a macro pack- Nevertheless, it is hard to believe that the ex- age created by Leslie LAMPORT, which has as posure of the source code to public scrutiny, its beautiful characteristic the separation be- no matter how few people actually make in- tween a document’s structure and its visual ap- formed use of this, would not have a positive pearance. A large number of so-called document effect — in the same way that the scrutiny of classes have been created for LATEX, standard- a free press tends to make governments better ised layout solutions for, e.g., scientific jour- 1 behaved. nals . On the other hand deviating from these standard layouts, i.e., their visual-manual “tun- ing”, is cumbersome or impossible to do. (Not 2.2 What is (La)TEX? necessarily a bad thing, as such tuning tends to consume inordinate amounts of time and few Millions of computer users are familiar with so- users dabbling in this are competent typogra- called WYSIWYG word processing (“What You phers.) See Is What You Get”), as practiced in Microsoft Word, WordPerfect or StarOffice Writer. The If you are curious why on Earth many people governing principle is that the on-screen view still use LATEX when perfectly good WYSIWYG is reproduced faithfully on paper. software exists, you only should visually com- pare a text typeset by LAT X with the same text The beauty of WYSIWYG is, that it is easily E created in Microsoft Word. Especially if the text learnt and a robust principle: it produces pre- is scientific. The typographic quality is from a cisely what it promises. different planet. Nevertheless WYSIWYG has its share of prob- lems and limitations. “What You See Is All You Get”. For this reason, all word processing appli- 2.3 What is LYX? cations contain also non-WYSIWYG properties, such as, e.g., auto-numbering header styles.
Recommended publications
  • Build It with Nitrogen the Fast-Off-The-Block Erlang Web Framework
    Build it with Nitrogen The fast-off-the-block Erlang web framework Lloyd R. Prentice & Jesse Gumm dedicated to: Laurie, love of my life— Lloyd Jackie, my best half — Jesse and to: Rusty Klophaus and other giants of Open Source— LRP & JG Contents I. Frying Pan to Fire5 1. You want me to build what?7 2. Enter the lion’s den9 2.1. The big picture........................ 10 2.2. Install Nitrogen........................ 11 2.3. Lay of the land........................ 13 II. Projects 19 3. nitroBoard I 21 3.1. Plan of attack......................... 21 3.2. Create a new project..................... 23 3.3. Prototype welcome page................... 27 3.4. Anatomy of a page...................... 30 3.5. Anatomy of a route...................... 33 3.6. Anatomy of a template.................... 34 3.7. Elements............................ 35 3.8. Actions............................. 38 3.9. Triggers and Targets..................... 39 3.10. Enough theory........................ 40 i 3.11. Visitors............................ 44 3.12. Styling............................. 64 3.13. Debugging........................... 66 3.14. What you’ve learned..................... 66 3.15. Think and do......................... 68 4. nitroBoard II 69 4.1. Plan of attack......................... 69 4.2. Associates........................... 70 4.3. I am in/I am out....................... 78 4.4. Styling............................. 81 4.5. What you’ve learned..................... 82 4.6. Think and do......................... 82 5. A Simple Login System 83 5.1. Getting Started........................ 83 5.2. Dependencies......................... 84 5.2.1. Rebar Dependency: erlpass ............. 84 5.3. The index page........................ 85 5.4. Creating an account..................... 87 5.4.1. db_login module................... 89 5.5. The login form........................ 91 5.5.1.
    [Show full text]
  • LYX Frequently Asked Questions with Answers
    LYX Frequently Asked Questions with Answers by the LYX Team∗ January 20, 2008 Abstract This is the list of Frequently Asked Questions for LYX, the Open Source document processor that provides a What-You-See-Is-What-You-Mean environment for producing high quality documents. For further help, you may wish to contact the LYX User Group mailing list at [email protected] after you have read through the docs. Contents 1 Introduction and General Information 3 1.1 What is LYX? ......................... 3 1.2 That's ne, but is it useful? . 3 1.3 Where do I start? . 4 1.4 Does LYX run on my computer? . 5 1.5 How much hard disk space does LYX need? . 5 1.6 Is LYX really Open Source? . 5 2 Internet Resources 5 2.1 Where should I look on the World Wide Web for LYX stu? 5 2.2 Where can I get LYX material by FTP? . 6 2.3 What mailing lists are there? . 6 2.4 Are the mailing lists archived anywhere? . 6 2.5 Okay, wise guy! Where are they archived? . 6 3 Compatibility with other word/document processors 6 3.1 Can I read/write LATEX les? . 6 3.2 Can I read/write Word les? . 7 3.3 Can I read/write HTML les? . 7 4 Obtaining and Compiling LYX 7 4.1 What do I need? . 7 4.2 How do I compile it? . 8 4.3 I hate compiling. Where are precompiled binaries? . 8 ∗If you have comments or error corrections, please send them to the LYX Documentation mailing list, <[email protected]>.
    [Show full text]
  • A Work-Pattern Centric Approach to Building a Personal Knowledge Advantage Machine
    Graduate Theses, Dissertations, and Problem Reports 2012 A Work-Pattern Centric Approach to Building a Personal Knowledge Advantage Machine Daniel Sloan West Virginia University Follow this and additional works at: https://researchrepository.wvu.edu/etd Recommended Citation Sloan, Daniel, "A Work-Pattern Centric Approach to Building a Personal Knowledge Advantage Machine" (2012). Graduate Theses, Dissertations, and Problem Reports. 4919. https://researchrepository.wvu.edu/etd/4919 This Thesis is protected by copyright and/or related rights. It has been brought to you by the The Research Repository @ WVU with permission from the rights-holder(s). You are free to use this Thesis in any way that is permitted by the copyright and related rights legislation that applies to your use. For other uses you must obtain permission from the rights-holder(s) directly, unless additional rights are indicated by a Creative Commons license in the record and/ or on the work itself. This Thesis has been accepted for inclusion in WVU Graduate Theses, Dissertations, and Problem Reports collection by an authorized administrator of The Research Repository @ WVU. For more information, please contact [email protected]. A Work-Pattern Centric Approach to Building a Personal Knowledge Advantage Machine Daniel Sloan Thesis submitted to the College of Engineering and Mineral Resources at West Virginia University in partial fulfillment of the requirements for the degree of Master of Science in Computer Science Yenumula V. Reddy, Ph.D., Chair Bojan Cukic, Ph.D. Cynthia D. Tanner, MS. Lane Department of Computer Science and Electrical Engineering Morgantown, West Virginia 2012 Keywords: Work-patterns, file usage, semantic desktop, machine learning Copyright c 2012 Daniel Sloan Abstract A Work-Pattern Centric Approach to Building a Personal Knowledge Advantage Machine Daniel Sloan A work pattern, also known as a usage pattern, can be broadly defined as the methods by which a user typically utilizes a particular system.
    [Show full text]
  • Metadefender Core V4.12.2
    MetaDefender Core v4.12.2 © 2018 OPSWAT, Inc. All rights reserved. OPSWAT®, MetadefenderTM and the OPSWAT logo are trademarks of OPSWAT, Inc. All other trademarks, trade names, service marks, service names, and images mentioned and/or used herein belong to their respective owners. Table of Contents About This Guide 13 Key Features of Metadefender Core 14 1. Quick Start with Metadefender Core 15 1.1. Installation 15 Operating system invariant initial steps 15 Basic setup 16 1.1.1. Configuration wizard 16 1.2. License Activation 21 1.3. Scan Files with Metadefender Core 21 2. Installing or Upgrading Metadefender Core 22 2.1. Recommended System Requirements 22 System Requirements For Server 22 Browser Requirements for the Metadefender Core Management Console 24 2.2. Installing Metadefender 25 Installation 25 Installation notes 25 2.2.1. Installing Metadefender Core using command line 26 2.2.2. Installing Metadefender Core using the Install Wizard 27 2.3. Upgrading MetaDefender Core 27 Upgrading from MetaDefender Core 3.x 27 Upgrading from MetaDefender Core 4.x 28 2.4. Metadefender Core Licensing 28 2.4.1. Activating Metadefender Licenses 28 2.4.2. Checking Your Metadefender Core License 35 2.5. Performance and Load Estimation 36 What to know before reading the results: Some factors that affect performance 36 How test results are calculated 37 Test Reports 37 Performance Report - Multi-Scanning On Linux 37 Performance Report - Multi-Scanning On Windows 41 2.6. Special installation options 46 Use RAMDISK for the tempdirectory 46 3. Configuring Metadefender Core 50 3.1. Management Console 50 3.2.
    [Show full text]
  • List of Word Processors (Page 1 of 2) Bob Hawes Copied This List From
    List of Word Processors (Page 1 of 2) Bob Hawes copied this list from http://en.wikipedia.org/wiki/List_of_word_processors. He added six additional programs, and relocated the Freeware section so that it directly follows the FOSS section. This way, most of the software on page 1 is free, and most of the software on page 2 is not. Bob then used page 1 as the basis for his April 15, 2011 presentation Free Word Processors. (Note that most of these links go to Wikipedia web pages, but those marked with [WEB] go to non-Wikipedia websites). Free/open source software (FOSS): • AbiWord • Bean • Caligra Words • Document.Editor [WEB] • EZ Word • Feng Office Community Edition • GNU TeXmacs • Groff • JWPce (A Japanese word processor designed for English speakers reading or writing Japanese). • Kword • LibreOffice Writer (A fork of OpenOffice.org) • LyX • NeoOffice [WEB] • Notepad++ (NOT from Microsoft) [WEB] • OpenOffice.org Writer • Ted • TextEdit (Bundled with Mac OS X) • vi and Vim (text editor) Proprietary Software (Freeware): • Atlantis Nova • Baraha (Free Indian Language Software) • IBM Lotus Symphony • Jarte • Kingsoft Office Personal Edition • Madhyam • Qjot • TED Notepad • Softmaker/Textmaker [WEB] • PolyEdit Lite [WEB] • Rough Draft [WEB] Proprietary Software (Commercial): • Apple iWork (Mac) • Apple Pages (Mac) • Applix Word (Linux) • Atlantis Word Processor (Windows) • Altsoft Xml2PDF (Windows) List of Word Processors (Page 2 of 2) • Final Draft (Screenplay/Teleplay word processor) • FrameMaker • Gobe Productive Word Processor • Han/Gul
    [Show full text]
  • Conservative Conversion Between and Texmacs
    Conservative conversion between A L TEX and TEXMACS by Joris van der Hoevena, François Poulainb LIX, CNRS École polytechnique 91128 Palaiseau Cedex France a. Email: [email protected] b. Email: [email protected] April 15, 2014 Abstract Back and forth converters between two document formats are said to be conservative if the following holds: given a source document D, its conversion D0, a locally modied version M 0 of D0 and the back con- version M of M 0, the document M is a locally modied version of D. We will describe mechanisms for the implementation of such converters, A with the L TEX and TEXMACS formats as our guiding example. Keywords: Conservative document conversion, LATEX conversion, TEXMACS, mathematical editing A.M.S. subject classication: 68U15, 68U35, 68N99 1 Introduction The TEXMACS project [7, 10] aims at creating a free scientic oce suite with an integrated structured mathematical text editor [8], tools for graphical drawings and presentations, a spreadsheed, interfaces to various computer algebra sys- tems, and so on. Although TEXMACS aims at a typesetting quality which is at least as good as TEX and LATEX [14, 15], the system is not based on these latter systems. In particular, a new incremental typesetting engine was implemented from scratch, which allows documents to be edited in a wysiwyg and thereby more user friendly manner. This design choice made it also possible or at least easier to use TEXMACS as an interface for external systems, or as an editor for technical drawings. However, unlike existing graphical front-ends for LATEX such as LyX [2] or Scientific Workplace [23], native compatibility with LATEX is not ensured.
    [Show full text]
  • 32 Tugboat, Volume 22 (2001), No. 1/2
    32 TUGboat, Volume 22 (2001), No. 1/2 LYX — An Open Source Document Processor Laura Elizabeth Jackson and Herbert Voß Abstract LYX — the so-called front-end to LATEX, which is itself a front-end to TEX — tries to optimize some- thing that LATEX doesn’t attempt: to make a high quality layout system like (LA)TEX accessible to users who are relatively uninterested in serious typograph- ical questions. LYX is not a word processor, but a document processor, because it takes care of many of the formatting details itself, details that the user need not be bothered with. All LYX features de- scribed here apply to the current official version LYX 1.1.6fix4. The significantly expanded version 1.2 is expected this summer. 1 History Drawing on the principles of the traditional printed word, Donald Knuth1 developed a system that en- abled users to prepare professional technical publi- cations. Knuth called the first version of this system τχ, which has since come to be written TEX and pronounced “tech”. A graphical user interface is in principle not essential for LATEX; however, in today’s “all-things- bright-and-beautiful” world, the absence of a GUI makes LATEX less accessible to the masses. This lack of a GUI was recognized in 1994/95 as the opportunity to create one; it began as a master’s thesis and was first called Lyrik, then LyriX, and finally LYX. From the beginning, the main goal so that the user would be freed from having to delve into the details of (LA)TEX usage.
    [Show full text]
  • LYX Tips and Tricks
    LYX Tips and Tricks Alex Ames February 12, 2015 Contents General overview2 Purpose of LYX.......................................2 Hello, world........................................2 Using LYX on CAE lab computers............................3 Document settings....................................3 Adding graphics and tables...............................3 Further reading......................................4 Math maneuvers5 Shortcuts and special characters.............................6 Making fractions fit....................................6 Math operators......................................7 Vectors...........................................8 Matrices..........................................8 Defining your own operators..............................9 Advanced Fiddling9 What I’ve discovered (and want to record).......................9 1 General overview Purpose of LYX TL;DR: LYX makes it easy to create good-looking technical papers. LYX is designed using the WYSIWYM (what you see is what you mean) paradigm, versus standard word processors like MS Word, which use WYSIWYG (what you see is what you get). This means that when you want to add a section heading, you select ’Section’ in the drop-down menu to the top left, and LYX will take care of the formatting. It also has a very powerful and flexible math typesetting system. LYX takes a bit of adjustment, but it means that you don’t have to remember which font size you’ve been using for headings, or futz around with spacing. It isn’t always the right tool for a particular job; it’s good at making great-looking technical papers and reports, but it’s much harder to fiddle around with graphic placement and fonts like you might want to for a poster. If you’ve ever used LATEX, you should be right at home–LYX is built as a graphical interface on top of LATEX, abstracting away the class declarations and control symbols that clutter up LATEX source files and instead showing you something that’s closer to the final result.
    [Show full text]
  • LYX for Academia
    LYX for academia John R Hudson∗† 1 What is LYX? LyX is a cross-platform program which harnesses the resources of the TEX, XeTeX and LuaTeX typesetting engines and a wide variety of writing tools, including the LibreOffice dictionaries and thesauri, to enable writers, editors, copy-editors and typesetters to create superior docu- ments for web and print media. 2 TEX, LATEX and LYX TEX1, a typesetting engine written in Pascal by Donald Knuth, implements best typesetting practice as set out in the The Chicago manual of style (University of Chicago Press, 1982). Among the limitations of TEX arising from its creation before the growth of the Internet is that it does not support Unicode and offers only a limited range of typefaces. The XeTEX and LuaTEX typesetting engines seek to address these weaknesses and support for them was added in LYX 2. LATEX began as a markup language to help DEC employees to use TEX but has spawned a large number of packages to serve the diverse needs of writers, all of which are available from CTAN. No one needs them all; so selections of the most useful are distributed, notably as MacTeX for Apple computers, TexLive for Linux and MiKTeX for Windows, to which users can add whatever else they need from CTAN. LYX was created by Matthias Ettrich in 1995 as a graphical user interface for the LATEX macros. Originally, it simply hid the complexity of the most common features of LATEX so that the user could produce beautiful documents without knowing anything about LATEX. But it has gradually evolved into a flexible writing tool that can handle an increasing range of LATEX features while enabling those who understand LATEX to tweak the output in a variety of ways.
    [Show full text]
  • Microsoft Exchange 2007 Journaling Guide
    Microsoft Exchange 2007 Journaling Guide Digital Archives Updated on 12/9/2010 Document Information Microsoft Exchange 2007 Journaling Guide Published August, 2008 Iron Mountain Support Information U.S. 1.800.888.2774 [email protected] Copyright © 2008 Iron Mountain Incorporated. All Rights Reserved. Trademarks Iron Mountain and the design of the mountain are registered trademarks of Iron Mountain Incorporated. All other trademarks and registered trademarks are the property of their respective owners. Entities under license agreement: Please consult the Iron Mountain & Affiliates Copyright Notices by Country. Confidentiality CONFIDENTIAL AND PROPRIETARY INFORMATION OF IRON MOUNTAIN. The information set forth herein represents the confidential and proprietary information of Iron Mountain. Such information shall only be used for the express purpose authorized by Iron Mountain and shall not be published, communicated, disclosed or divulged to any person, firm, corporation or legal entity, directly or indirectly, or to any third person without the prior written consent of Iron Mountain. Disclaimer While Iron Mountain has made every effort to ensure the accuracy and completeness of this document, it assumes no responsibility for the consequences to users of any errors that may be contained herein. The information in this document is subject to change without notice and should not be considered a commitment by Iron Mountain. Iron Mountain Incorporated 745 Atlantic Avenue Boston, MA 02111 +1.800.934.0956 www.ironmountain.com/digital
    [Show full text]
  • Application Tips for Word Processors Introduction Formatting a Table Of
    Application Tips for Word Processors [email protected] [ updated: Monday, December 27, 2010 ] Course: BUS 302 Title: The Gateway Experience (3 units) “Man is still the most extraordinary computer of all.” ---John F. Kennedy (1917-1963) Introduction Most contemporary business students use Microsoft Word (MS-Word) for the production of their case reports and other print-based deliverables. The purpose of this document is to help BUS 302 students learn a few commands in MS-Word that are helpful in producing a quality work product. In general, MS-Word works the same way in both the Windows and MacOS environments. Similar commands exist in other word processing applications, such as OpenOffice Writer (Linux/MacOS/Windows), Lyx (Linux/MacOS/Windows), AbiWord (Linux/MacOS/Windows) and Pages (MacOS). Similar commands exist in online word processing applications, such as Google Docs, although the functionality may be limited. If this document is unclear, please contact the instructor. Formatting a Table of Contents Table of Contents typically have some text (usually a section or a component of the case report) on the left-hand side of the page and a page number on the right-hand side of the page. And in between both of those two elements lie “dot leaders.” Dot leaders connect the text on the left-hand side with the page number on the right-hand side to improve clarity and reduce ambiguity for the reader. Appendix..............................................................................................................................5 The command sequence to insert a dot leader is to 1), move the cursor to the first line of the table of contents, 2), select “Format | Tabs,” 2), insert 6 to place a tab stop at the sixth inch (or similar), 3), select “Decimal” alignment, 4), select “…” leader, 5), click “Set”, and 6), click “Close.” Now, type the text on the left-hand side of the page, press the tab key, and type the page number.
    [Show full text]
  • TUGBOAT Volume 31, Number 1 / 2010
    TUGBOAT Volume 31, Number 1 / 2010 General Delivery 3 From the president / Karl Berry 4 Editorial comments / Barbara Beeton TEX at 25; Pi Day; The @ sign as a design icon; Amusements on the Web; Videos of typography talks on the Web; Alphabet soup 6 An argument for learning LATEX: The benefits of typesetting and beyond / Evan Wessler Publishing 9 A computer scientist self-publishing in the humanities / Nicolaas Mars Typography 12 Strategies against widows / Paul Isambert 18 Theses and other beautiful documents with classicthesis / Andr´eMiede 21 Typographers’ Inn / Peter Flynn Fonts 23 Minimal setup for a (cyrillic) TrueType font / Oleg Parashchenko 26 LuaTEX: Microtypography for plain fonts / Hans Hagen 27 Mathematical typefaces in TEX documents / Amit Raj Dhawan Software & Tools 32 LuaTEX: Deeply nested notes / Hans Hagen Graphics 36 Plotting experimental data using pgfplots / Joseph Wright 50 The current state of the PSTricks project / Herbert Voß 59 From Logo to MetaPost / Mateusz Kmiecik A L TEX 64 LATEX news, issue 19 / LATEX Project Team 65 Talbot packages: An overview / Nicola Talbot 68 Tuning LATEX to one’s own needs / Jacek Kmiecik 76 Some misunderstood or unknown LATEX2ε tricks / Luca Merciadri A L TEX 3 79 LATEX3 news, issue 3 / LATEX Project Team 80 Beyond \newcommand with xparse / Joseph Wright 83 Programming key–value in expl3 / Joseph Wright ConTEXt 88 ConTEXt basics for users: Conditional processing / Aditya Mahajan Hints & Tricks 90 Glisterings: Counting; Changing the layout / Peter Wilson 94 The exact placement of superscripts
    [Show full text]