DOCSLIB.ORG

Babel Yannis Haralambous, John Plaice, Johannes Braams

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Babel Yannis Haralambous, John Plaice, Johannes Braams Never again active characters! Ω-Babel Yannis Haralambous, John Plaice, Johannes Braams To cite this version: Yannis Haralambous, John Plaice, Johannes Braams. Never again active characters! Ω-Babel. Tug- boat, TeX Users Group, 1995, 16 (4), pp.418-427. hal-02101590 HAL Id: hal-02101590 https://hal.archives-ouvertes.fr/hal-02101590 Submitted on 25 Apr 2019 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. 418 TUGboat, Volume 16 (1995), No. 4 LATEX Never again active characters! Ω-Babel Yannis Haralambous, John Plaice and Johannes Braams »Weißt Du, wo ich das Wasser des Lebens finden kann?« »An der Grenze Phantásiens«, sagte Dame Aiuóla. »Aber Phantásien hat keine Grenzen«, antwortete er. »Doch, aber sie liegen nicht außen, sondern innen.« M. Ende, Die unendliche Geschichte Abstract This progress report of the Ω development team (the first two authors) presents the first major applica- tion of Ω: an adaptation of Babel, the well-known multilingual LATEX package, developed by the third author. We discuss problems related to multilingual typesetting, and show their solutions in the Ω-Babel system. The paper is roughly divided into two parts: the first one (sections 1–4) is intended for average LATEX users, especially those typesetting in languages other than American English; the second part (section 5) is more technical and will be of more interest to developers of multilingual LATEX software. TUGboat, Volume 16 (1995), No. 4 419 1 Introduction Ω-Babel is the first real-world application of Ω:we are in the process of adapting the multilingual LATEX package Babel by Johannes Braams (1991a, 1991b) to take advantage of the functionality of Ω.This allows safer and more complete LATEX typesetting of languages other than American English. Prob- lems due to technical limitations of TEX are solved; for example, the LATEX macros \MakeUppercase and \MakeLowercase have been replaced by Ω filtering processes. The whole process is simpler and more natural. In this progress report we present the first step in adapting Babel to Ω. There will be (at least) two more steps which we describe below; for more information, see section 5 (the technicalities). 1. Babel adapted to Ω;weuseDC font output. \MakeUppercase and \MakeLowercase macros are being replaced by macros launching transla- tion processes. Various input encoding transla- tion processes are being written. The inputenc and fontenc packages are being adapted (their Figure 1: Allegory: input (on the left) and Ω counterparts are called inpenc and fntenc). output (on the right) encodings, too close together. This step has been completed. 2. UC (Unicode Computer Modern) fonts will be released by spring 1996. These fonts contain bel (Bahasa, Breton, Catalan, Croatian, Czech, Dan- Latin, Greek and Cyrillic characters, and a cer- ish, Dutch, English, Estonian, Finnish, French, Gali- tain number of dingbats and graphical charac- cian, German, Hungarian, Irish, Italian, Lower or ters. Ω-Babel uses UC fonts for output: new upper Sorbian, Norwegian, Polish, Romanian, Scot- languages will be dealt with (Bulgarian, Es- tish, Slovakian, Slovenian, Spanish, Swedish, Por- peranto, Greek, Latvian, Lithuanian, Maltese, tuguese or Turkish), then Ω can make it easier for Russian, Vietnamese, Welsh, etc.). Alan Jef- you and give you better results. All you have to do frey’s fontinst will be adapted to make ex- is download the Ω implementation for your machine tended virtual fonts in UC encoding. from ftp://ftp.ens.fr/pub/tex/yannis/omega/ Latin letters with dieresis will be provided in systems or the top-level omega directory1;ifyou two versions: with high or low accent: French- use a T X implementation not already covered, then → E men like dieresis ( tréma) to be high, Ger- (kindly) suggest to the implementor that they → mans prefer to have it ( Umlaut) a little lower. consider including Ω support). Then download the 3. Arabic alphabet languages, Hebrew and Yid- Ω-Babel package from ftp://ftp.ens.fr/pub/tex/ dish will be added at some point during 1996. yannis/omega/macros/obabel or , install it on your 4. Soft hyphenation will be done through Ω trans- machine and use it! The basic syntax is the same lation processes. This allows dynamic loading as in Babel, but we will discuss new options and of hyphenation algorithms, independently of the functionality in section 4.1. process of format creation. There will be no Ω need to recompile formats when adding or chang- 3 General philosophy of combined and ing hyphenation patterns. It will also be possi- Babel ble to add new features to hyphenation (auto- In Fig. 1, the reader can see an allegory of how TEX matic processing of German „ck→k-k“, prefer- works: input (the worker on the left) and output ential hyphenations, etc.). 2 Practically, what does this mean for me? 1 At press time Ω has been ported to several UNIX ma- It means that if you are typesetting in some non- chines (Sun, Silicon Graphics and others), DOS (by Kraus American English language covered by current Ba- Kalle) and Macintosh (by Tom Kiffe). 420 TUGboat, Volume 16 (1995), No. 4 (the one on the right) are close together. For exam- the fact that there should be no ‘ff’, ‘fi’, ... ple, consider the fact that hyphenation patterns— ligatures, etc. which are a language-intrinsic feature—are described See 4.4 for a good example of the difference and in the output font encoding. In Fig. 2 you can see combined use of aliases and inherent transforms. how Ω remedies this situation: input and output are clearly separated and, in between, there is a big Hyphenation container (imagine a huge barrel), the Unicode en- Hyphenation must be done on the level where the coding. information is most device-independent: that is, the Whatever you type is first of all converted into Unicode level. Not only can you define hyphenation Unicode. This conversion is language dependent; algorithms using all possible 16-bit characters (for for example, the ASCII character ‘i’ does not mean example to hyphenate Welsh, which uses letters such the same thing in Turkish and in the other Latin- as “ˆw”), but your algorithm is automatically valid alphabet languages. Unicode is very big; so you will for any input or output encoding. We’ll come back hardly ever ask for something not available; even if to this issue later in 1996, when we reach step 3 of that happens there is a “private zone” where we can Ω-Babel development. temporarily store characters of our own choice. Once inside Unicode we deal with pure device- Upper/lowercasing independent information: we can process it in many This is certainly not a trivial process: different let- different ways. In Fig. 2 we list five possible trans- ters may share the same glyph for their upper or Ω forms, all pertaining to -Babel, and we will discuss lower forms (example: both the Icelandic eth “ð” Ω these in turn. The translation processes needed and the Croatian dz “ñ” share the glyph “Д for for every language are activated when you enter the their upper form); letters may have different upper Ω corresponding -Babel environment. Our goal is to forms depending on the semantics of the word (ex- keep the technical aspects hidden: the average user ample: one possible upper form of the German “ß” typesetting in a given language does not need to be is “SS”, another one is “SZ”), or on local traditions aware of the different transformations we have just (in bad French typography, upper forms of accented described. letters are not always accented), or on the language Aliasing itself (example: the upper form of the Turkish letter “i” is “İ” and not “I”—the lower form of “I” is “ı” We call “aliasing” the making of aliases. An alias and not “i”) these are major incompatibilities, and is the expression of a character in some convenient hence we should be able to dynamically change the way: for example in 7-bit ASCII. InGermanBa- upper/lowercasing process. bel, when you write "s instead of \ss{},thisisan Finally, as Martin Dürst pointed out on the alias: (a) it is 7-bit, (b) you can very well avoid it if omega list2, there are six kinds of letter cases: your keyboard and screen support 8-bit characters, 1. regular lowercase (glyph becomes uppercase when and (c) in TEX, it used to be handled using active characters. we apply the uppercasing process); 2. regular uppercase (glyph becomes lowercase when Inherent transforms we apply the lowercasing process); These go deeper than aliases; they are: 3. fixed lowercase (glyph is invariant under the up- 1. either transforms that traditionally belong to percasing process), for example the “m” and TEX syntax, like --- for “—”, or ‘‘ for the En- “b” in the German „GmbH“; glish opening double quote, or ?‘ for the Span- 4. fixed uppercase (glyph is invariant under the ish inverted question mark “¿”; lowercasing process), for example the first letter 2. or transforms that historically derive from dacty- of a name; lographical keyboard traditions (for example, the French << that gets converted into “«” with 5. fake lowercase (the glyph is uppercase, it be- the appropriate spacing, or the Catalan l.l comes lowercase when we apply the uppercas- which produces “l.l”); ing process), for example the “i” in the mod- 3.
Load more

Recommended publications
  • Evaluating the Impact of the Long-S Upon 18Th-Century Encyclopedia Britannica Automatic Subject Metadata Generation Results Sam Grabus
    ARTICLES Evaluating the Impact of the Long-S upon 18th-Century Encyclopedia Britannica Automatic Subject Metadata Generation Results Sam Grabus ABSTRACT This research compares automatic subject metadata generation when the pre-1800s Long-S character is corrected to a standard < s >. The test environment includes entries from the third edition of the Encyclopedia Britannica, and the HIVE automatic subject indexing tool. A comparative study of metadata generated before and after correction of the Long-S demonstrated an average of 26.51 percent potentially relevant terms per entry omitted from results if the Long-S is not corrected. Results confirm that correcting the Long-S increases the availability of terms that can be used for creating quality metadata records. A relationship is also demonstrated between shorter entries and an increase in omitted terms when the Long-S is not corrected. INTRODUCTION The creation of subject metadata for individual documents is long known to support standardized resource discovery and analysis by identifying and connecting resources with similar aboutness.1 In order to address the challenges of scale, automatic or semi-automatic indexing is frequently employed for the generation of subject metadata, particularly for academic articles, where the abstract and title can be used as surrogates in place of indexing the full text. When automatically generating subject metadata for historical humanities full texts that do not have an abstract, anachronistic typographical challenges may arise. One key challenge is that presented by the historical “Long-S” < ſ >. In order to account for these idiosyncrasies, there is a need to understand the impact that they have upon the automatic subject indexing output.
    [Show full text]
  • Whenever There Is a Line Or Tilde Over a Vowel, It Is an Abbreviation for the Letters M Or N. in This Case, the Full Word Is Quadam
    Whenever there is a line or tilde over a vowel, it is an abbreviation for the letters m or n. In this case, the full word is quadam. In this instance, the line over the e represents an omission of the letter n, giving the word debent when written in full. Whenever a word in Latin had an instance of the letter i in succession, the second i was always written as a j. This applies to all words wherein ii is present and also to the Roman numeral ii, which was written as ij. Therefore, cambij = cambii, negotijs = negotiis. The e with a cedilla was an abbreviation for the letters ae. This word spelled out is quae. Following the letter q, a period or semicolon was used as an abbreviation for the letters ue. The first example reads denique, the second one is quacunque. In the seventeenth century, the letter u and v were interchangeable and not yet viewed as two distinct letters. While not universal, a general rule is that if u or v began a word, it was written as a v; if a u or v occurred in the middle or end of a word, it was written as a u. In the 17th century, a lowercase s had two forms- one long and one short. As a general rule, when a lowercase s occurred as the first letter of the word or in any other place in the word except as the final letter, it was written with a long s, which resembles the letter f.
    [Show full text]
  • The English Renaissance in Context: Looking at Older Books
    The English Renaissance in Context: Looking at Older Books The History of the Book Books from the 16th and 17th centuries are both quite similar to and different from books today. The similarities include such things as use of the Codex format, general page layouts, use of title pages, etc. The codex book has been around for a long time. Its roots go back to the age of Cicero, though it only comes into more general use with the spread of Christianity throughout the later Roman Empire in the 4th and 5th centuries CE. Since then, the codex book has undergone a long and gradual evolution during which time the book, its properties, and characteristics became firmly embedded in Western consciousness. Roughly speaking, the general layout of the page that we use today came into existence in the 13th century, with the rise of the universities and the creation of books for study. It is possible, for example, to look at a page in a medieval manuscript and experience a general orientation to it, even if you cannot actually read the text. The evolution of the book, we emphasize, was slow. Such conventions as pagination, title pages, foot or endnotes, tables of contents, indices, et alia are by and large relatively recent additions. We take these features for granted; but prior to the age of Gutenberg, they are hard to find. University of Pennsylvania Libraries - 1 - Furness Shakespeare Collection The English Renaissance in Context: Looking at Older Books Renaissance books can certainly look very different from books today. They exhibit a variety and diversity that have long since been standardized and homogenized.
    [Show full text]
  • Text — Text in Graphs
    Title stata.com text — Text in graphs Description Remarks and examples Also see Description Text elements in Stata graphs, like text in the rest of Stata, can contain Unicode characters. In addition, all text elements in Stata graphs support the use of certain SMCL markup directives, or tags, to affect how they appear on the screen. SMCL, which stands for Stata Markup and Control Language and is pronounced “smickle”, is Stata’s output language, and is discussed in detail in[ P] smcl. All text output in Stata, including text in graphs, can be modified with SMCL. For example, you can italicize a word in a graph title: . scatter mpg weight, title("This is {it:italics} in a graph title") This is italics in a graph title 40 30 Mileage (mpg) 20 10 2,000 3,000 4,000 5,000 Weight (lbs.) This entry documents the features of SMCL that are unique to graphs. We recommend that you have a basic understanding of SMCL before reading this entry; see[ P] smcl. Remarks and examples stata.com Remarks are presented under the following headings: Overview Bold and italics Superscripts and subscripts Fonts, standard Fonts, advanced Greek letters and other symbols Full list of SMCL tags useful in graph text 1 2 text — Text in graphs Overview Assuming you read[ P] smcl before reading this entry, you know about the four syntaxes that SMCL tags follow. As a refresher, the syntaxes are Syntax 1: {xyz} Syntax 2: {xyz:text} Syntax 3: {xyz args} Syntax 4: {xyz args:text} Syntax 1 means “do whatever it is that {xyz} does”.
    [Show full text]
  • Long Directed (S, T)-Path: FPT Algorithm
    Long Directed (s; t)-Path: FPT Algorithm Fedor V. Fomin∗ Daniel Lokshtanovy Fahad Panolanz Saket Saurabhx Meirav Zehavi{ December 13, 2017 Abstract Given a digraph G, two vertices s; t 2 V (G) and a non-negative integer k, the Long Directed (s; t)-Path problem asks whether G has a path of length at least k from s to t. We present a simple algorithm that solves Long Directed (s; t)-Path in time O?(4:884k). This results also in an improvement upon the previous fastest algorithm for Long Directed Cycle. 1 Introduction Given a digraph (directed graph) G, two vertices s; t 2 V (G) and a non-negative integer k, the Long (Directed) (s; t)-Path problem asks whether G has an (s; t)-path (i.e. a path from s to t) of length at least k. Here, the term length refers to the number of vertices on the path, and paths are assumed to be directed simple paths. Observe that Long (s; t)-Path and k-(s; t)-Path are not equivalent problems, where that latter problem asks whether G has an (s; t)-path of length exactly k. Indeed, G may not have any (s; t)-path of length exactly k, or more generally, it may not even have any (s; t)-path of \short" length, but it may have an (s; t)-path of \long" length. For example, the only (s; t)-path of length at least k in G might be a Hamiltonian path. Both Long (s; t)-Path and k-(s; t)-Path are generalizations of the classic k-Path problem, whose objective is to determine whether G has a path of length at least k.
    [Show full text]
  • Nonleaf Patterns in Trees: Protected Nodes and Fine Numbers
    Nonleaf Patterns in Trees: Protected Nodes and Fine Numbers Nachum Dershowitz∗ School of Computer Science Tel Aviv University Ramat Aviv Israel [email protected] The barren and fertile fronds [of the Sensitive Fern] are extremely unlike, the former being leaf-like, very sensitive to frost, quickly wilting when plucked, and much taller and more common than the latter which are non-leaf-like and remain erect, though drying up, through the winter. —Transactions of the Royal Society of Canada (1884) Abstract A closed-form formula is derived for the number of occurrences of matches of a multiset of patterns among all ordered (plane-planted) trees with a given number of edges. A pattern looks like a tree, with internal nodes and leaves, but also contain components that match subtrees or sequences of subtrees. This result extends previous versatile tree-pattern enumeration formulæ to incorporate components that are only allowed to match nonleaf subtrees and provides enumerations of trees by the number of protected (shortest outgoing path has two or more edges) or unprotected nodes. 1 Tree Patterns One routinely asks how often certain patterns occur among a set of combinatorial objects, such as trees. Here, we concern ourselves with patterns in ordered (plane-planted) trees, 1 2n which are counted by the Catalan numbers, Cn = n+1 n , sequence A000108 in Sloane’s Encyclopedia of Integer Sequences [17]. Lattice (Dyck) paths—which may not dip below the abscissa, and very many other interesting objects (including full binary trees), are their ∗Corresponding author. 1 f g ♦y h ♦w ♦x k ♦z Figure 1: The 7-edge 4-leaf tree hhhihiihihhhiiii with labeled nodes for reference.
    [Show full text]
  • Math Symbol Tables
    APPENDIX A Math symbol tables A.1 Hebrew and Greek letters Hebrew letters Type Typeset \aleph ℵ \beth ℶ \daleth ℸ \gimel ℷ © Springer International Publishing AG 2016 481 G. Grätzer, More Math Into LATEX, DOI 10.1007/978-3-319-23796-1 482 Appendix A Math symbol tables Greek letters Lowercase Type Typeset Type Typeset Type Typeset \alpha \iota \sigma \beta \kappa \tau \gamma \lambda \upsilon \delta \mu \phi \epsilon \nu \chi \zeta \xi \psi \eta \pi \omega \theta \rho \varepsilon \varpi \varsigma \vartheta \varrho \varphi \digamma ϝ \varkappa Uppercase Type Typeset Type Typeset Type Typeset \Gamma Γ \Xi Ξ \Phi Φ \Delta Δ \Pi Π \Psi Ψ \Theta Θ \Sigma Σ \Omega Ω \Lambda Λ \Upsilon Υ \varGamma \varXi \varPhi \varDelta \varPi \varPsi \varTheta \varSigma \varOmega \varLambda \varUpsilon A.2 Binary relations 483 A.2 Binary relations Type Typeset Type Typeset < < > > = = : ∶ \in ∈ \ni or \owns ∋ \leq or \le ≤ \geq or \ge ≥ \ll ≪ \gg ≫ \prec ≺ \succ ≻ \preceq ⪯ \succeq ⪰ \sim ∼ \approx ≈ \simeq ≃ \cong ≅ \equiv ≡ \doteq ≐ \subset ⊂ \supset ⊃ \subseteq ⊆ \supseteq ⊇ \sqsubseteq ⊑ \sqsupseteq ⊒ \smile ⌣ \frown ⌢ \perp ⟂ \models ⊧ \mid ∣ \parallel ∥ \vdash ⊢ \dashv ⊣ \propto ∝ \asymp ≍ \bowtie ⋈ \sqsubset ⊏ \sqsupset ⊐ \Join ⨝ Note the \colon command used in ∶ → 2, typed as f \colon x \to x^2 484 Appendix A Math symbol tables More binary relations Type Typeset Type Typeset \leqq ≦ \geqq ≧ \leqslant ⩽ \geqslant ⩾ \eqslantless ⪕ \eqslantgtr ⪖ \lesssim ≲ \gtrsim ≳ \lessapprox ⪅ \gtrapprox ⪆ \approxeq ≊ \lessdot
    [Show full text]
  • Fonts for Latin Paleography 
    FONTS FOR LATIN PALEOGRAPHY Capitalis elegans, capitalis rustica, uncialis, semiuncialis, antiqua cursiva romana, merovingia, insularis majuscula, insularis minuscula, visigothica, beneventana, carolina minuscula, gothica rotunda, gothica textura prescissa, gothica textura quadrata, gothica cursiva, gothica bastarda, humanistica. User's manual 5th edition 2 January 2017 Juan-José Marcos [email protected] Professor of Classics. Plasencia. (Cáceres). Spain. Designer of fonts for ancient scripts and linguistics ALPHABETUM Unicode font http://guindo.pntic.mec.es/jmag0042/alphabet.html PALEOGRAPHIC fonts http://guindo.pntic.mec.es/jmag0042/palefont.html TABLE OF CONTENTS CHAPTER Page Table of contents 2 Introduction 3 Epigraphy and Paleography 3 The Roman majuscule book-hand 4 Square Capitals ( capitalis elegans ) 5 Rustic Capitals ( capitalis rustica ) 8 Uncial script ( uncialis ) 10 Old Roman cursive ( antiqua cursiva romana ) 13 New Roman cursive ( nova cursiva romana ) 16 Half-uncial or Semi-uncial (semiuncialis ) 19 Post-Roman scripts or national hands 22 Germanic script ( scriptura germanica ) 23 Merovingian minuscule ( merovingia , luxoviensis minuscula ) 24 Visigothic minuscule ( visigothica ) 27 Lombardic and Beneventan scripts ( beneventana ) 30 Insular scripts 33 Insular Half-uncial or Insular majuscule ( insularis majuscula ) 33 Insular minuscule or pointed hand ( insularis minuscula ) 38 Caroline minuscule ( carolingia minuscula ) 45 Gothic script ( gothica prescissa , quadrata , rotunda , cursiva , bastarda ) 51 Humanist writing ( humanistica antiqua ) 77 Epilogue 80 Bibliography and resources in the internet 81 Price of the paleographic set of fonts 82 Paleographic fonts for Latin script 2 Juan-José Marcos: [email protected] INTRODUCTION The following pages will give you short descriptions and visual examples of Latin lettering which can be imitated through my package of "Paleographic fonts", closely based on historical models, and specifically designed to reproduce digitally the main Latin handwritings used from the 3 rd to the 15 th century.
    [Show full text]
  • The Brill Typeface User Guide & Complete List of Characters
    The Brill Typeface User Guide & Complete List of Characters Version 2.06, October 31, 2014 Pim Rietbroek Preamble Few typefaces – if any – allow the user to access every Latin character, every IPA character, every diacritic, and to have these combine in a typographically satisfactory manner, in a range of styles (roman, italic, and more); even fewer add full support for Greek, both modern and ancient, with specialised characters that papyrologists and epigraphers need; not to mention coverage of the Slavic languages in the Cyrillic range. The Brill typeface aims to do just that, and to be a tool for all scholars in the humanities; for Brill’s authors and editors; for Brill’s staff and service providers; and finally, for anyone in need of this tool, as long as it is not used for any commercial gain.* There are several fonts in different styles, each of which has the same set of characters as all the others. The Unicode Standard is rigorously adhered to: there is no dependence on the Private Use Area (PUA), as it happens frequently in other fonts with regard to characters carrying rare diacritics or combinations of diacritics. Instead, all alphabetic characters can carry any diacritic or combination of diacritics, even stacked, with automatic correct positioning. This is made possible by the inclusion of all of Unicode’s combining characters and by the application of extensive OpenType Glyph Positioning programming. Credits The Brill fonts are an original design by John Hudson of Tiro Typeworks. Alice Savoie contributed to Brill bold and bold italic. The black-letter (‘Fraktur’) range of characters was made by Karsten Lücke.
    [Show full text]
  • Times and Helvetica Fonts Under Development
    ΩTimes and ΩHelvetica Fonts Under Development: Step One Yannis Haralambous, John Plaice To cite this version: Yannis Haralambous, John Plaice. ΩTimes and ΩHelvetica Fonts Under Development: Step One. Tugboat, TeX Users Group, 1996, Proceedings of the 1996 Annual Meeting, 17 (2), pp.126-146. hal- 02101600 HAL Id: hal-02101600 https://hal.archives-ouvertes.fr/hal-02101600 Submitted on 25 Apr 2019 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. ΩTimes and ΩHelvetica Fonts Under Development: Step One Yannis Haralambous Atelier Fluxus Virus, 187, rue Nationale, F-59800 Lille, France [email protected] John Plaice D´epartement d’informatique, Universit´e Laval, Ste-Foy (Qu´ebec) Canada G1K 7P4 [email protected] TheTruthIsOutThere and publishers request that their texts be typeset —ChrisCARTER, The X-Files (1993) in Times; Helvetica (especially the bold series) is often used as a titling font. Like Computer Modern, Times is a very neutral font that can be used in a Introduction wide range of documents, ranging from poetry to ΩTimes and ΩHelvetica will be public domain technical documentation.. virtual Times- and Helvetica-like fonts based upon It would surely be more fun to prepare a real PostScript fonts, which we call “Glyph Con- Bembo- or Stempel Garamond-like font for the serifs tainers”.
    [Show full text]
  • The Writing Revolution
    9781405154062_1_pre.qxd 8/8/08 4:42 PM Page iii The Writing Revolution Cuneiform to the Internet Amalia E. Gnanadesikan A John Wiley & Sons, Ltd., Publication 9781405154062_1_pre.qxd 8/8/08 4:42 PM Page iv This edition first published 2009 © 2009 Amalia E. Gnanadesikan Blackwell Publishing was acquired by John Wiley & Sons in February 2007. Blackwell’s publishing program has been merged with Wiley’s global Scientific, Technical, and Medical business to form Wiley-Blackwell. Registered Office John Wiley & Sons Ltd, The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ, United Kingdom Editorial Offices 350 Main Street, Malden, MA 02148-5020, USA 9600 Garsington Road, Oxford, OX4 2DQ, UK The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ, UK For details of our global editorial offices, for customer services, and for information about how to apply for permission to reuse the copyright material in this book please see our website at www.wiley.com/wiley-blackwell. The right of Amalia E. Gnanadesikan to be identified as the author of this work has been asserted in accordance with the Copyright, Designs and Patents Act 1988. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, except as permitted by the UK Copyright, Designs and Patents Act 1988, without the prior permission of the publisher. Wiley also publishes its books in a variety of electronic formats. Some content that appears in print may not be available in electronic books. Designations used by companies to distinguish their products are often claimed as trademarks.
    [Show full text]
  • Adobe Framemaker 9 Character Sets
    ADOBE®® FRAMEMAKER 9 Character Sets © 2008 Adobe Systems Incorporated. All rights reserved. Adobe® FrameMaker® 9 Character Sets for Windows® If this guide is distributed with software that includes an end-user agreement, this guide, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. Except as permitted by any such license, no part of this guide may be reproduced, stored in a retrieval system, or trans- mitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of Adobe Systems Incorporated. Please note that the content in this guide is protected under copyright law even if it is not distributed with software that includes an end-user license agreement. The content of this guide is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Adobe Systems Incorpo- rated. Adobe Systems Incorporated assumes no responsibility or liability for any errors or inaccuracies that may appear in the informational content contained in this guide. Please remember that existing artwork or images that you may want to include in your project may be protected under copyright law. The unauthorized incorporation of such material into your new work could be a violation of the rights of the copyright owner. Please be sure to obtain any permission required from the copyright owner. Any references to company names in sample templates are for demonstration purposes only and are not intended to refer to any actual organization.
    [Show full text]