TEX Project: a Case Study of Open-Source Software

Total Page:16

File Type:pdf, Size:1020Kb

TEX Project: a Case Study of Open-Source Software The (LA)TEX project: A case study of open-source software Alexandre Gaudeul∗ University of Toulouse [email protected] December 15, 2003 ∗I would like to thank William Adams, Jacques André, Nelson Beebe, Barbara Beeton, Karl Berry, Lance Carnes, Thomas Esser, David Fuchs, Bernard Gaulle, Hans Hagen, Yannis Haralambous, Jim Hefferon, David Kastrup, Donald Knuth, Leslie Lamport, Wendy McKay, Barry McKichan, B. Mahesh, Frank Mittelbach, Oren Patashnik, Simon Pepping, John Plaice, Fabrice Popineau, Sebastian Rahtz, Denis Roegel, Chris Rowley, Joachim Schröd, Karel Skoupy, Hàn Thê´ Thành, and all other TEX project participants I met. This paper was directly inspired by the reflections that community kept having about its own culture, history, future and organization. All errors and omissions are of course mine and are the result of my bad understanding. I also owe many thanks to all the people who develop, maintain and distribute the TEX system and make it freely available to us researchers and academics; this project was an opportunity to learn how to better use that typesetting system that keeps amazing me. I would also like to thank Jacques Crémer, Bruno Jullien, Jean Tirole, Hal Varian and other academics who inspired or guided my reflections. 1 CONTENTS 2 Contents 1 Introduction 4 2 The context of the (LA)TEX case study 8 2.1 Motivation . 8 2.2 Research Background . 8 2.3 Definitions of TEX: a software and a community . 10 2.3.1 TEX and LATEX ................................ 10 2.3.2 The software, its users and developers . 10 2.3.3 The software, its developers’ groups and support institutions . 11 2.4 An history of (LA)TEX................................. 12 2.4.1 The first phase: building the program and distributing it. 13 2.4.2 The second phase: taking a life of its own . 15 2.4.3 The third phase: going beyond (LA)TEX ................... 15 2.5 TEX, an Open Source Software Project? . 16 2.5.1 TEX’s license terms . 16 2.5.2 The organisation of TEX’s development . 17 2.6 A reference point: Linux. 17 3 Some preliminary findings. 19 3.1 The output: The characteristics of the code and its quality. 19 3.1.1 The importance of the initial coding of the software for its future. 19 3.1.2 The impact of the OS software on welfare and innovation. Its quality seen from various point of views. 20 3.2 The process. 22 3.2.1 The dynamics of the project and its limits. 22 3.2.2 Leadership . 25 3.3 The framework: The TEX rules and culture and how it evolved. 28 4 Conclusion: Work to be done. 30 A Glossary 33 A.1 Projects and programs . 33 A.1.1 TEX...................................... 33 A.1.2 TEX1.0, TEX2.0 and TEX3.0 . 34 A.1.3 LATEX, LATEX2.09, LATEX 2ε,LATEX3 . 35 A.1.4 eTEX ..................................... 36 A.1.5 NTS: a New Typesetting System. 36 A.1.6 Omega . 36 A.1.7 pdfTEX .................................... 37 A.1.8 AMSTEX................................... 37 A.1.9 ConTEXt ................................... 37 A.1.10 Web2c . 37 A.1.11 preview-LATEX ................................ 38 A.1.12 BibTEX.................................... 38 A.2 Other typesetting systems . 38 LIST OF FIGURES 3 A.2.1 Derived commercial systems: PCTEX, MicroTEX, Scientific Word by Mc- Kichan Software, Y&Y, TEXtures by Blue Sky Research,... 38 A.2.2 Derived open-source systems: TEXMacs, LyX... and interfaces: WinShell, WinEdt... 38 A.2.3 Concurrent typesetting systems: TROFF/NROFF, Scribe, Script... 39 A.2.4 Competing typesetting systems: Adobe’s InDesign, QuarkXPress, 3B2, Framemaker, Word... 39 A.3 Infrastructure . 39 A.3.1 The main (LA)TEX distributions . 39 A.3.2 TEX Directory Structure . 40 A.3.3 CTAN . 40 A.3.4 TUG . 41 A.3.5 AMS ..................................... 41 A.3.6 TUGboat . 41 A.3.7 LUG . 42 A.3.8 LPPL . 42 A.3.9 TEX newsgroups . 42 A.4 TEX related terms . 44 A.4.1 TEX implementation . 44 A.4.2 The Errors of TEX .............................. 44 A.4.3 TAOCP . 44 A.4.4 (LA)TEX.................................... 45 A.4.5 tex.web . 45 A.4.6 plain.tex . 45 A.4.7 Core LATEX .................................. 45 A.4.8 TRIP tests . 45 A.4.9 The bug report filter system . 45 A.5 Programming and OS related terms . 46 A.5.1 Programming languages: Pascal, WebPascal, C, Java . 46 A.5.2 WEB and literate programming . 46 A.5.3 Monolithic, modular and object oriented programming . 46 A.5.4 Macros and primitives . 47 A.5.5 The free/open source licenses: GPL, BSD, Debian guidelines, FSF . 47 A.6 Typesetting and electronic publishing . 47 A.6.1 The WYSIWYG controversy . 49 A.6.2 The web document formats: html, sgml, xml . 49 A.6.3 The document sharing formats: DVI, PDF, PostScript... 49 B A chronology 50 List of Figures 1 The bugs of TEX.................................... 24 2 The monthly posting to TEX-related newsgroups. 24 3 TUG’s revenues and membership. 27 1 INTRODUCTION 4 1 Introduction This is a case study of TEX, a typesetting software that was developed by Donald E. Knuth in the late 70’s. Released with an open source license, it has become a reference in scientific publishing. TEX is now used to typeset and publish much of the world’s scientific literature in physics and mathematics. This case study is part of a wider effort by academics to understand the open-source phenomenon. That development model is similar to the organization of the production of knowledge in academia; there is no set organization with a hierarchy, but free collaboration that is coordinated spontaneously and winds up generating complex products that are the property of all who can understand its functioning. The case study was led by gathering qualitative data via interviews with TEX developers and quantitative data on the TEX community – the program’s code, the software that is part of the TEX distribution, the newsgroups dedicated to the software, and many other indicators of the evolution and activity in that open-source project. The case study is aimed at economists who want to develop models to understand and analyze the open-source phenomenon. It is also geared towards policy-makers who would like to encourage or regulate open-source, and towards open-source developers who wonder what are the efficient strategies to make an open-source project successful. The primary aim of this case study is to define the relationship between consumers and pro- ducers of a software product in an open-source (“OS”) organization; how can a product that was developed for a producer’s own use become of use to others. The case-study is inspired by the work of Hippel (2002) that underlines how, while the development of open-source software (“OSS”) may have own-use as their primary motivation, it is complemented by another, collective, process that reconciles private aims with the aims of the general public. (LA)TEX provides a good case study to illustrate that point, as its development was oriented from the beginning towards the end-user, and it was distributed under a liberal license that allowed developers to build commercial products from their work in developing the software. The open-source user/developer interface organization was set up very early, and worked alongside commercial ventures to popularize the TEX software. The study of the development of TEX thus provides an interesting sample of various strategies to bring open-source software development efforts to the market. The process by which software is popu- larized may be taken up by the developers who, to obtain a better product, must make it available to others so that they may contribute to its development, and must therefore take their needs into account. That process can also be taken up by a mediating organization, set up by users to exploit the work of the developers. That organization assumes the role that the marketer plays in the pro- prietary model of software development. The production and marketing of a product inside a firm are closely linked in a continuous feedback process; a product has no meaning other than the value it has on the market. The open-source phenomenon, as seen through this case study, disjoins the production and the marketing side of software development; the productive activity of developers is not directed towards the market, but rather towards the fulfilment of private needs, while the market appropriates the result of that independent productive activity and transforms it to make it available to the general public. The analysis of the coordination between developers and users in an OS project is analyzed in more details in another paper (Gaudeul (2003b)) that is not included in the thesis. The present paper mainly deals with other matters: By examining the raw output of the project – the software’s code and its evolution, the stages in the development of the core of TEX are delineated: there is a ‘breaking’ point in the development where a code that favored early development and usability of the software becomes an impediment to its further, independent, development into new applica- tions and for new types of users. By looking at the process by which that code was produced – the project’s functioning – the constant clash between a logic of centralization of the contributions and 1 INTRODUCTION 5 of competition between development initiatives is underlined. The independent development initia- tives must be centralized so as to make them available to all, developers and users. However, there are cases where it is not possible to make a choice between two incompatible ideas, which leads to the choice being made later, based on the ensuing compared popularity of the two competing devel- opment strands.
Recommended publications
  • Latex on Windows
    LaTeX on Windows Installing MikTeX and using TeXworks, as described on the main LaTeX page, is enough to get you started using LaTeX on Windows. This page provides further information for experienced users. Tips for using TeXworks Forward and Inverse Search If you are working on a long document, forward and inverse searching make editing much easier. • Forward search means jumping from a point in your LaTeX source file to the corresponding line in the pdf output file. • Inverse search means jumping from a line in the pdf file back to the corresponding point in the source file. In TeXworks, forward and inverse search are easy. To do a forward search, right-click on text in the source window and choose the option "Jump to PDF". Similarly, to do an inverse search, right-click in the output window and choose "Jump to Source". Other Front End Programs Among front ends, TeXworks has several advantages, principally, it is bundled with MikTeX and it works without any configuration. However, you may want to try other front end programs. The most common ones are listed below. • Texmaker. Installation notes: 1. After you have installed Texmaker, go to the QuickBuild section of the Configuration menu and choose pdflatex+pdfview. 2. Before you use spell-check in Texmaker, you may need to install a dictionary; see section 1.3 of the Texmaker user manual. • Winshell. Installation notes: 1. Install Winshell after installing MiKTeX. 2. When running the Winshell Setup program, choose the pdflatex-optimized toolbar. 3. Winshell uses an external pdf viewer to display output files.
    [Show full text]
  • Arxiv:Cs/0107036V2 [Cs.SC] 31 Jul 2001
    TEXmacs interfaces to Maxima, MuPAD and REDUCE A. G. Grozin Budker Institute of Nuclear Physics, Novosibirsk 630090, Russia [email protected] Abstract GNU TEXmacs is a free wysiwyg word processor providing an excellent typesetting quality of texts and formulae. It can also be used as an interface to Computer Algebra Systems (CASs). In the present work, interfaces to three general-purpose CASs have been implemented. 1 TEXmacs GNU TEXmacs [1] is a free (GPL) word processor which typesets texts and mathematical formulae with very high quality (like LAT X), • E emphasizes the logical structure of a document rather than its appearance (like • LATEX), is easy to use and intuitive (like typical wysiwyg word processors), • arXiv:cs/0107036v2 [cs.SC] 31 Jul 2001 can be extended by a powerful programming language (like Emacs), • can include PostScript figures (as well as other figures which can be converted • to PostScript), can export LAT X, and import LAT X and html, • E E supports a number of languages based on Latin and Cyrillic alphabets. • It uses TEX fonts both on screen and when printing documents. Therefore, it is truly wysiwyg, with equally good quality of on-screen and printed documents (in contrast to LyX which uses X fonts on screen and calls LATEX for printing). There is a similar commercial program called Scientific Workplace (for Windows). TEXmacs can also be used as an interface to any CAS which can generate LATEX output. It renders LATEX formulae on the fly, producing CAS output with highest 1 typesetting quality (better than, e.g., Mathematica, which uses fixed-width fonts for formula output).
    [Show full text]
  • Developments in Technical Typesetting: Tex at the End of the Th Century
    A Century of Science Publishing E.H. Fredriksson (Ed.) IOS Press, Chapter Developments in Technical Typesetting: TeX at the End of the th Century Barbara Beeton Editor, TUGboat, the Communications of the TeX Users Group Introduction The composition of mathematical and technical material has traditionally been considered “penalty copy”, because of both the large number of special sym- bols required, and the complicated arrangement of these symbols on the page. While careful exposition has always been a valued skill for the mathematician or scientist, the tools were not available to allow authors to complete the presentation until relatively recently. The machinery has now come together: a desktop or portable computer; a text editor; an input language that is reasonably intuitive to a scientific author; a composition program that “understands” what mathematical notation is supposed to look like; a laser printer with a resolution high enough to print even very small symbols clearly. The composition engine is TeX, by Donald Knuth of Stanford University. This tool, originally developed specifically to pro- duce the second edition of Knuth’s The Art of Computer Programming, Volume , has been adopted by mathematicians, physicists, and other scientists for their own use. A number of scientific and technical publishers accept electronic manuscripts prepared with TeX and insert them directly into their production flow, while other publishers use TeX as a back end, continuing to accept and process copy in the tra- ditional manner. TeX manuscripts are circulated in electronic form by their authors in e-mail and posted into preprint archives on the World Wide Web; they are portable and durable — a new edition of a work need not be typed from scratch, but can be modified from the file of the previous edition.
    [Show full text]
  • Texworks: Lowering the Barrier to Entry
    TEXworks: Lowering the barrier to entry Jonathan Kew 21 Ireton Court Thame OX9 3EB England [email protected] 1 Introduction The standard TEXworks workflow will also be PDF-centric, using pdfT X and X T X as typeset- One of the most successful TEX interfaces in recent E E E years has been Dick Koch's award-winning TeXShop ting engines and generating PDF documents as the on Mac OS X. I believe a large part of its success has default formatted output. Although it will still be been due to its relative simplicity, which has invited possible to configure a processing path based on new users to begin working with the system with- DVI, newcomers to the TEX world need not be con- out baffling them with options or cluttering their cerned with DVI at all, but can generally treat TEX screen with controls and buttons they don't under- as a system that goes directly from marked-up text stand. Experienced users may prefer environments files to ready-to-use PDF documents. T Xworks includes an integrated PDF viewer, such as iTEXMac, AUCTEX (or on other platforms, E based on the Poppler library, so there is no need WinEDT, Kile, TEXmaker, or many others), with more advanced editing features and project man- to switch to an external program such as Acrobat, agement, but the simplicity of the TeXShop model xpdf, etc., to view the typeset output. The inte- has much to recommend it for the new or occasional grated viewer also allows it to support source $ user.
    [Show full text]
  • R Course for the Nsos in the Arab Countries Part I: Introduction
    R Course for the NSOs in the Arab countries Part I: Introduction Valentin Todorov1 1United Nations Industrial Development Organization, Vienna 18-20 May 2015 Todorov (UNIDO) R Course for the NSOs in the Arab countriesPart I: Introduction18-20 May 2015 1 / 1 Outline Todorov (UNIDO) R Course for the NSOs in the Arab countriesPart I: Introduction18-20 May 2015 2 / 1 About R Outline Todorov (UNIDO) R Course for the NSOs in the Arab countriesPart I: Introduction18-20 May 2015 3 / 1 About R What is R • R is a language and environment for statistical computing and graphics • R is based on the S language originally developed by John Chambers and colleagues at AT&T Bell Labs in the late 1970s and early 1980s • R (sometimes called "GNU S\ ) is free open source software licensed under the GNU general public license (GPL 2) • R was created by Robert Gentleman and Ross Ihaka at the University of Auckland as a test bed for trying out some ideas in statistical computing • R is formally known as The R Project for Statistical Computing: http://www.r-project.org Todorov (UNIDO) R Course for the NSOs in the Arab countriesPart I: Introduction18-20 May 2015 4 / 1 About R The R project • The R Project is an international collaboration of researchers in statistical computing. • There are roughly 20 members of the "R Core Team\ who maintain and enhance R. • Releases of the R environment are made through the CRAN (comprehensive R archive network) twice per year. • The software is released under a "free software\ license, which makes it possible for anyone to download and use it.
    [Show full text]
  • Simplifying the Scientific Writing and Review Process with Sciflow
    Future Internet 2010, 2, 645-661; doi:10.3390/fi2040645 OPEN ACCESS future internet ISSN 1999-5903 www.mdpi.com/journal/futureinternet Article Simplifying the Scientific Writing and Review Process with SciFlow Frederik Eichler and Wolfgang Reinhardt ? Computer Science Education Group, University of Paderborn, Fuerstenallee 11, 33102 Paderborn, Germany; E-Mail: [email protected] ? Author to whom correspondence should be addressed; E-Mail: [email protected]; Tel.: +49-5251-60-6603; Fax: +49-5251-60-6336. Received: 13 September 2010; in revised form: 30 November 2010 / Accepted: 2 December 2010 / Published: 6 December 2010 Abstract: Scientific writing is an essential part of a student’s and researcher’s everyday life. In this paper we investigate the particularities of scientific writing and explore the features and limitations of existing tools for scientific writing. Deriving from this analysis and an online survey of the scientific writing processes of students and researchers at the University of Paderborn, we identify key principles to simplify scientific writing and reviewing. Finally, we introduce a novel approach to support scientific writing with a tool called SciFlow that builds on these principles and state of the art technologies like cloud computing. Keywords: scientific writing; survey; word processors; cloud computing 1. Introduction Scientific writing is an essential part of a student’s and researcher’s life. Depending on the particular field of study, papers have to be written and written assignments have to be handed in. As the end of studies approaches, most students are asked to prove their ability to work in a scientific manner by writing a thesis.
    [Show full text]
  • Computer Engineering Program
    ABET SELF STUDY REPORT for the Computer Engineering Program at Texas A&M University College Station, Texas July 1, 2010 CONFIDENTIAL The information supplied in this Self-Study Report is for the confidential use of ABET and its authorized agents, and will not be disclosed without authorization of the institution concerned, except for summary data not identifiable to a specific institution. ABET Self-Study Report for the Computer Engineering Program at Texas A&M University College Station, TX June 28, 2010 CONFIDENTIAL The information supplied in this Self-Study Report is for the confidential use of ABET and its authorized agents, and will not be disclosed without authorization of the institution concerned, except for summary data not identifiable to a specific institution. CONTENTS Background Information 3 .A Contact Information . .3 .B Program History . .3 .C Options . .4 .D Organizational Structure . .4 .E Program Delivery Modes . .6 .F Deficiencies, Weaknesses or Concerns from Previous Evaluation(s) and the Ac- tions taken to Address them . .6 .F.1 Previous Institutional Concerns . .7 .F.2 Previous Program Concerns . .9 I Criterion I: Students 11 I.A Student Admissions . 11 I.B Evaluating Student Performance . 12 I.C Advising Students . 14 I.D Transfer Students and Transfer Courses . 17 I.E Graduation Requirements . 18 I.F Student Assistance . 19 I.G Enrollment and Graduation Trends . 20 II Criterion II: Program Educational Objectives 23 II.A Mission Statement . 23 II.B Program Educational Objectives . 25 II.C Consistency of the Program Educational Objectives with the Mission of the Insti- tution . 25 II.D Program Constituencies .
    [Show full text]
  • DE-Tex-FAQ (Vers. 72
    Fragen und Antworten (FAQ) über das Textsatzsystem TEX und DANTE, Deutschsprachige Anwendervereinigung TEX e.V. Bernd Raichle, Rolf Niepraschk und Thomas Hafner Version 72 vom September 2003 Dieser Text enthält häufig gestellte Fragen und passende Antworten zum Textsatzsy- stem TEX und zu DANTE e.V. Er kann über beliebige Medien frei verteilt werden, solange er unverändert bleibt (in- klusive dieses Hinweises). Die Autoren bitten bei Verteilung über gedruckte Medien, über Datenträger wie CD-ROM u. ä. um Zusendung von mindestens drei Belegexem- plaren. Anregungen, Ergänzungen, Kommentare und Bemerkungen zur FAQ senden Sie bit- te per E-Mail an [email protected] 1 Inhalt Inhalt 1 Allgemeines 5 1.1 Über diese FAQ . 5 1.2 CTAN, das ‚Comprehensive TEX Archive Network‘ . 8 1.3 Newsgroups und Diskussionslisten . 10 2 Anwendervereinigungen, Tagungen, Literatur 17 2.1 DANTE e.V. 17 2.2 Anwendervereinigungen . 19 2.3 Tagungen »geändert« .................................... 21 2.4 Literatur »geändert« .................................... 22 3 Textsatzsystem TEX – Übersicht 32 3.1 Grundlegendes . 32 3.2 Welche TEX-Formate gibt es? Was ist LATEX? . 38 3.3 Welche TEX-Weiterentwicklungen gibt es? . 41 4 Textsatzsystem TEX – Bezugsquellen 45 4.1 Wie bekomme ich ein TEX-System? . 45 4.2 TEX-Implementierungen »geändert« ........................... 48 4.3 Editoren, Frontend-/GUI-Programme »geändert« .................... 54 5 TEX, LATEX, Makros etc. (I) 62 5.1 LATEX – Grundlegendes . 62 5.2 LATEX – Probleme beim Umstieg von LATEX 2.09 . 67 5.3 (Silben-)Trennung, Absatz-, Seitenumbruch . 68 5.4 Seitenlayout, Layout allgemein, Kopf- und Fußzeilen »geändert« . 72 6 TEX, LATEX, Makros etc. (II) 79 6.1 Abbildungen und Tafeln .
    [Show full text]
  • El Manual De GNU TEXMACS
    El manual de GNU TEXMACS Índice 1. Iniciar . 9 1.1. Convenciones para este manual . 9 1.2. Congurar TEXMACS . 9 1.3. Crear, guardar y cargar documentos . 10 1.4. Imprimir documentos . 10 2. Escribir documentos sencillos . 11 2.1. Generalidades para teclear de texto . 11 2.2. Tecleando texto estructurado . 11 2.3. Etiquetas basadas en contenido . 12 2.4. Listas . 12 2.5. Entornos . 13 2.6. Aspectos de presentación . 14 2.7. El sistema de selección de fuentes . 14 2.8. Dominando el teclado . 15 2.8.1. Reglas generales de prejos . 15 2.8.2. Algunos atajos de teclado fundamentales . 15 2.8.3. Atajos de teclado para el modo texto . 16 2.8.4. Comandos híbridos y simulación LATEX . 16 2.8.5. Objetos dinámicos . 16 2.8.6. Personalización del teclado . 17 3. Fórmulas matemáticas . 19 3.1. Principales constructos matemáticos . 19 3.2. Tecleando símbolos matemáticos . 20 3.3. Tecleando operadores grandes . 20 3.4. Teclear delimitadores grandes . 21 3.5. Acentos matemáticos anchos . 22 4. Material tabular . 23 4.1. Creando tablas . 23 4.2. El modo para dar formato . 23 4.3. Especicando el alineamiento de la celda y la tabla . 24 4.4. Especicando el tamaño de la celda y la tabla . 24 4.5. Bordes, acolchado y color de fondo . 25 4.6. Características avanzadas de la tabla . 25 5. Links and automatically generated content . 27 5.1. Creating labels, links and references . 27 5.2. Inserting images . 27 5.3. Generating a table of contents . 28 5.4.
    [Show full text]
  • Software Livre Para Engenharia
    SSOOFFTTWWAARREE LLIIVVRREE PPAARRAA EENNGENHGENHAARRIAIA AdAdiillssoonn JJ.. ddee AsAsssiiss [email protected] I Semana Acadêmica da UFU 28 de maio de 2004 Universidade Federal de Uberlândia Faculdade de Engenharia Química Núcleo de Modelagem, Controle e Otimização de Processos TERMINTERMINOOLLOOGGIAIA Software em Domínio Público Software em domínio público é software sem copyright. Alguns tipos de cópia, ou versões modificadas, podem não ser livres porque o autor permite que restrições adicionais sejam impostas na redistribuição do original ou de trabalhos derivados. Software Semi-livre Software semi-livre é software que não é livre, mas é concedida a permissão para que indivíduos o usem, copiem, distribuam e modifiquem, incluindo a distribuição de versões modificadas, desde que o façam sem o propósito de auferir lucros. Exemplos de software semi-livre são as primeiras versões do Internet Explorer da Microsoft, algumas versões dos browsers da Netscape, e o StarOffice. Softw are liv re p ara engenha ria I Sem ana Acadêm ica da UFU TERMINTERMINOOLLOOGGIAIA Freeware O termo freeware não possui uma definição amplamente aceita mas é usado com programas que permitem a redistribuição mas não a modificação, e seu código fonte não é disponibilizado. Estes programas não são software livre. Shareware Shareware é o software disponibilizado com a permissão para que seja redistribuído, mas a sua utilização implica no pagamento pela sua licença. Geralmente, o código fonte não é disponibilizado e portanto modificações são impossíveis. Softw are liv re p ara engenha ria I Sem ana Acadêm ica da UFU TERMINTERMINOOLLOOGGIAIA Software Proprietário Software proprietário é aquele cuja cópia, redistribuição ou modificação são em alguma medida proibidos pelo seu proprietário.
    [Show full text]
  • OFFICE the Text in the Main Editing Window and Italicize It
    ic or bold to the text you type in the Insert Endnote window, so if you W'ant to itali- cize a book title in a note, you have to insert the note with no italics, then edit OFFICE the text in the main editing window and italicize it. EasySpreadsheet handled our complex sample worksheets reasonably well, although it did not even try to open the charts. Our 4MB Microsoft Excel spread- sheet opened slowly but accurately. Easy0ffice7.0 labeled Filel and File2. Each of those EasySpreadsheet makes life simple for be- E-Press Corp, www.e-press.com. menus contains more than 20 items, in- ginners by displaying a vortical Totals ••COO cluding PDF and HTML export and items column on the right edge, showing the EasyOffice 7.0 packs more applications that store and search backup, grandfather, sums of all rows, and a horizontal Totals and utilities into one freeware package and great-grandfather versions of your column at the foot, with the sums of all than you'll find in any high-priced suite. A files—features you won't find in better- columns, it supports about 125 functions, <?6MB installer expands into a word known suites. Some menu items have but none as advanced as pivot tables, pn'cessor, spreadsheet, calculator, picture shortcut keys that let you access them by array formulas, conditional formatting, fil- editor. PDr editor, presentation program, typing an underlined letter; others are ac- teritig, and macros. You cannot customize and e-mail client. EasyOffice also contains the built-in number several applications that no other office formats.
    [Show full text]
  • Miktex Manual Revision 2.0 (Miktex 2.0) December 2000
    MiKTEX Manual Revision 2.0 (MiKTEX 2.0) December 2000 Christian Schenk <[email protected]> Copyright c 2000 Christian Schenk Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the con- ditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another lan- guage, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the Free Software Foundation. Chapter 1: What is MiKTEX? 1 1 What is MiKTEX? 1.1 MiKTEX Features MiKTEX is a TEX distribution for Windows (95/98/NT/2000). Its main features include: • Native Windows implementation with support for long file names. • On-the-fly generation of missing fonts. • TDS (TEX directory structure) compliant. • Open Source. • Advanced TEX compiler features: -TEX can insert source file information (aka source specials) into the DVI file. This feature improves Editor/Previewer interaction. -TEX is able to read compressed (gzipped) input files. - The input encoding can be changed via TCX tables. • Previewer features: - Supports graphics (PostScript, BMP, WMF, TPIC, . .) - Supports colored text (through color specials) - Supports PostScript fonts - Supports TrueType fonts - Understands HyperTEX(html:) specials - Understands source (src:) specials - Customizable magnifying glasses • MiKTEX is network friendly: - integrates into a heterogeneous TEX environment - supports UNC file names - supports multiple TEXMF directory trees - uses a file name database for efficient file access - Setup Wizard can be run unattended The MiKTEX distribution consists of the following components: • TEX: The traditional TEX compiler.
    [Show full text]