DOCSLIB.ORG

A User's Guide to the Lout Document Formatting System

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A User's Guide to the Lout Document Formatting System A User’s Guide to the Lout Document Formatting System Jeffrey H. Kingston Version 3.40 June 2013 Copyright 1991, 2013 Jeffrey H. Kingston, School of Information Technologies, The University of Sydney 2006, Australia. ISBN 0 86758 9515. Preface This User’s Guide brings together in one document everything needed for the day-to-day use of Version 3 of the Lout document formatting system. There are three other documents describing Lout: the Expert’s Guide [5], which you need if you want to add new features to Lout; a journal paper on the design and implementation of Lout [3]; and a set of overhead transparencies [4]that cover much the same ground as this Guide. These documents are all distributed with the software. Lout is distributed free of charge under the GNU Public License. The primary source is ftp://ftp.it.usyd.edu.au/jeff/lout containing a gzipped tar file of the current version, and various other things including a PostScript version of this guide. The distribution contains source code, libraries,documentation, license, and installation instructions. A mailing list has been set up for discussion of all topics related to Lout. To subscribe (or unsubscribe), visit http://lists.nongnu.org/mailman/listinfo/lout-users After subscribing, to post an item send email to [email protected]; it will be forwarded to all subscribers via email. There is also a web site at http://savannah.nongnu.org/projects/lout. Lout began in 1984 as a research project into the design of a high-level language for document formatting. At that time my name for the subject was ‘document layout,’ and this terminology survives in the name ‘Lout’. The initial design was strongly influenced by Brian W. Kernighan and Lorinda L.Cherry’s eqn equation formatter [2], and also by Brian K.Reid’s Scribe system [9]. That research phase ended in October 1991 with the first public release. Since then the system has been steadily improved and extended. Optimal paragraph break- ing and automatic hyphenation were copied from Donald E. Knuth’s TEX system [6], and the optimal paragraph breaking algorithm was applied to the problem of producing optimal page breaks. The first implementations of horizontal galleys and optimal page breaking were by my student Gabor Inokai. Vincent Tan contributed the PDF back end. Ludovic Courtès contributed the @Math package and set up the current mailing list. ValeriyE. Ushakov smoothed the path for many people,by his contributionsto improving Lout’s robustness,and his tirelessmanagement of and responses to the Lout mailing list. The number of other people who have offered comments and suggestions to me is so great that it is quite out of my power to acknowledge them individu- ally. I hope that seeing their ideas adopted will be thanks enough. Jeffrey H. Kingston School of Information Technologies The University of Sydney 2006, Australia [email protected] Contents Preface .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ii Chapter 1. The Basics .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 1 1.1. Getting started .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 1 1.2. Objects, symbols, options, and lengths .. .. .. .. .. .. .. .. .. .. 3 1.3. Spaces and braces .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 5 1.4. Characters .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 7 1.5. The empty object .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 12 1.6. Fonts and font sizes .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 12 1.7. Headings .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 16 1.8. Starting a new line, paragraph, or page .. .. .. .. .. .. .. .. .. .. 17 1.9. Paragraph breaking .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 18 1.10. Line spacing .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 23 1.11. Hyphenation .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 23 1.12. Margin kerning .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 24 1.13. Underlining .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 24 1.14. Languages other than English .. .. .. .. .. .. .. .. .. .. .. .. 25 1.15. The current date and time .. .. .. .. .. .. .. .. .. .. .. .. .. 27 1.16. Superscripts and subscripts .. .. .. .. .. .. .. .. .. .. .. .. 28 1.17. Verbatim and piped text .. .. .. .. .. .. .. .. .. .. .. .. .. 28 1.18. Drop capitals .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 30 1.19. Alternative conventions for white space .. .. .. .. .. .. .. .. .. 31 Chapter 2. Documents With Structure .. .. .. .. .. .. .. .. .. .. .. .. 33 2.1. Displays .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 33 2.2. Lists .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 34 2.3. Footnotes and endnotes .. .. .. .. .. .. .. .. .. .. .. .. .. .. 40 2.4. Margin notes and arbitrary placement .. .. .. .. .. .. .. .. .. .. 43 2.5. Theorems, lemmas, corollaries, definitions, propositions, examples, and claims .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 45 2.6. Figures and tables .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 46 2.7. Large-scale structure: chapters, sections, etc. .. .. .. .. .. .. .. .. 50 2.8. Cross references and links .. .. .. .. .. .. .. .. .. .. .. .. .. 53 2.9. Tables of contents .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 57 2.10. Glossaries .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 58 2.11. Indexes .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 61 2.12. Multiple columns .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 69 2.13. Defining new symbols .. .. .. .. .. .. .. .. .. .. .. .. .. .. 69 Chapter 3. Types of Documents .. .. .. .. .. .. .. .. .. .. .. .. .. .. 72 3.1. Ordinary documents .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 72 3.2. Technical reports .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 76 3.3. Books .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 81 3.4. Overhead transparencies .. .. .. .. .. .. .. .. .. .. .. .. .. .. 89 3.5. Stand-alone illustrations .. .. .. .. .. .. .. .. .. .. .. .. .. .. 93 3.6. Plain text documents .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 95 3.7. PDF (Adobe Portable Document Format) documents .. .. .. .. .. .. 96 3.8. Organizing large documents .. .. .. .. .. .. .. .. .. .. .. .. .. 97 Chapter 4. Changing the Overall Format .. .. .. .. .. .. .. .. .. .. .. .. 99 4.1. Setup files .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 99 4.2. Page size and page orientation .. .. .. .. .. .. .. .. .. .. .. .. 102 4.3. Page margins, page boxes, and page backgrounds .. .. .. .. .. .. .. 104 4.4. Page numbers and running headers .. .. .. .. .. .. .. .. .. .. .. 107 Chapter 5. References .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 112 5.1. Setting up a bibliographic database .. .. .. .. .. .. .. .. .. .. .. 112 5.2. Citation .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 113 5.3. Labelled (as opposed to numbered) references .. .. .. .. .. .. .. .. 115 5.4. Constructing database entries .. .. .. .. .. .. .. .. .. .. .. .. 116 5.5. Changing the appearance of citations and the reference list .. .. .. .. 119 5.6. Creating your own entry types and formats .. .. .. .. .. .. .. .. .. 122 Chapter 6. Tables .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 125 6.1. Getting started .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 125 6.2. Changing the appearance of cells .. .. .. .. .. .. .. .. .. .. .. 127 6.3. Changing the appearance of rows .. .. .. .. .. .. .. .. .. .. .. 129 6.4. Rules .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 130 6.5. Margins .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 132 6.6. Cell width and height .. .. .. .. .. .. .. .. .. .. .. .. .. .. 133 6.7. Indenting and struts .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 134 6.8. Aligned columns .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 134 6.9. Spanning columns and rows .. .. .. .. .. .. .. .. .. .. .. .. .. 136 6.10. Vertical alignment of tables .. .. .. .. .. .. .. .. .. .. .. .. 139 iv 6.11. Multi-page tables .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 140 6.12. Plain text tables .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 142 6.13. Changing the overall format .. .. .. .. .. .. .. .. .. .. .. .. 144 6.14. Summary of options .. .. .. .. .. .. .. .. .. .. .. .. .. .. 145 Chapter 7. Mathematics .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 148 7.1. Getting started .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 148 7.2. Commonly used symbols .. .. .. .. .. .. .. .. .. .. .. .. .. 149 7.3. Matrices .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 150 7.4. Displaying equations .. .. .. .. .. .. .. .. .. .. .. .. .. .. 153 7.5. Defining new mathematical symbols .. .. .. .. .. .. .. .. .. .. 155 7.6. Summary .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 156 Chapter 8. Basic Graphics .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 165 8.1. Colour .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 165 8.2. Textures .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 166 8.3. Boxes and rules .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 168 8.4. Outlined words .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 172 8.5. Rotation .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 172 8.6. Scaling .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 173 8.7. Clipping .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 175 8.8. Mirror reflections .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 176 8.9. Including an illustration .. .. .. .. .. .. .. .. .. .. .. .. .. .. 176 8.10. Precise object placement .. .. .. .. .. .. .. .. .. .. .. .. .. 177 Chapter 9. Diagrams .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 182 9.1. Introduction
Load more

Recommended publications
  • Tinn-R Team Has a New Member Working on the Source Code: Wel- Come Huashan Chen
    Editus eBook Series Editus eBooks is a series of electronic books aimed at students and re- searchers of arts and sciences in general. Tinn-R Editor (2010 1. ed. Rmetrics) Tinn-R Editor - GUI forR Language and Environment (2014 2. ed. Editus) José Cláudio Faria Philippe Grosjean Enio Galinkin Jelihovschi Ricardo Pietrobon Philipe Silva Farias Universidade Estadual de Santa Cruz GOVERNO DO ESTADO DA BAHIA JAQUES WAGNER - GOVERNADOR SECRETARIA DE EDUCAÇÃO OSVALDO BARRETO FILHO - SECRETÁRIO UNIVERSIDADE ESTADUAL DE SANTA CRUZ ADÉLIA MARIA CARVALHO DE MELO PINHEIRO - REITORA EVANDRO SENA FREIRE - VICE-REITOR DIRETORA DA EDITUS RITA VIRGINIA ALVES SANTOS ARGOLLO Conselho Editorial: Rita Virginia Alves Santos Argollo – Presidente Andréa de Azevedo Morégula André Luiz Rosa Ribeiro Adriana dos Santos Reis Lemos Dorival de Freitas Evandro Sena Freire Francisco Mendes Costa José Montival Alencar Junior Lurdes Bertol Rocha Maria Laura de Oliveira Gomes Marileide dos Santos de Oliveira Raimunda Alves Moreira de Assis Roseanne Montargil Rocha Silvia Maria Santos Carvalho Copyright©2015 by JOSÉ CLÁUDIO FARIA PHILIPPE GROSJEAN ENIO GALINKIN JELIHOVSCHI RICARDO PIETROBON PHILIPE SILVA FARIAS Direitos desta edição reservados à EDITUS - EDITORA DA UESC A reprodução não autorizada desta publicação, por qualquer meio, seja total ou parcial, constitui violação da Lei nº 9.610/98. Depósito legal na Biblioteca Nacional, conforme Lei nº 10.994, de 14 de dezembro de 2004. CAPA Carolina Sartório Faria REVISÃO Amek Traduções Dados Internacionais de Catalogação na Publicação (CIP) T591 Tinn-R Editor – GUI for R Language and Environment / José Cláudio Faria [et al.]. – 2. ed. – Ilhéus, BA : Editus, 2015. xvii, 279 p. ; pdf Texto em inglês.
    [Show full text]
  • Markdown Markup Languages What Is Markdown? Symbol
    Markdown What is Markdown? ● Markdown is a lightweight markup language with plain text formatting syntax. Péter Jeszenszky – See: https://en.wikipedia.org/wiki/Markdown Faculty of Informatics, University of Debrecen [email protected] Last modified: October 4, 2019 3 Markup Languages Symbol ● Markup languages are computer languages for annotating ● Dustin Curtis. The Markdown Mark. text. https://dcurt.is/the-markdown-mark – They allow the association of metadata with parts of text in a https://github.com/dcurtis/markdown-mark clearly distinguishable way. ● Examples: – TeX, LaTeX https://www.latex-project.org/ – Markdown https://daringfireball.net/projects/markdown/ – troff (man pages) https://www.gnu.org/software/groff/ – XML https://www.w3.org/XML/ – Wikitext https://en.wikipedia.org/wiki/Help:Wikitext 2 4 Characteristics Usage (2) ● An easy-to-read and easy-to-write plain text ● Collaboration platforms and tools: format that. – GitHub https://github.com/ ● Can be converted to various output formats ● See: Writing on GitHub (e.g., HTML). https://help.github.com/en/categories/writing-on-github – Trello https://trello.com/ ● Specifically targeted at non-technical users. ● See: How To Format Your Text in Trello ● The syntax is mostly inspired by the format of https://help.trello.com/article/821-using-markdown-in-trell o plain text email. 5 7 Usage (1) Usage (3) ● Markdown is widely used on the web for ● Blogging platforms and content management entering text. systems: – ● The main application areas include: Ghost https://ghost.org/
    [Show full text]
  • Using NROFF and TROFF
    Using NROFF and TROFF Part Number: 800-1755-10 Revision A, of 9 May 1988 UNIX is a registered trademark of AT&T. SunOS is a trademark of Sun Microsystems, Inc. Sun Workstation is a registered trademark of Sun Microsystems, Inc. Material in this manual comes from a number of sources: NrofflTroff User's Manual, Joseph F. Ossanna, Bell Laboratories, Murray Hill, New Jersey; A Troff Tutorial, Brian W. Kernighan, Bell Laboratories, Murray Hill, New Jersey; Typ­ ing Documents on the UNIXSystem: Using the -ms Macros with Troff and Nroff, M. E. Lesk, Bell Laboratories, Murray Hill, New Jersey; A Guide to Preparing Documents with -ms, M. E. Lesk, Bell Laboratories, Murray Hill, New Jersey; Document Formatting on UNIXUsing the -ms Macros, Joel Kies, University of California, Berkeley, California; Writing Papers with Nroff Using -me, Eric P. Allman, University of California, Berkeley; and Introducing the UNIXSystem, Henry McGilton, Rachel Morgan, McGraw-Hill Book Company, 1983. These materials are gratefully acknowledged. Copyright © 1987, 1988 by Sun Microsystems, Inc. This publication is protected by Federal Copyright Law, with all rights reserved. No part of this publication may be reproduced, stored in a retrieval system, translated, transcribed, or transmitted, in any form, or by any means manual, electric, electronic, electro-magnetic, mechanical, chemical, optical, or other­ wise, without prior explicit written permission from Sun Microsystems. Contents Chapter 1 Introduction . 1.1. nrof f andtrof f . Text Formatting Versus Word Processing TheEvolutionof nr of f andt ro f f Preprocessors and Postprocessors 1.2. tr of f, Typesetters, and Special-Purpose Formatters ............ 1.3.
    [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]
  • Tugboat, Volume 33 (2012), No. 1 53 TEX on Windows: Miktex Or TEX Live? Joseph Wright on Windows, There Are Two Actively-Develop
    TUGboat, Volume 33 (2012), No. 1 53 TEX on Windows: MiKTEX or TEX Live? A reminder that MiKTEX and TEX Live are not the only choices. W32TEX (Kakuto, 2012) is popular Joseph Wright in the far east. As well as being a TEX system in On Windows, there are two actively-developed free its own right, it is the source of the Windows binar- TEX systems with similar coverage: MiKTEX (Schenk, ies for TEX Live, and TEX Live acquires more CJK 2011) and TEX Live (TEX Users Group, 2011). The support from it every year. For users focussed on good news is that there is a lot of similarity between ConTEXt, ConTEXt standalone (Pragma ADE, 2012) the two systems, so for most users both systems is probably the best way to go (it uses the W32TEX are equally usable, and (LA)TEX documents are port- binaries on Windows). There are also the commer- able between them. However, there are differences cial options, for example BaKoMa TEX (BaKoMa and depending on what you need these might be Soft., 2011) or PCTEX (Personal TEX, Inc., 2011). important. However, for most users it comes down to a choice between the ‘big two’. • The default settings install everything for TEX Live, but only a minimal set of packages for References MiKT X. MiKT X will then install extra pack- E E BaKoMa Soft. “BaKoMa T X 9.77”. ages ‘on the fly’, while T X Live does not (there E E http://www.bakoma-tex.com/, 2011. is a package to do that in TEX Live, but it is aimed at GNU/Linux users).
    [Show full text]
  • Deployment of XML for Office Documents in Organizations
    JYVÄSKYLÄ LICENTIATE THESES IN COMPUTING 16 Eliisa Jauhiainen DeployPent of XML for OfÀFe DoFXPents in Organizations JYVÄSKYLÄ LICENTIATE THESES IN COMPUTING 16 Eliisa Jauhiainen Deployment of XML for Office Documents in Organizations UNIVERSITY OF JYVÄSKYLÄ JYVÄSKYLÄ 2014 Deployment of XML for Office Documents in Organizations JYVÄSKYLÄ LICENTIATE THESES IN COMPUTING 16 Eliisa Jauhiainen Deployment of XML for Office Documents in Organizations UNIVERSITY OF JYVÄSKYLÄ JYVÄSKYLÄ 2014 Editor Mauri Leppänen Department of Computer Science and Information Systems, University of Jyväskylä URN:ISBN:978-951-39-5600-4 ISBN 978-951-39-5600-4 (PDF) ISBN 978-951-39-5599-1 (nid.) ISSN 1795-9713 Copyright © 2014, by University of Jyväskylä Jyväskylä University Printing House, Jyväskylä 2014 ABSTRACT Jauhiainen, Eliisa Deployment of XML for office documents in organizations Jyväskylä: University of Jyväskylä, 201, 63 p. (+ four included articles) (-\YlVN\Ol/LFHQWLDWH7KHVHVLQ&RPSXWLQJ ISSN) ,6%1 (nid.), 978-951-39-5600-4 (PDF) Licentiate Thesis Majority of the content in organizations is stored as documents. Structured documents, like XML documents, allow the structure definitions, document instances, and layout specifications to be handled as separate entities. This is an important feature to realize from a document management point of view. A class of similar documents with the same structure constitutes a document type. The documents are built from components that are logical units of information within the context of the document type. Office documents are typically authored using word-processing software, they are relatively short in length, and intended for human consumption. The development of open office standards brought XML to organizations’ office en- vironments and changed the capabilities of using document content in ways that were previously impossible or difficult.
    [Show full text]
  • System Tools Reference Manual for Filenet Image Services
    IBM FileNet Image Services Version 4.2 System Tools Reference Manual SC19-3326-00 IBM FileNet Image Services Version 4.2 System Tools Reference Manual SC19-3326-00 Note Before using this information and the product it supports, read the information in “Notices” on page 1439. This edition applies to version 4.2 of IBM FileNet Image Services (product number 5724-R95) and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright IBM Corporation 1984, 2019. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About this manual 17 Manual Organization 18 Document revision history 18 What to Read First 19 Related Documents 19 Accessing IBM FileNet Documentation 20 IBM FileNet Education 20 Feedback 20 Documentation feedback 20 Product consumability feedback 21 Introduction 22 Tools Overview 22 Subsection Descriptions 35 Description 35 Use 35 Syntax 35 Flags and Options 35 Commands 35 Examples or Sample Output 36 Checklist 36 Procedure 36 May 2011 FileNet Image Services System Tools Reference Manual, Version 4.2 5 Contents Related Topics 36 Running Image Services Tools Remotely 37 How an Image Services Server can hang 37 Best Practices 37 Why an intermediate server works 38 Cross Reference 39 Backup Preparation and Analysis 39 Batches 39 Cache 40 Configuration 41 Core Files 41 Databases 42 Data Dictionary 43 Document Committal 43 Document Deletion 43 Document Services 44 Document Retrieval 44 Enterprise Backup/Restore (EBR)
    [Show full text]
  • Looking to the Future by JOHN BALDWIN
    1 of 3 Looking to the Future BY JOHN BALDWIN FreeBSD’s 13.0 release delivers new features to users and refines the workflow for new contri- butions. FreeBSD contributors have been busy fixing bugs and adding new features since 12.0’s release in December of 2018. In addition, FreeBSD developers have refined their vision to focus on FreeBSD’s future users. An abbreviated list of some of the changes in 13.0 is given below. A more detailed list can be found in the release notes. Shifting Tools Not all of the changes in the FreeBSD Project over the last two years have taken the form of patches. Some of the largest changes have been made in the tools used to contribute to FreeBSD. The first major change is that FreeBSD has switched from Subversion to Git for storing source code, documentation, and ports. Git is widely used in the software industry and is more familiar to new contribu- tors than Subversion. Git’s distributed nature also more easily facilitates contributions from individuals who are Not all of the changes in the not committers. FreeBSD had been providing Git mir- rors of the Subversion repositories for several years, and FreeBSD Project over the last many developers had used Git to manage in-progress patches. The Git mirrors have now become the offi- two years have taken the form cial repositories and changes are now pushed directly of patches. to Git instead of Subversion. FreeBSD 13.0 is the first release whose sources are only available via Git rather than Subversion.
    [Show full text]
  • Interface Specification – Archive Content Services
    gSPECIFICATION REV. 484-0200155 F5 NCR Corporation Image & Payment Systems 50 Northland Road Unit 100 Waterloo, Ontario N2V1 N3 PROGRAM: ImageMark Archive 5.1 TITLE: Interface Specification – Archive Content Services DATE: December 7, 2016 RELEASE: Draft SOURCE ORGANIZATION: Solutions Architecture Prepared By: Peter Robinson, Solutions Architecture Date Approved By: Judy Sandison, Manager, Solutions Architecture Date Copyright © 2016 by NCR Corporation, Duluth, Georgia, USA. All rights reserved. SPECIFICATION REV. 484-0200155 F5 NCR Corporation Image & Payment Systems 50 Northland Road Unit 100 Waterloo, Ontario N2V1 N3 PROGRAM: ImageMark Archive 5.1 TITLE: Interface Specification – Archive Content Services DATE: December 7, 2016 RELEASE: Draft SOURCE ORGANIZATION: Solutions Architecture Copyright © 2016 by NCR Corporation, Duluth, Ohio, USA. All rights reserved. ImageMark Archive 4.01 484-0200155, Rev F13 Interface Specification – Archive Content Services Page 3 of 62 CHANGE SHEET Rev Date Section Description of Change By A 06/13/2003 All Initial Release – 53DR25561 Peter Robinson B 09/03/2003 All Change Release – 53DR25690 Peter Robinson C 11/30/2003 All Change Release – 53DR25905 Peter Robinson D 10/28/2004 All Change Release – 53DR26456 Peter Robinson E 02/16/2005 All Change Release – 53DR24994 F1 06/01/2005 Peter Robinson F All Change Rev.F is a copy of draft Rev.Fn Peter Robinson F All Released on 53DRnnnnn Peter Robinson F2 03/28/2006 6.2 Added error codes for Fill element F3 09/22/2014 All Updated 5.1 Release Information Saurabh Patel F4 10/17/2016 6, 7, 12 New sections Anjali Phatak F5 11/18/2016 13 New section - FAQs Anjali Phatak NCR Corporation December 7, 2016 ImageMark Archive 4.01 484-0200155, Rev F13 Interface Specification – Archive Content Services Page 4 of 62 TABLE OF CONTENTS 1.
    [Show full text]
  • Luametatex Reference Manual
    LuaMetaTEX Reference Manual February 2021 Version 2.08.16 LuaMetaTEX Reference Manual copyright : LuaTEX development team :CONTEXT development team more info : www.luatex.org : contextgarden.net version : February 20, 2021 Contents Introduction 11 1 The internals 15 2 Differences with LUATEX 19 3 The original engines 25 3.1 The merged engines 25 3.1.1 The rationale 25 3.1.2 Changes from TEX 3.1415926... 25 3.1.3 Changes from 휀-TEX 2.2 26 3.1.4 Changes from PDFTEX 1.40 27 3.1.5 Changes from ALEPH RC4 28 3.1.6 Changes from standard WEB2C 28 3.2 Implementation notes 29 3.2.1 Memory allocation 29 3.2.2 Sparse arrays 29 3.2.3 Simple single-character csnames 29 3.2.4 Binary file reading 29 3.2.5 Tabs and spaces 30 3.2.6 Logging 30 3.2.7 Parsing 30 4 Using LUAMETATEX 33 4.1 Initialization 33 4.1.1 LUAMETATEX as a LUA interpreter 33 4.1.2 Other commandline processing 33 4.2 LUA behaviour 35 4.2.1 The LUA version 35 4.2.2 Locales 35 4.3 LUA modules 35 4.4 Testing 36 5 Basic TEX enhancements 37 5.1 Introduction 37 5.1.1 Primitive behaviour 37 5.1.2 Version information 37 5.2 UNICODE text support 38 5.2.1 Extended ranges 38 5.2.2 \Uchar 39 5.2.3 Extended tables 39 1 5.3 Attributes 41 5.3.1 Nodes 41 5.3.2 Attribute registers 42 5.3.3 Box attributes 42 5.4 LUA related primitives 44 5.4.1 \directlua 44 5.4.2 \luaescapestring 45 5.4.3 \luafunction, \luafunctioncall and \luadef 45 5.4.4 \luabytecode and \luabytecodecall 46 5.5 Catcode tables 47 5.5.1 Catcodes 47 5.5.2 \catcodetable 47 5.5.3 \initcatcodetable 47 5.5.4 \savecatcodetable 48 5.6 Tokens, commands
    [Show full text]
  • Triroff, an Adaptation of the Device-Independent Troff for Formatting Tri-Directional Text
    ELECTRONIC PUBLISHING, VOL . 2(3), 119±142 (OCTOBER 1989) triroff, an adaptation of the device-independent troff for formatting tri-directional text ( K9J+ דניאל ברי) 69K ) AND DANIEL BERRY זאב בקר) ZEEV BECKER 9 T Computer Science Department Technion , Haifa 32000 N , Israel X SUMMARY This paper describes a system for formatting documents consisting of text written in languages printed in three different directions, left-to-right, right-to-left, and top-to-bottom. For example, this paper is such a document because it contains text written in English, Hebrew, Japanese, and Chinese. The system assumes that the input is in the order in which the text is read aloud, and it produces output in which each language is printed in its own correct direction, but for which a human cognizant of the reading conventions will reproduce the input order. The system consists of three major pieces of software: Ossana and Kernighan's ditroff for formatting text consisting of only left-to-right or unidirectional text, Buchman and Berry's ffortid for rearranging right-to-left language text occurring in ditroff output to be printed from right to left, and a new program bditroff for rearranging top-to- bottom text occurring in ditroff output to be printed from top to bottom. Below are translations of this English language abstract, except for this paragraph, into Hebrew, Japanese, and Chinese. The latter two are each printed twice, once in a modern left- to-right style, and once in a more traditional top-to-bottom style. The software described in this paper was used to format and typeset this paper.
    [Show full text]
  • GNU Texinfo Reference Card @Contents Print a Complete Table of Contents
    GNU Texinfo Reference Card @contents Print a complete table of contents. Has no effect in Cross references (for Texinfo version 6.8) Info, which uses menus instead. Within the Info system http://www.gnu.org/software/texinfo/ Nodes @xref {node, [entry] , [node-title] , [info-file] , [manual] } Makes @node name Begin a new node. a reference that starts with ‘See’ in a printed manual. Follow Texinfo document skeleton command with punctuation. Only the first argument is @top title Mark the topmost @node in the file, which must be mandatory. Texinfo source files are plain text; standard extensions are defined on the line immediately preceding @top. The title is @pxref {node, [entry] , [node-title] , [info-file] , [manual] } Like ‘.texinfo’, ‘.texi’, and ‘.txi’. A Texinfo file must begin with formatted as a chapter-level heading. The entire top node, @xref, but starts with ‘see’ instead of ‘See’, and must be used lines like this: including the @node and @top lines, are normally enclosed with @ifnottex ... @end ifnottex. inside parentheses. \input texinfo @ref {node, [entry] , [node-title] , [info-file] , [manual] } Like @xref, @settitle name-of-manual @anchor {name} Define name as the current location, for use as a cross-reference target. but produces only the bare reference without ‘See’ or ‘see’; must ... be followed by a punctuation mark. the contents of the Texinfo document, ending with: @novalidate Suppress validation of node references and omit @bye creation of auxiliary files with T X. Use before @setfilename. @xrefautomaticsectiontitle on|off By default, use the section E title instead of the node name in cross references. Texinfo @-commands Chapter structuring Outside of Info Beginning a Texinfo document @lowersections Change subsequent chapters to sections, sections @url {url, [displayed-text] , [replacement] } Make a hyperlink to subsections, and so on.
    [Show full text]