Do Open Source Developers Respond to Competition? the Case Study

Total Page:16

File Type:pdf, Size:1020Kb

Do Open Source Developers Respond to Competition? the Case Study Review of Network Economics Vol.6, Issue 2 – June 2007 Do Open Source Developers Respond to Competition? The Case Study ALEX GAUDEUL * School of Economics, University of East Anglia Abstract This paper traces the history of , the open source typesetting program. was an early and very successful open source project that imposed its standards in a particularly competitive environment and inspired many advances in the typesetting industry. Developed over three decades, came into competition with a variety of open source and proprietary alternatives. I argue from this case study that open source developers derive direct and indirect network externalities from the use of their software by others and must therefore consider non-developers’ needs to make their software more attractive to a broader audience and more competitive with proprietary alternatives. 1 Introduction This paper offers an analysis of the competition between open source (OS) and proprietary software systems through a study of the long-term development dynamics of the typesetting software.1 The project was launched in 1978 under an open source license, long before other better known OS projects such as Linux. This case study thus draws on a long history. In this article, I focus on the dynamics of competition between OS and proprietary typesetting software. I analyze the multi-period strategies by which they borrowed from each other, complemented each other and reacted to advances on the competing side. A variety of developers developed applications, proprietary or otherwise, for , an open source typesetting platform. On one side, users chose whether to adopt as their * School of Economics, University of East Anglia, Norwich NR4 7TJ United Kingdom. E-mail: [email protected]. 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 MacKichan, B. Mahesh, Frank Mittelbach, Oren Patashnik, Simon Pepping, John Plaice, Fabrice Popineau, Sebastian Rahtz, Denis Roegel, Chris Rowley, Joachim Schröd, Karel Skoupý, Hàn Thế Thành and all other participants in the project whom I met and interviewed. Special thanks are due to Hans Hagen for his help in editing this paper. I would also like to thank Jacques Crémer, Bruno Jullien, Jean Tirole and Hal Varian for their advice, and an anonymous referee for helpful comments. The support of the CNRS and of the ESRC Centre for Competition Policy is gratefully acknowledged. All errors and omissions are mine. 1 is the core of the typesetting program while most users of use the set of macros. Both the terms and are used to designate the whole of the project. 239 Review of Network Economics Vol.6, Issue 2 – June 2007 typesetting platform, or competing proprietary platforms, and if they chose , also chose what specific applications to use. On the other side, developers chose whether to develop for the platform or for another platform, and if they chose , chose under what license they would release their contributions. This depended on the nature of the application they wished to develop. It also depended on the presence of and ease of access to other development platforms in the proprietary world. Decisions of users and developers were complementary: the diffusion of was closely dependent on the dynamics of its development and on the technological changes that happened outside of the world. OS developers and users recognized this; they formed coalitions and took strategic decisions to influence the direction of the development of . This paper illustrates a simple basic hypothesis: while OS developers improve open source software (OSS) for their own purposes, in order to better fulfil their needs, they also derive benefits from the use of their software by others (network externalities). This encourages them to broaden the software’s user base by providing features that may be of no direct use to themselves or that may be low on their own priority lists. For example, they work to facilitate the initiation into the use of the software, or to make the software more accessible and easy to use. They also want to maximize the benefit of network externalities by agreeing on and following a variety of standards in the development, licensing and maintenance of their contributions to the software. They want the software to behave the same way on any user’s machine, they want new contributions to fit guidelines so they can be integrated seamlessly into the software distribution and they want this “official” software distribution to be used by all. Those objectives are only achieved by agreeing with others on how the software should behave and by coordinating the ensuing development efforts with other developers. Developers have to balance their need for independence in their development decisions with the need to coordinate with other developers and they have to be receptive to the needs of users. OS developers also have to take account of the proprietary offering and negotiate the positioning of their software in the market in order to maintain or increase their user base. Not only do they have to think in strategic terms but they also have to impose a level of discipline and a sense of direction onto the development of the software, which is more difficult. This is the purpose of OSS organizations. Those organizations provide a platform where users can express their needs and where developers can express their ideas and goals. Users and developers make sense together of the software’s position in its development area and negotiate development objectives. This process give rise to complex organizational dynamics whereby developers position themselves, form coalitions, try to convince others by appealing to shared interests or the common good, etc. The basic hypothesis according to which developers and users consider network effects in their development and consumption decisions is used to explain a number of patterns in the development of the development platform. The next section is an analysis of the existing literature on the topic. 2 Literature review This paper is a study of the competition in the provision of a potentially excludable but non-rival good, software. When a good is non-excludable, then it is generally assumed it has to be publicly provided. If it is made excludable, by putting it under copyright for 240 Review of Network Economics Vol.6, Issue 2 – June 2007 example, then it is assumed it is privately supplied in the same way as most standard goods. However, the situation in the software industry is different: some software is provided under open source licenses,2 while some other software is provided under proprietary licenses. This is a mixed industry where for-profits and nonprofits coexist (Kuan, 2001). Open source software is privately provided through voluntary contributions (Bergstrom, 1986). OSS organizations differ from other nonprofits in that OSS production is not usually publicly subsidized, it does not rely in any significant way on private donations for its development, and its provision is not directed by the State or any other formal institutions or interest group. Open source projects are the result of the work of individually motivated developers and it is difficult for any institution to direct their development. This paper extends the literature on public goods in the specific context of open source provision by examining the dynamics of the private provision of a public good in a competitive setting. How does an OS organization react to competition, both from other OS projects and from proprietary projects? How does an open source organization adapt to changes in its market environment? How do commercial organizations adapt to the presence of OS competition? Will each type of organization specialize in specific areas of software development? Will they serve different types of customers or develop different software parts? Are there exchanges and synergies between each type of organization? I will build on the existing literature on OS methods of production, which deals principally with (1) the organization of development and (2) the incentives of OS developers. I will then be able to present (3) the literature on competition between OS and proprietary organizations. 2.1 Organization: Far from being the “bazaar” evoked in Raymond (2001), open source development is hierarchic and subject to peer review. Small groups of developers contribute most of the “core” code. Other developers provide support for specific systems or functionalities while some other volunteers provide user support and help maintain the infrastructure of the project (Mockus, 2005; and Lakhani, 2002).3 Development is done module by module in an incremental way, with each module a relatively independent part of the complete software. Work is thus fragmented to the individual or small team level, with limited need for central coordination (Krogh, 2003a). Central coordination is done by the lead developers, who also contribute the most to the software’s development (see, for example, Kogut, 2001, Table 3) and are able to influence its course (see, for example,e Bezroukov, 1999 on the role of the leader and conflicts between developers). 2.2 Incentives A developer who develops software that is under OS licensing terms has two sets of motives (Lakhani, 2005). One set of motives is own-use or own-enjoyment; she wants to develop software that she needs or enjoys developing (Hippel, 2005). The other set of 2 OS developers keep the copyright over their contributions to an OS project, but are limited in its use; it can be asserted only to prevent others from using their contribution without acknowledgment (Berkeley licenses (BSD)) or from using it as part of proprietary software (GNU Public License (GPL)). 3 Fitzgerald, 2001; Fitzgerald, 2002; and Krogh, 2003b introduce special issues on this topic.
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]
  • 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]
  • 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]
  • Design Decisions for a Structured Front End to LATEX Documents
    Design decisions for a structured front end to LATEX documents Barry MacKichan MacKichan Software, Inc. barry dot mackichan at mackichan dot com 1 Logical design Procedural Scientific WorkPlace and Scientific Word are word processors that have been designed from the start to TeX handle mathematics gracefully. Their design philos- PostScript ophy is descended from Brian Reid’s Scribe,1 which emphasized the separation of content from form and 2 was also an inspiration for LATEX. This logical de- sign philosophy holds that the author of a document should concern him- or herself with the content of the document, and with identifying the role that each bit of text plays, such as a header, a footnote, Structured or a quote. The details of formatting should be ig- Unstructured nored by the author, and handled instead by a pre- defined (or custom) style specification. LaTeX There are several very compelling reasons for the separation of content from form. • The expertise of the author is in the content; PDF the expertise of the publisher is in the presen- tation. Declarative • Worrying and fussing about the presentation is wasted effort when done by the author, since Thus, PostScript is a powerful programming the publisher will impose its own formatting on language, but it was later supplemented by PDF, the paper. which is not a programming language, but instead contains declarations of where individual characters • Applying formatting algorithmically is the eas- are placed. PDF is not structured, but Adobe has iest way to assure consistency of presentation. been adding a structural overlay. LATEX is quite • When a document is re-purposed it can be re- structured, but it still contains visible signs of the formatted automatically for its new purpose.
    [Show full text]
  • Latex in Twenty Four Hours
    Plan Introduction Fonts Format Listing Tabbing Table Figure Equation Bibliography Article Thesis Slide A Short Presentation on Dilip Datta Department of Mechanical Engineering, Tezpur University, Assam, India E-mail: [email protected] / datta [email protected] URL: www.tezu.ernet.in/dmech/people/ddatta.htm Dilip Datta A Short Presentation on LATEX in 24 Hours (1/76) Plan Introduction Fonts Format Listing Tabbing Table Figure Equation Bibliography Article Thesis Slide Presentation plan • Introduction to LATEX Dilip Datta A Short Presentation on LATEX in 24 Hours (2/76) Plan Introduction Fonts Format Listing Tabbing Table Figure Equation Bibliography Article Thesis Slide Presentation plan • Introduction to LATEX • Fonts selection Dilip Datta A Short Presentation on LATEX in 24 Hours (2/76) Plan Introduction Fonts Format Listing Tabbing Table Figure Equation Bibliography Article Thesis Slide Presentation plan • Introduction to LATEX • Fonts selection • Texts formatting Dilip Datta A Short Presentation on LATEX in 24 Hours (2/76) Plan Introduction Fonts Format Listing Tabbing Table Figure Equation Bibliography Article Thesis Slide Presentation plan • Introduction to LATEX • Fonts selection • Texts formatting • Listing items Dilip Datta A Short Presentation on LATEX in 24 Hours (2/76) Plan Introduction Fonts Format Listing Tabbing Table Figure Equation Bibliography Article Thesis Slide Presentation plan • Introduction to LATEX • Fonts selection • Texts formatting • Listing items • Tabbing items Dilip Datta A Short Presentation on LATEX
    [Show full text]
  • Taft to the Negroes
    " A u 1 I iH ifl M M v ,1 ii U. B. WEATHER BUREAU, September 15. Last 24 Hours Rainfall, .05. :! SUGAR. 96 Degree Test Centrifugals, 3.90c Per Ton, $78.00. Temperature, Max. 82; 71. Weather, cloudy. Mia. 83 Analysis Beets, 9s. 64. Per Ton, $79.80. ESTABLISHED JULY 2, 1856. I 8145. HONOLULU, HAWAII TERRITORY, WEDNESDAY, SEPTEMBER VOL. XLVIIL, NO. 16, 1908. PRICE FIVE CENTS ATM SON HARD AT RKANSAS DEMOCRATS r WORK TO PUT PARTY ROLL UP OF ? V. il N FIGHTING TRI SIXTY FIVE THOUSAND tl 1 f;-- looking After a Good Campaign Committee Portland, Ore., Goes Republican by a Good I 4 and a Republican Senate Gossip on the MarginNew York Democrats t Advertiser Photo. Harmonize Chas. Clark. J. D. Holt. L. L. McCandless. Rialto About Candidates. Hughes Renominated. ft WHAT CAN THEY BE TALKING ABOUT? a "I am interested in seeing the have removed from the active zone of BROKE IIP TIE COLLEGE OF (Associated Press Cablegrams.) party get a campaign com- politics and it was further thought that he would retire from official life at LITTLE ROCK, Arkansas, September 16. The Democrats mittee that will inspire confidence the end of his regime atthe head of have carried aniong all classes of voters in the Re- the police department. The Sheriff an- HAWAII OPEN Arkansas by 65,000 majority. publican party," said Chairman A. L. nounced several months ago that he C Atkinson of the Republican Terri- would not be a candidate for Sheriff. nijoni The following statistics of previous elections are from the World Almanac: About that .
    [Show full text]
  • Open Architecture for Multilingual Parallel Texts M.T
    Open architecture for multilingual parallel texts M.T. Carrasco Benitez Luxembourg, 28 August 2008, version 1 1. Abstract Multilingual parallel texts (abbreviated to parallel texts) are linguistic versions of the same content (“translations”); e.g., the Maastricht Treaty in English and Spanish are parallel texts. This document is about creating an open architecture for the whole Authoring, Translation and Publishing Chain (ATP-chain) for the processing of parallel texts. 2. Summary 2.1. Next steps The next steps should be: • Administrative organisation: create a coordinating organisation and approach the existing organisations that might cooperate; e.g., IETF, LISA, OASIS, W3C. • Public discussion: with an emailing list (or similar) to reach a rough consensus, in particular on aspects such as the required specifications. Organise the necessary meeting(s). • Tools: implement some tools. This might be done simultaneously with the public discussion to better illustrate the approach and support the discussion. 2.2. Best approaches To obtain the best quality, speed and the lowest possible cost (QSC) in the production of parallel texts, one should aim for: • Generating all the linguistic versions ready for publication, from linguistic resources. Probably one of the best approaches. • Seamless ATP-chain implementations. • Authoring: Computer-aided authoring (CAA) tools with a controlled authoring environment; it should deliver source texts prepared for translation. • Translation: Computer-aided translation (CAT) tools to allow translators to focus only in translating and unburden translators from auxiliary tasks such as formatting. These tools should have functionalities such as side-by-side editor and the re-use of previous translations. • Publishing: Computer-aided publishing (CAP) tools to minimise human intervention.
    [Show full text]
  • Get Started with Scientific Workplace
    Get started with Scientific Workplace What is Scientific WorkPlace? Scientific WorkPlace is a fully featured technical word processing program. Additionally, it can perform symbolic computation and prepare material for publishing on the World Wide Web. Availability Scientific WorkPlace version 5.5 is provided on all public room computers at LSE and can be run on any machine at LSE that is connected to the network. Starting Scientific WorkPlace On a public room machine: Click Start | All Programs | Specialist and Teaching Software | Scientific WorkPlace For other machines, ask your IT Support Team to install Scientific WorkPlace 5.5. In this case there will be probably an icon on the desktop from which you can start the program. Using Scientific WorkPlace Comprehensive help on using Scientific WorkPlace is available on-line via the Help menu. Beginners can start from the Help Menu, Contents, Take a Tour for a general introduction. This can be followed with Learn the Basics (also from Help, Contents) which leads to tutorials to be followed on-line and the online version of Getting Started, the Manufacturer's manual. Instructions for using Beamer, a package for making slides, are in C:\SWP55\SWSamples\PackageSample- beamer.tex (If this file is missing, then Beamer is not installed on the computer you are using.) File types The main file type used by Scientific WorkPlace is tex for documents. Please Note: There may be a file association for Scientific WorkPlace in the LSE implementation, so that double- clicking on files of type tex will start Scientific WorkPlace; however, the file association may be to a different program.
    [Show full text]
  • Classicthesis.Pdf
    andré miede & ivo pletikosic´ ACLASSICTHESISSTYLE [ June 3, 2018 at 15:29 – classicthesis v4.6 ] [ June 3, 2018 at 15:29 – classicthesis v4.6 ] ACLASSICTHESISSTYLE andré miede & ivo pletikosic´ An Homage to The Elements of Typographic Style June 2018 – classicthesis v4.6 [ June 3, 2018 at 15:29 – classicthesis v4.6 ] André Miede & Ivo Pletikosi´c: A Classic Thesis Style, An Homage to The Elements of Typographic Style, c June 2018 [ June 3, 2018 at 15:29 – classicthesis v4.6 ] Ohana means family. Family means nobody gets left behind, or forgotten. — Lilo & Stitch Dedicated to the loving memory of Rudolf Miede. 1939 – 2005 [ June 3, 2018 at 15:29 – classicthesis v4.6 ] [ June 3, 2018 at 15:29 – classicthesis v4.6 ] ABSTRACT Short summary of the contents in English. a great guide by Kent Beck how to write good abstracts can be found here: https://plg.uwaterloo.ca/~migod/research/beckOOPSLA.html ZUSAMMENFASSUNG Kurze Zusammenfassung des Inhaltes in deutscher Sprache. vii [ June 3, 2018 at 15:29 – classicthesis v4.6 ] [ June 3, 2018 at 15:29 – classicthesis v4.6 ] PUBLICATIONS This is just an early This might come in handy for PhD theses: some ideas and figures – and currently ugly – have appeared previously in the following publications: test! [1] Tobias Isenberg, André Miede, and Sheelagh Carpendale. “A Buffer Framework for Supporting Responsive Interaction in Information Visualization Interfaces.” In: Proceedings of the Fourth International Conference on Creating, Connecting, and Collaborating through Computing (C 5 2006). IEEE, 2006, pp. 262–269. isbn: 978- 0-7695-2563-1. [2] Ulrich Lampe, Markus Kieselmann, André Miede, Sebastian Zöller, and Ralf Steinmetz.
    [Show full text]
  • The Treasure Chest for Compatibility with Texpower and Seminar
    TUGboat, Volume 22 (2001), No. 1/2 67 the concept of pdfslide, but completely rewritten The Treasure Chest for compatibility with texpower and seminar. ifsym: in fonts Fonts with symbols for alpinistic, electronic, mete- orological, geometric, etc., usage. A LATEX2ε pack- age simplifies usage. Packages posted to CTAN jas99_m.bst: in biblio/bibtex/contrib “What’s in a name?” I did not realize that Jan Update of jas99.bst,modifiedforbetterconfor- Tschichold’s typographic standards lived on in the mity to the American Meteorological Society. koma-script package often mentioned on usenet (in LaTeX WIDE: in nonfree/systems/win32/LaTeX_WIDE comp.text.tex) until I happened upon the listing A demonstration version of an integrated editor for it in a previous edition of “The Treasure Chest”. and shell for TEX— free for noncommercial use, but without registration, customization is disabled. This column is an attempt to give TEX users an on- : LAT X2ε macro package of simple, “little helpers” going glimpse of the trove which is CTAN. lhelp E converted into dtx format. Includes common units This is a chronological list of packages posted with preceding thinspaces, framed boxes, start new to CTAN between June and December 2000 with odd or even pages, draft markers, notes, condi- descriptive text pulled from the announcement and tional includes (including EPS files), and versions edited for brevity — however, all errors are mine. of enumerate and itemize which allow spacing to Packages are in alphabetic order and are listed only be changed. in the last month they were updated. Individual files makecmds Provides commands to make commands, envi- / partial uploads are listed under their own name if ronments, counters and lengths.
    [Show full text]