DOCSLIB.ORG

Optex Manual

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Optex Manual OpTEX 1 Format Based on Plain TEX and OPmac Version 1.04 Petr Olšák, 2020, 2021 http://petr.olsak.net/optex OpTEX is LuaTEX format with Plain TEX and OPmac. Only LuaTEX engine is supported. OpTEX should be a modern Plain TEX with power from OPmac (Fonts Selection System, colors, graphics, references, hyperlinks, indexing, bibliography, ...) with preferred Unicode fonts. The main goal of OpTEX is: • OpTEX keeps the simplicity (like in Plain TEX and OPmac macros). • There is no old obscurities concerning various 8-bit encodings and various engines. • OpTEX provides a powerful Fonts Selection System (for Unicode font families, of course). • OpTEX supports hyphenations of all languages installed in your TEX system. • All features from OPmac macros are copied. For example sorting words in the Index2, reading .bib files directly2, syntax highlighting2, colors, graphics, hyperlinks, references). • Macros are documented in the same place where code is. • User namespace of control sequences is separated from the internal namespace of OpTEX and primitives (\foo versus \_foo). The namespaces for macro writers are designed too. If you need to customize your document or you need to use something very specific, then you can copy relevant parts of OpTEX macros into your macro file and do changes to these macros here. This is a significant difference fromA LTEX or ConTeXt, which is an attempt to create a new user level with a plenty of non-primitive parameters and syntax hiding TEX internals. The macros from OpTEX are simple and straightforward because they solve only what is explicitly needed, they do not create a new user level for controlling your document. We are using TEX directly in this case. You can use OpTEX macros, understand them, and modify them. OpTEX offers a markup language for authors of texts (likeA LTEX), i. e. the fixed set of tags to define the structure of the document. This markup is differentA fromtheLTEX markup. It may offer to write the source text of the document somewhat clearer and more attractive. The manual includes two parts: user documentation and technical documentation. The second part is generated directly from the sources of OpTEX. There are many hyperlinks from one part to second and vice versa. This manual describes OpTEX features only. We suppose that the user knows TEX basics. They are described in many books. You can see a short document TEX in nutshell too. 1 OPmac package is a set of simple additional macros to Plain TEX. It enables users to take advantage of LATEX functionality but keeps Plain TEX simplicity. See http://petr.olsak.net/opmac-e.html for more information about it. 2 All these features are implemented by TEX macros, no external program is needed. 1 Contents 1 User documentation 5 1.1 Starting with OpTEX..................................... 5 1.2 Page layout . 5 1.2.1 Setting the margins . 5 1.2.2 Concept of the default page . 6 1.2.3 Footnotes and marginal notes . 7 1.3 Fonts ............................................. 7 1.3.1 Font families . 7 1.3.2 Font sizes . 8 1.3.3 Typesetting math . 9 1.4 Typical elements of the document . 10 1.4.1 Chapters and sections . 10 1.4.2 Another numbered objects . 10 1.4.3 References . 12 1.4.4 Hyperlinks, outlines . 12 1.4.5 Lists . 13 1.4.6 Tables . 14 1.4.7 Verbatim . 16 1.5 Autogenerated lists . 18 1.5.1 Table of contents . 18 1.5.2 Making the index . 18 1.5.3 BibTEXing....................................... 20 1.6 Graphics . 21 1.6.1 Colors . 21 1.6.2 Images . 22 1.6.3 PDF transformations . 22 1.6.4 Ovals, circles . 23 1.6.5 Putting images and texts wherever . 24 1.7 Others . 24 1.7.1 Using more languages . 24 1.7.2 Pre-defined styles . 25 1.7.3 Loading other macro packages . 25 1.7.4 Lorem ipsum dolor sit . 26 1.7.5 Logos . 26 1.7.6 The last page . 26 1.7.7 Use OpTEX....................................... 26 1.8 Summary . 27 1.9 API for macro writers . 27 1.10 Compatibility with Plain TEX............................... 29 2 Technical documentation 30 2.1 The main initialization file . 30 2.2 Concept of namespaces of control sequences . 32 2.2.1 Prefixing internal control sequences . 32 2.2.2 Namespace of control sequences for users . 32 2.2.3 Macro files syntax . 33 2.2.4 Name spaces for package writers . 33 2.2.5 Summary about rules for external macro files published forE OpT X........ 33 2.2.6 The implementation of the namespaces . 34 2 2.3 pdfTEX initialization . 35 2.4 Basic macros . 37 2.5 Allocators for TEX registers . 39 2.6 If-macros, loops, is-macros . 41 2.6.1 Classical \newif .................................... 41 2.6.2 Loops.......................................... 41 2.6.3 Is-macros . 43 2.7 Setting parameters . 44 2.7.1 Primitive registers . 45 2.7.2 Plain TEX registers . 45 2.7.3 Different settings than in plainE T X......................... 46 2.7.4 OpTEX parameters . 46 2.8 More OpTEX macros . 51 2.9 Using key=value format in parameters . 54 2.10 Plain TEX macros . 55 2.11 Preloaded fonts for text mode . 59 2.12 Scaling fonts in text mode (low-level macros) . 60 2.12.1 The \setfontsize macro . 60 2.12.2 The \font primitive . 60 2.12.3 The \fontlet declarator . 60 2.12.4 Optical sizes . 61 2.12.5 Implementation of resizing . 61 2.13 The Font Selection System . 62 2.13.1 Terminology . 62 2.13.2 Font families, selecting fonts . 63 2.13.3 Math Fonts . 64 2.13.4 Declaring font commands . 64 2.13.5 The \fontdef declarator in detail . 64 2.13.6 The \famvardef declarator . 64 2.13.7 The \tt variant selector . 65 2.13.8 Font commands defined by \def ........................... 66 2.13.9 Modifying font features . 66 2.13.10 Special font modifiers . 66 2.13.11 How to create the font family file . 67 2.13.12 How to write the font family file with optical sizes . 70 2.13.13 How to register the font family in the Font Selection System . 71 2.13.14 Notices about extension of \font primitive . 72 2.13.15 Implementation of the Font Selection System . 72 2.14 Preloaded fonts for math mode . 79 2.15 Math macros . 82 2.16 Unicode-math fonts . 90 2.16.1 Unicode-math macros preloaded in the format . 91 2.16.2 Macros and codes set when \loadmatfont is processed . 93 2.16.3 More Unicode-math examples . 100 2.16.4 Printing all Unicode math slots in used math font . 100 2.17 Scaling fonts in document (high-level macros) . ..
Load more

Recommended publications
  • Typesetting Classical Greek Philology Could Not find Anything Really Suitable for Her
    276 TUGboat, Volume 23 (2002), No. 3/4 professor of classical Greek in a nearby classical high Philology school, was complaining that she could not typeset her class tests in Greek, as she could do in Latin. I stated that with LATEX she should not have any The teubner LATEX package: difficulty, but when I started searching on CTAN,I Typesetting classical Greek philology could not find anything really suitable for her. At Claudio Beccari that time I found only the excellent Greek fonts de- signed by Silvio Levy [1] in 1987 but for a variety of Abstract reasons I did not find them satisfactory for the New The teubner package provides support for typeset- Font Selection Scheme that had been introduced in LAT X in 1994. ting classical Greek philological texts with LATEX, E including textual and rhythmic verse. The special Thus, starting from Levy’s fonts, I designed signs and glyphs made available by this package may many other different families, series, and shapes, also be useful for typesetting philological texts with and added new glyphs. This eventually resulted in other alphabets. my CB Greek fonts that now have been available on CTAN for some years. Many Greek users and schol- 1 Introduction ars began to use them, giving me valuable feedback In this paper a relatively large package is described regarding corrections some shapes, and, even more that allows the setting into type of philological texts, important, making them more useful for the com- particularly those written about Greek literature or munity of people who typeset in Greek — both in poetry.
    [Show full text]
  • Survey Concerning Citation Practices in Industrial Property Offices
    HANDBOOK ON INDUSTRIAL PROPERTY INFORMATION AND DOCUMENTATION Ref.: Examples and IPO practices page: 7.9.1.0 SURVEY CONCERNING CITATION PRACTICES IN INDUSTRIAL PROPERTY OFFICES Editorial note by the International Bureau 1. A survey “Citation Practices in Patent Offices” commissioned by the Standards and Documentation Working Group (SDWG) of the Standing Committee on Information Technologies (SCIT) in its fourth session, held in January 2004, was prepared by the Citation Practices Task Force (see document SCIT/SDWG/4/14, paragraph 78). The Task Force was convened to clarify the different practices by industrial property offices regarding the difficulties in citing specific parts of the description of the invention text in a patent document. 2. At its ninth session, held in February 2008, the SDWG approved (see document SCIT/SDWG/9/12, paragraph 30) the publication of the summary of responses to the survey “Citation Practices in Patent Offices” in Part 7 of the WIPO Handbook. Furthermore the SDWG mandated the Task Force to develop an extended survey questionnaire to further determine the citation practices of industrial property offices (see document SCIT/SDWG/9/12, paragraph 32). The extended survey prepared by the Task Force was issued as WIPO Circular C.SCIT 2651 on May 9, 2008. 3. The SDWG, at its tenth session, held in November 2008, approved (see document SCIT/SDWG/10/12, paragraph 47) the publication of “Citation Practices in Industrial Property Offices” in Part 7 of the WIPO Handbook, replacing the previous survey concerning “Citation Practices in Patent Offices”, which has been moved to the Archives. 4. The current document summarizes the results of the extended survey, the second version.
    [Show full text]
  • The File Cmfonts.Fdd for Use with Latex2ε
    The file cmfonts.fdd for use with LATEX 2".∗ Frank Mittelbach Rainer Sch¨opf 2019/12/16 This file is maintained byA theLTEX Project team. Bug reports can be opened (category latex) at https://latex-project.org/bugs.html. 1 Introduction This file contains the external font information needed to load the Computer Modern fonts designed by Don Knuth and distributed with TEX. From this file all .fd files (font definition files) for the Computer Modern fonts, both with old encoding (OT1) and Cork encoding (T1) are generated. The Cork encoded fonts are known under the name ec fonts. 2 Customization If you plan to install the AMS font package or if you have it already installed, please note that within this package there are additional sizes of the Computer Modern symbol and math italic fonts. With the release of LATEX 2", these AMS `extracm' fonts have been included in the LATEX font set. Therefore, the math .fd files produced here assume the presence of these AMS extensions. For text fonts in T1 encoding, the directive new selects the new (version 1.2) DC fonts. For the text fonts in OT1 and U encoding, the optional docstrip directive ori selects a conservatively generated set of font definition files, which means that only the basic font sizes coming with an old LATEX 2.09 installation are included into the \DeclareFontShape commands. However, on many installations, people have added missing sizes by scaling up or down available Metafont sources. For example, the Computer Modern Roman italic font cmti is only available in the sizes 7, 8, 9, and 10pt.
    [Show full text]
  • Surviving the TEX Font Encoding Mess Understanding The
    Surviving the TEX font encoding mess Understanding the world of TEX fonts and mastering the basics of fontinst Ulrik Vieth Taco Hoekwater · EuroT X ’99 Heidelberg E · FAMOUS QUOTE: English is useful because it is a mess. Since English is a mess, it maps well onto the problem space, which is also a mess, which we call reality. Similary, Perl was designed to be a mess, though in the nicests of all possible ways. | LARRY WALL COROLLARY: TEX fonts are mess, as they are a product of reality. Similary, fontinst is a mess, not necessarily by design, but because it has to cope with the mess we call reality. Contents I Overview of TEX font technology II Installation TEX fonts with fontinst III Overview of math fonts EuroT X ’99 Heidelberg 24. September 1999 3 E · · I Overview of TEX font technology What is a font? What is a virtual font? • Font file formats and conversion utilities • Font attributes and classifications • Font selection schemes • Font naming schemes • Font encodings • What’s in a standard font? What’s in an expert font? • Font installation considerations • Why the need for reencoding? • Which raw font encoding to use? • What’s needed to set up fonts for use with T X? • E EuroT X ’99 Heidelberg 24. September 1999 4 E · · What is a font? in technical terms: • – fonts have many different representations depending on the point of view – TEX typesetter: fonts metrics (TFM) and nothing else – DVI driver: virtual fonts (VF), bitmaps fonts(PK), outline fonts (PFA/PFB or TTF) – PostScript: Type 1 (outlines), Type 3 (anything), Type 42 fonts (embedded TTF) in general terms: • – fonts are collections of glyphs (characters, symbols) of a particular design – fonts are organized into families, series and individual shapes – glyphs may be accessed either by character code or by symbolic names – encoding of glyphs may be fixed or controllable by encoding vectors font information consists of: • – metric information (glyph metrics and global parameters) – some representation of glyph shapes (bitmaps or outlines) EuroT X ’99 Heidelberg 24.
    [Show full text]
  • DNDO Statement of Intent for New National Lab Work, 22 Nov 05
    70RDND18R00000001 ER BAA FY18 Exploratory Research in Preventing Nuclear and Radiological Terrorism Broad Agency Announcement No. 70RDND18R00000001 for Domestic Nuclear Detection Office (DNDO) Transformational and Applied Research Directorate (TAR) 1 70RDND18R00000001 ER BAA FY18 Table of Contents 1 Introduction ..............................................................................................................................4 1.1 Background ......................................................................................................................5 1.2 Grand Challenges & Technology Portfolios ....................................................................6 1.3 Strategic Approach...........................................................................................................8 1.4 Scope and Funding ...........................................................................................................8 2 Exploratory Research Topics ...................................................................................................9 2.1 RTA-01: Mobile Active Interrogation Using Neutrons (MAIN) ....................................9 2.2 RTA-02: Radiation Isotope Identification Device (RIID) Based on Thallium Bromide......................................................................................................................................11 2.3 RTA-03: Nuclear Detection through Centralized Data Analytics .................................14 3 Management Approach ..........................................................................................................16
    [Show full text]
  • Typeset MMIX Programs with TEX Udo Wermuth Abstract a TEX Macro
    TUGboat, Volume 35 (2014), No. 3 297 Typeset MMIX programs with TEX Example: In section 9 the lines \See also sec- tion 10." and \This code is used in section 24." are given. Udo Wermuth No such line appears in section 10 as it only ex- tends the replacement code of section 9. (Note that Abstract section 10 has in its headline the number 9.) In section 24 the reference to section 9 stands for all of ATEX macro package is presented as a literate pro- the eight code lines stated in sections 9 and 10. gram. It can be included in programs written in the If a section is not used in any other section then languages MMIX or MMIXAL without affecting the it is a root and during the extraction of the code a assembler. Such an instrumented file can be pro- file is created that has the name of the root. This file cessed by TEX to get nicely formatted output. Only collects all the code in the sequence of the referenced a new first line and a new last line must be entered. sections from the code part. The collection process And for each end-of-line comment a flag is set to for all root sections is called tangle. A second pro- indicate that the comment is written in TEX. cess is called weave. It outputs the documentation and the code parts as a TEX document. How to read the following program Example: The following program has only one The text that starts in the next chapter is a literate root that is defined in section 4 with the headline program [2, 1] written in a style similar to noweb [7].
    [Show full text]
  • Accessibility Checklists
    Accessibility Checklists www.aub.edu.lb/it May 2020 Contact Person Maha Zouwayhed Office of Information Technology American University of Beirut [email protected] | +961-1-350-000 ext. 2082 Beirut PO Box 11-0236, Riad El Solh 1107 2020, Beirut, Lebanon | Tel: +961-1-350-000 | New York 3 Dag Hammarskjold Plaza, 8th Floor | New York, NY 10017–2303, USA | Tel: +1-212-583-7600 | Fax: +1-212-583-7651 1 ACCESSIBILITY CHECKLISTS Role Name & Role Date Compilation Farah Eid – IT Business Development Assistant 13-May-2020 Review Maha Zouwayhed -IT Business Development Manager 14-May-2020 Review Yousif Asfour - CIO (Chief Information Officer) 19-May-2020 Review Walid El-Khazen – Assistant CIO 21-May-2020 Review Ali Zaiter – Senior Software Engineer and Analyst 21-May-2020 Review Fadi Khoury- Manager, Software Development 21-May-2020 Review Rami Farran – Director, It Academic Service 19-May-2020 Review Rana Al Ghazzi – Instructional Designer 19-May-2020 2 ACCESSIBILITY CHECKLISTS Table of Contents Purpose...................................................................................................................................................................... 4 Introduction ............................................................................................................................................................... 5 Developers Checklist ............................................................................................................................................... 6 Designers Checklist ................................................................................................................................................
    [Show full text]
  • The Latex2ε Package Ccfonts
    The LATEX 2" package ccfonts Walter Schmidt∗ (v1.2 { 2020/03/25) Contents 1 Prerequisites 1 2 Using the package 2 2.1 Package options . 3 2.2 Font encoding . 3 3 Known problems 3 4 NFSS classification of the Concrete typefaces 4 5 Implementation 4 5.1 Font setup for text mode . 4 5.2 Options . 5 5.2.1 Standard leading . 5 5.2.2 The option exscale .................. 5 5.2.3 The option slantedGreek ............... 6 5.3 The option boldsans ...................... 6 5.3.1 Processing options . 6 5.4 Font setup for math mode . 6 5.5 Initialization . 7 1 Prerequisites In order to make use of the package ccfonts, the following fonts and .fd files are required: ∗[email protected] 1 • The Concrete text fonts with traditional encoding (CTAN: fonts/ concrete/) • The Concrete text fonts with European encoding (CTAN: fonts/ ecc/) • The mathematical Concrete fonts (CTAN: fonts/concmath/) • The .fd files for the traditional and mathematical Concrete fonts (CTAN: macros/latex/contrib/supported/concmath/) • The .fd files for the European Concrete fonts, which are distributed and installed in conjunction with the ccfonts package On CTAN the fonts are available in METAFONT format. The Concrete typefaces are also provided in Type1 format from Micropress Inc, see <http://www.micropress-inc.com>. 2 Using the package The LATEX macro package ccfonts supports typesetting with the font fam- ily `Concrete'. Loading this package through \usepackage{ccfonts} will effect the following: • The default roman font family is changed to ccr, i.e. Concrete. • The default leading (\baselineskip) for the font sizes 8{12 pt is increased slightly.
    [Show full text]
  • Report of Liaison to ISO Technical Committee 46 to IFLA Cataloguing
    Report of liaison to ISO Technical Committee 46 to IFLA Cataloguing Section, August 2019 Prepared by William Leonard, Chair Standards Council of Canada Mirror Committee to ISO TC46; IFLA CATS member ISO Technical Committee 46 Information and documentation scope: Standardization of practices relating to libraries, documentation and information centres, publishing, archives, records management, museum documentation, indexing and abstracting services, and information science. https://www.iso.org/committee/48750.html ISO TC 46 Information and documentation Current Projects: Working Group 2 Coding of country names and related entities (ISO 3166) Working Group 3 Conversion of written languages (transliteration standards) Working Group 4 and Ad Hoc Group Ongoing revision of ISO 5127:2017 Information and documentation – Foundation and vocabulary Working Group 13 Information Governance Joint TC 171/SC 2 - TC 42 - TC 46/SC 11 - TC 130 WG: Document management applications - Application issues - PDF/A Project recently completed: ISO 8:2019 Presentation and identification of periodicals (revision) News: The Swedish Institute for Standards (SIS) has been approved as the secretariat and chair for Subcommittee 10 Requirements for document storage and conditions for preservation. The project to revise the three parts of ISO 3166 Codes for the representation of names of countries and their subdivisions is currently in the Draft International Standard balloting stage. A ballot to introduce the Jyutping Romanization of Cantonese into the ISO suite of transliteration
    [Show full text]
  • OWS-9 Reference Architecture Profile (RAP) Advisor Engineering Report
    Open Geospatial Consortium Approval Date: 2013-01-18 Posted Date: 2012-12-26 Publication Date: 2013-02-19 OGC 12-156 OGC URI: http://www.opengis.net/def/doc-type/per/OWS-9-RAP Category: Public Engineering Report Editor: George Percivall OGC® OWS-9 Reference Architecture Profile (RAP) Advisor Engineering Report Copyright © 2013 Open Geospatial Consortium. To obtain additional rights of use, visit http://www.opengeospatial.org/legal/. Warning This document is not an OGC Standard. This document is an OGC Public Engineering Report created as a deliverable in an OGC Interoperability Initiative and is not an official position of the OGC membership. It is distributed for review and comment. It is subject to change without notice and may not be referred to as an OGC Standard. Further, any OGC Engineering Report should not be referenced as required or mandatory technology in procurements. ® Document type: OGC Engineering Report Document subtype: NA Document stage: Approved for public release Document language: English OGC 12-156 Abstract The Reference Architecture Profiler (RAP) Advisor™ is a web based application that recommends OGC Standards and OGC Reference Model (ORM) Sections that are relevant to a system development; such that a community of interest could derive and build a profile of suitable OGC standards to meet their specific needs. This Engineering Report contains the requirements, conceptual design, development methodology, and implementation of the RAP Advisor. Initial development of the RAP Advisor™ was concurrent with the OGC Web Services Testbed, Phase 9 (OWS-9) with NGA sponsorship. During OWS-9 timeframe, key concepts of the RAP Advisor were confirmed through prototyping.
    [Show full text]
  • P Font-Change Q UV 3
    p font•change q UV Version 2015.2 Macros to Change Text & Math fonts in TEX 45 Beautiful Variants 3 Amit Raj Dhawan [email protected] September 2, 2015 This work had been released under Creative Commons Attribution-Share Alike 3.0 Unported License on July 19, 2010. You are free to Share (to copy, distribute and transmit the work) and to Remix (to adapt the work) provided you follow the Attribution and Share Alike guidelines of the licence. For the full licence text, please visit: http://creativecommons.org/licenses/by-sa/3.0/legalcode. 4 When I reach the destination, more than I realize that I have realized the goal, I am occupied with the reminiscences of the journey. It strikes to me again and again, ‘‘Isn’t the journey to the goal the real attainment of the goal?’’ In this way even if I miss goal, I still have attained goal. Contents Introduction .................................................................................. 1 Usage .................................................................................. 1 Example ............................................................................... 3 AMS Symbols .......................................................................... 3 Available Weights ...................................................................... 5 Warning ............................................................................... 5 Charter ....................................................................................... 6 Utopia .......................................................................................
    [Show full text]
  • Managing Research Data 101 Workshop GFZ Phd-Day, 22.11.10
    Managing Research Data 101 Workshop GFZ PhD-Day, 22.11.10 Dr. Jens Klump - GFZ/CeGIT Roland Bertelmann - GFZ/Library and Information Services (LIS) Managing Research Data 101 Agenda: With a little help from: Managing Research Data 101, MIT Libraries, MacKenzie Smith (2009) http://libraries.mit.edu/guides/subjects/data-management/Managing%20Research%20Data%20101.pdf Why should we talk about data? You have digital data. You think they are important. Some questions: • Your grant runs out… and then what? • You have been doing all the data-management and then you leave with Ph.D. in hand… and then what? • Your favorite grant agency institutes a data-sustainability requirement for all grants… and then what? • Your lab's PI retires… and then what? • Your instrument manufacturer or favorite software's developer goes out of business… and then what? http://scienceblogs.com/bookoftrogool/2009/11/_and_then_what.php What do you expect today? • You’re managing research data • You’re not sure how to do that • You’re not sure if you should worry about it • You want some clues and pointers • What else? Data Curation Continuum Andrew.treloar.net Basics Basics for the Private Domain Aim: make your data reusable What are Data? What Are Data? Observational data captured in real-time -- Usually irreplaceable Experimental data from lab equipment -- Often reproducable, but can be expensive What Are Data? Simulation data -- Model and metadata inputs are more important than outputs Derived and compiled data -- Reproducable (expensive) What Are Data? • Text e.g. flat text files, Word, PDF • Numerical e.g. SPSS, STATA, Excel, Access, MySQL • Multimedia e.g.
    [Show full text]