(2016), No. 3 317

Total Page:16

File Type:pdf, Size:1020Kb

(2016), No. 3 317 TUGboat, Volume 37 (2016), No. 3 317 GUST e-foundry font projects fonts and their structure and puts forward a few proposals concerning future works. Bogusław Jackowski, Piotr Strzelczyk and This is not an overly strict report, but rather a Piotr Pianowski story about our technical work on fonts, illustrated What is a document? It is a sequence of rectangles by representative examples which, we hope, show containing a collection of graphic elements. the essence of the matter. In order to keep our nar- What is a font? It is a sequence of rectangles containing ration smooth, we decided not to use formal captions a collection of graphic elements. with explanations to figures and tables (only num- — Marek Ryćko bers of figures and tables are given). The relevant 1 Introduction detailed descriptions always appear in the main text. The Polish TEX Users Group (GUST) has paid at- 2 Historical background tention to the issue of the fonts since the begin- PostScript and T X are genetically related: their ning of its existence. In a way, it was a must, be- E common ancestor is the ingenious idea of a program- cause the repertoire of the diacritical characters of ming language for the description of documents un- the Computer Modern family of fonts (CM), “canon- derstood as a sequence of rectangular pages filled ical” T X family defined as the Metafont programs E with letters and graphics. Both projects were de- (see [5]), turned out to be insufficient for the Polish vised nearly at the same time — at the turn of the language. The efforts of the GUST font team (GUST 1970s to the 1980s.1 And both are still alive and e-foundry), led by Bogusław Jackowski, were kindly well, proving that the idea behind both projects was acknowledged by the professor Donald E. Knuth: indeed brilliant. From our perspective, the most important thing in common, and at the same time a key distinc- tive element, was the different handling of fonts and graphics; in other words, both systems clearly distin- guished illustrations from fonts. That approach was justified by the computer technology at that time. For both TEX and PostScript, fonts were exter- nal entities, both used metric files plus files defining glyph shapes, both defined contours as Bézier splines Obviously, our first fonts were PK bitmap fonts pro- (planar polynomials of the 3rd degree), and for both grammed using Metafont. Alas, the TEX/Metafont fonts were to be prepared separately with dedicated bitmap font format never became the world-wide font programs, prior to creating documents. standard. Therefore, the next step were fonts in the And this exhausts the list of similarities. PostScript Type 1 format which fairly soon became TEX worked with binary metric files, TFM; its obsolescent and was replaced by the OpenType for- output, a device independent file (DVI), was pro- mat (OTF, a joint enterprise of Microsoft and Adobe, cessed by so-called drivers which made use of the 1996, see [31]) which is actually a common container “proper” fonts, that is, the relevant bitmap collec- for the Adobe PostScript Type1 and Microsoft True- tions, and produced output that could be sent to a Type (TTF) formats. In 2007, Microsoft extended printer or to a screen. The bitmaps were prepared the OTF standard with the capability of typesetting independently with the Metafont program(s) which math formulas, largely based on ideas developed for interpreted scripts written in the Metafont language TEX, and implemented it in MS Office. Soon, TEX and generated TFM and bitmap files. engines were adapted to process such math OTF In Metafont, the shapes of glyphs are defined fonts. Therefore our recent fonts are released in the as Bézier curves, stroked with a “pen” and/or filled. OpenType format, which also makes them easily us- Basic PostScript fonts (i.e., Type 1; see [28]) able outside of the TEX realm. employ contours defined as non-intersecting closed So far, no OTF successor is in sight, which is Bézier outlines which can only be filled.2 The “filled both good and bad (cf. Section 7.4). 1 We published our partial results successively as Formally, TEX was released a little earlier—TEX in 1982, PostScript in 1984, both with earlier work. the work progressed. This paper provides an overall 2 summary of our work: it describes the collections of The PostScript Type 1 documentation [28], p. 34, men- tions the possibility of stroking: a Type 1 font program can fonts prepared by the GUST e-foundry, deals with also be stroked along its outline when the user changes the some technical issues related to the generation of PaintType entry in the font dictionary to 2. In this case, GUST e-foundry font projects 318 TUGboat, Volume 37 (2016), No. 3 outline” paradigm relates also to the Microsoft TTF 3.1 Our tools format and, thereby, to the OTF format. Our primary tool was MetaPost [4], a successor of PostScript Type1 fonts are usually (but not nec- Metafont, which promised well as a tool for mak- essarily) accompanied by corresponding ASCII met- ing PostScript Type 1 fonts due to its native Post- ric files (AFM), not used by the interpreters of the Script output. We called our MetaPost-based pack- PostScript language. In the Microsoft Windows op- age MetaType 1 [13]. It was instantiated as a set of erating system, making an already complex situa- scripts using, besides MetaPost, T1utils, that is, Lee tion even more complex, binary printer font met- Hetherington’s (dis)assembler for PostScript Type 1 ric files (PFM) were introduced for Windows drivers fonts (cf. [3, 4]). A few scripts written in Gawk and that used PostScript Type 1 fonts. Perl were also employed. For a long time, only commercial programs for On the one hand, such a simple approach turned generating PostScript Type 1 fonts were available. out to be insufficient for generating OTF fonts, in Only in 2001, George Williams released his remark- particular OTF math fonts. On the other hand, it able FontForge program (initially dubbed PfaEdit; turned out to be flexible enough to include an extra [25]). FontForge can generate outline fonts in many external step for making OTF fonts. For text fonts, formats, including PostScript Type 1 and OTF. we employed the Adobe Font Development Kit for PostScript was promptly (and rightly) hailed as OpenType (AFDKO [26]); for math fonts, the Font- the standard for printers and, more importantly, for Forge library governed by Python scripts [15, 25]. phototypesetters, therefore a driver converting DVI In the future, we want replace AFDKO by a Font- files to PostScript became necessary. Fortunately Forge+Python utility (cf. Section 7). for TEXies, PostScript is equipped also with Type 3 A set of MetaPost macros in the MetaType 1 fonts; glyphs in Type 3 fonts can be represented by package defines two important procedures, essential nearly arbitrary graphic objects, in particular, by for generating non-intersecting outlines and heavily bitmaps, therefore the making of a PostScript driver used in our font programs: finding a common outline for converting DVI files to PostScript was possible al- for overlapping figures, known also as removing over- ready in 1986, when Dvips, the first and still most laps, and finding the outline of a pen stroke, known popular driver was released by Tomas Rokicki. (It’s as expanding strokes or finding the pen envelope. a pity that the idea of Type 3 fonts was not sup- Another important feature, hinting, is imple- ported and developed by Adobe.) mented, but, in the end, we decided to avoid man- There were a few unsuccessful attempts to con- ual hinting, since it is difficult to control and yields vert the basic TEX font collection, CM, to the Post- mediocre results. Metafont has no notion of hint- Script Type 1 format automatically, thus preserving ing — the Metafont language simply offers rounding. the parameterization. The main hindrance was the Moreover, the language for describing outlines in excessive usage of stroked (both painted and erased) PostScript Type 1 fonts cannot express even as triv- elements in the CM font programs, while, as was ial a mathematical operation as rounding. mentioned previously, the PostScript Type 1 and For low-resolution devices, controlled rounding OTF formats accept only filled shapes. is crucial — hence the idea of “hinting”, that is, con- The “filled outline” paradigm was a convenient trolled rounding. Alas, hinting algorithms remain optimization at the beginning of the computer type- undisclosed, especially with regard to commercial setting era, when, for example, the generating of the typesetting devices such as phototypesetters. One complete collection of bitmaps for the CM fonts at can presume, however, that low-resolution devices resolution, say, 240 dots per inch (typical for dot are bound to disappear sooner rather than later: the matrix printers) took a few days. Nowadays, the resolution of display devices has reached almost 600 paradigm still thrives by virtue of tradition: there dpi and 1200 dpi (and more) for printers is nowa- is an abundance of such fonts and, and what is worse, days nothing special. Therefore, running with the all operating systems support only this kind of font. hare and hunting with the hounds, we decided to 3 First steps hint our recently released OTF fonts automatically with FontForge. Taking the above into account, we made up our minds to design our own programmable system for generating fonts in “world-compatible” formats. 3.2 Trying our tools out overlapping subpaths will be visible in the output; this yields undesirable visual results in outlined characters. In practice, We tested our newborn MetaType 1 engine against this possibility is not used.
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]
  • B.Casselman,Mathematical Illustrations,A Manual Of
    1 0 0 setrgbcolor newpath 0 0 1 0 360 arc stroke newpath Preface 1 0 1 0 360 arc stroke This book will show how to use PostScript for producing mathematical graphics, at several levels of sophistication. It includes also some discussion of the mathematics involved in computer graphics as well as a few remarks about good style in mathematical illustration. To explain mathematics well often requires good illustrations, and computers in our age have changed drastically the potential of graphical output for this purpose. There are many aspects to this change. The most apparent is that computers allow one to produce graphics output of sheer volume never before imagined. A less obvious one is that they have made it possible for amateurs to produce their own illustrations of professional quality. Possible, but not easy, and certainly not as easy as it is to produce their own mathematical writing with Donald Knuth’s program TEX. In spite of the advances in technology over the past 50 years, it is still not a trivial matter to come up routinely with figures that show exactly what you want them to show, exactly where you want them to show it. This is to some extent inevitable—pictures at their best contain a lot of information, and almost by definition this means that they are capable of wide variety. It is surely not possible to come up with a really simple tool that will let you create easily all the graphics you want to create—the range of possibilities is just too large.
    [Show full text]
  • Uniform Rendering of XML Encoded Mathematical Content with Opentype Fonts
    i \eutypon24-25" | 2011/1/21 | 8:58 | page 11 | #15 i i i Εὔτυπon, τεῦχος 24-25 — >Okt¸brioc/October 2010 11 Uniform Rendering of XML Encoded Mathematical Content with OpenType Fonts Apostolos Syropoulos 366, 28th October Str. GR-671 00 Xanthi Greece E-mail: asyropoulos at yahoo dot com The new OpenType MATH font table contains important information that can be used to correctly and uniformly render mathematical con- tent (e.g., mathematical formulae, equations, etc.). Until now, all sys- tems in order to render XML encoded mathematical content employed some standard algorithms together with some standard sets of TrueType and/or Type 1 fonts, which contained the necessary glyphs. Unfortu- nately, this approach does not produce uniform results because certain parameters (e.g., the thickness of the fraction line, the scale factor of superscripts/subscripts, etc.) are system-dependant, that is, their exact values will depend on the particular setup of a given system. Fortunately, the new OpenType MATH table can be used to remedy this situation. In particular, by extending renderers so as to be able to render mathemat- ical contents with user-specified fonts, the result will be uniform across systems and platforms. In other words, the proposed technology would allow mathematical content to be rendered the same way ordinary text is rendered across platforms and systems. 1 Introduction The OpenType font format is a new cross-platform font file format developed jointly by Adobe and Microsoft. OpenType fonts may contain glyphs with ei- ther cubic B´eziersplines (used in PostScript fonts) or with quadratic B´ezier splines (used in TrueType fonts).
    [Show full text]
  • Goldsmiths Research Online
    CORE Metadata, citation and similar papers at core.ac.uk Provided by Goldsmiths Research Online GOLDSMITHS Research Online Article (refereed) Mukhopadhyay, Bhaskar Dream kitsch – folk art, indigenous media and '9/11': The Work of Pat in the Era of Electronic Transmission Originally published in Journal of Material Culture Copyright Sage. The publisher's version is available at: http://mcu.sagepub.com/cgi/content/abstract/13/1/5 Please cite the publisher's version. You may cite this version as: Mukhopadhyay, Bhaskar, 2008. Dream kitsch – folk art, indigenous media and '9/11': The Work of Pat in the Era of Electronic Transmission. Journal of Material Culture, 13 (1). pp. 5-34. ISSN 1460-3586 [Article]: Goldsmiths Research Online. Available at: http://eprints.gold.ac.uk/2371/ This document is the author’s final manuscript version of the journal article, incorporating any revisions agreed during peer review. Some differences between this version and the publisher’s version remain. You are advised to consult the publisher’s version if you wish to cite from it. Copyright © and Moral Rights for the papers on this site are retained by the individual authors and/or other copyright owners. http://eprints-gro.goldsmiths.ac.uk Contact Goldsmiths Research Online at: [email protected] Dream kitsch – folk art, indigenous media and ‘9/11’: The work of pat in the era of electronic transmission Bhaskar Mukhopadhyay This article explores the process of transmission of the image(s) of 9/11 through an ethnographic/art-historical examination of Bengali (Indian) pat (traditional scroll painting) made by a community of rural Indian artisans with little or no exposure to mass-media.
    [Show full text]
  • Resources Ton 'QX Repository (For Details, Contact Peter Ab- Bott, E-Mail Address Above)
    TUGboat, Volume 10 (1989), No. 2 Janet users may obtain back issues from the As- Resources ton 'QX repository (for details, contact Peter Ab- bott, e-mail address above). DECnetISPAN users may obtain back issues from the European (con- Announcing (belatedly) -MAG tact Massimo Calvani, fisicaQastrpd.infn. it) or American (contact Ed Bell, 7388 : :bell) DECnet Don Hosek T)?J repositories. University of Illinois at Chicago Others with network access should send a mes- After being chided for not publicizing my electronic sage to archive-serverQsun.soe.clarkson.edu "magazine" enough, I have decided to make a formal with the first line being path followed by an address announcement of its availability to the 'J&X cornmu- from Clarkson to you, and then a line nity at large. get texmag texmag.v.nn What is =MAG? for each back issue desired where v is the volume number and nn the issue number. The line index WMAG is available free of charge to anyone reach- texmag will give a list of back issues available. able by electronic mail and is published approxi- A typical mail request may resemble: mately every two months. The subject material index t exmag generally falls somewhere between the somewhat get texmag texmag.l.08 chaotic (but still useful) correspondence of 'QXHAX and UKW, and the printed matter in TUGboat How do I submit articles to TEXMAG? and QXline. Some previous articles have included I was hoping you would ask. Articles are accepted an early version of Dominik Wujastyk's article on on all aspects of T)?J, M'QX, and METAFONT from fonts from TUB 9#2; an overview of the differ- specific information on interfacing graphics packages ent font files used by 'QX, METAFONT, and device with particular DVI drivers to general information drivers; macros for commutative diagrams and sim- on macro writing to product reviews to whatever ple chemical equations and many other topics.
    [Show full text]
  • Font HOWTO Font HOWTO
    Font HOWTO Font HOWTO Table of Contents Font HOWTO......................................................................................................................................................1 Donovan Rebbechi, elflord@panix.com..................................................................................................1 1.Introduction...........................................................................................................................................1 2.Fonts 101 −− A Quick Introduction to Fonts........................................................................................1 3.Fonts 102 −− Typography.....................................................................................................................1 4.Making Fonts Available To X..............................................................................................................1 5.Making Fonts Available To Ghostscript...............................................................................................1 6.True Type to Type1 Conversion...........................................................................................................2 7.WYSIWYG Publishing and Fonts........................................................................................................2 8.TeX / LaTeX.........................................................................................................................................2 9.Getting Fonts For Linux.......................................................................................................................2
    [Show full text]
  • Fira Code: Monospaced Font with Programming Ligatures
    Personal Open source Business Explore Pricing Blog Support This repository Sign in Sign up tonsky / FiraCode Watch 282 Star 9,014 Fork 255 Code Issues 74 Pull requests 1 Projects 0 Wiki Pulse Graphs Monospaced font with programming ligatures 145 commits 1 branch 15 releases 32 contributors OFL-1.1 master New pull request Find file Clone or download lf- committed with tonsky Add mintty to the ligatures-unsupported list (#284) Latest commit d7dbc2d 16 days ago distr Version 1.203 (added `__`, closes #120) a month ago showcases Version 1.203 (added `__`, closes #120) a month ago .gitignore - Removed `!!!` `???` `;;;` `&&&` `|||` `=~` (closes #167) `~~~` `%%%` 3 months ago FiraCode.glyphs Version 1.203 (added `__`, closes #120) a month ago LICENSE version 0.6 a year ago README.md Add mintty to the ligatures-unsupported list (#284) 16 days ago gen_calt.clj Removed `/**` `**/` and disabled ligatures for `/*/` `*/*` sequences … 2 months ago release.sh removed Retina weight from webfonts 3 months ago README.md Fira Code: monospaced font with programming ligatures Problem Programmers use a lot of symbols, often encoded with several characters. For the human brain, sequences like -> , <= or := are single logical tokens, even if they take two or three characters on the screen. Your eye spends a non-zero amount of energy to scan, parse and join multiple characters into a single logical one. Ideally, all programming languages should be designed with full-fledged Unicode symbols for operators, but that’s not the case yet. Solution Download v1.203 · How to install · News & updates Fira Code is an extension of the Fira Mono font containing a set of ligatures for common programming multi-character combinations.
    [Show full text]
  • Opentype Postscript Fonts with Unusual Units-Per-Em Values
    Luigi Scarso VOORJAAR 2010 73 OpenType PostScript fonts with unusual units-per-em values Abstract Symbola is an example of OpenType font with TrueType OpenType fonts with Postscript outline are usually defined outlines which has been designed to match the style of in a dimensionless workspace of 1000×1000 units per em Computer Modern font. (upm). Adobe Reader exhibits a strange behaviour with pdf documents that embed an OpenType PostScript font with A brief note about bitmap fonts: among others, Adobe unusual upm: this paper describes a solution implemented has published a “Glyph Bitmap Distribution Format by LuaTEX that resolves this problem. (BDF)” [2] and with fontforge it’s easy to convert a bdf font into an opentype one without outlines. A fairly Keywords complete bdf font is http://unifoundry.com/unifont-5.1 LuaTeX, ConTeXt Mark IV, OpenType, FontMatrix. .20080820.bdf.gz: this Vle can be converted to an Open- type format unifontmedium.otf with fontforge and it Introduction can inspected with showttf, a C program from [3]. Here is an example of glyph U+26A5 MALE AND FEMALE Opentype is a font format that encompasses three kinds SIGN: of widely used fonts: 1. outline fonts with cubic Bézier curves, sometimes Glyph 9887 ( uni26A5) starts at 492 length=17 referred to CFF fonts or PostScript fonts; height=12 width=8 sbX=4 sbY=10 advance=16 2. outline fonts with quadratic Bézier curve, sometimes Bit aligned referred to TrueType fonts; .....*** 3. bitmap fonts. ......** .....*.* Nowadays in digital typography an outline font is almost ..***... the only choice and no longer there is a relevant diUer- .*...*.
    [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]
  • CM-Super: Automatic Creation of Efficient Type 1 Fonts from Metafont
    CM-Super: Automatic creation of efficient Type 1 fonts from METAFONT fonts Vladimir Volovich Voronezh State University Moskovsky prosp. 109/1, kv. 75, Voronezh 304077 Russia [email protected] Abstract In this article I describe making the CM-Super fonts: Type 1 fonts converted from METAFONT sources of various Computer Modern font families. The fonts contain a large number of glyphs covering writing in dozens of languages (Latin-based, Cyrillic-based, etc.) and provide outline replacements for the original METAFONT fonts. The CM-Super fonts were produced by tracing the high resolution bitmaps generated by METAFONT with the help of TEXtrace, optimizing and hinting the fonts with FontLab, and applying cleanups and optimizations with Perl scripts. 1 The idea behind the CM-Super fonts There exist free Type 1 versions of the original CM The Computer Modern (CM) fonts are the default fonts, provided by Blue Sky Research, Elsevier Sci- ence, IBM Corporation, the Society for Industrial and most commonly used text fonts with TEX. Orig- inally, CM fonts contained only basic Latin letters, and Applied Mathematics (SIAM), Springer-Verlag, and thus covered only the English language. There Y&Y and the American Mathematical Society, but are however a number of Computer Modern look- until not long ago there were no free Type 1 versions alike METAFONT fonts developed which cover other of other “CM look-alike” fonts available, which lim- languages and scripts. Just to name a few: ited their usage in PDF and PostScript target docu- ment formats. The CM-Super fonts were developed • EC and TC fonts, developed by J¨orgKnappen, to cover this gap.
    [Show full text]
  • FONT GUIDE Workbook to Help You Find the Right One for Your Brand
    FONT GUIDE Workbook to help you find the right one for your brand. www.ottocreative.com.au Choosing the right font for your brand YOUR BRAND VALUES: How different font styles can be used to make up your brand: Logo Typeface: Is usually a bit more special and packed with your brands personality. This font should be used sparingly and kept for special occasions. Headings font: Logo Font This font will reflect the same brand values as your logo font - eg in this example both fonts are feminine and elegant. Headings Unlike your logo typeface, this font should be easier to read and look good a number of different sizes and thicknesses. Body copy Body font: The main rule here is that this font MUST be easy to read, both digitally and for print. If there is already alot going on in your logo and heading font, keep this style simple. Typefaces, common associations & popular font styles San Serif: Clean, Modern, Neutral Try these: Roboto, Open Sans, Lato, Montserrat, Raleway Serif: Classic, Traditional, reliable Try these: Playfair Display, Lora, Source Serif Pro, Prata, Gentium Basic Slab Serif: Youthful, modern, approachable Try these: Roboto Slab, Merriweather, Slabo 27px, Bitter, Arvo Script: Feminine, Romantic, Elegant Try these: Dancing Script, Pacifico, Satisfy, Courgette, Great Vibes Monotype:Simple, Technical, Futuristic Try these: Source Code Pro, Nanum Gothic Coding, Fira Mono, Cutive Mono Handwritten: Authentic, casual, creative Try these: Indie Flower, Shadows into light, Amatic SC, Caveat, Kalam Display: Playful, fun, personality galore Try these: Lobster, Abril Fatface, Luckiest Guy, Bangers, Monoton NOTE: Be careful when using handwritten and display fonts, as they can be hard to read.
    [Show full text]
  • The New Font Project: TEX Gyre
    Hans Hagen, Jerzy Ludwichowski, Volker Schaa NAJAAR 2006 47 The New Font Project: TEX Gyre Abstract metric and encoding files for each font. We look for- In this short presentation, we will introduce a new ward to an extended TFM format which will lift this re- project: the “lm-ization” of the free fonts that come striction and, in conjunction with OpenType, simplify with T X distributions. We will discuss the project E delivery and usage of fonts in TEX. objectives, timeline and cross-lug funding aspects. We especially look forward to assistance from pdfTEX users, because the pdfTEX team is working on the implementation on the support for OpenType Introduction fonts. An important consideration from Hans Hagen: “In The New Font Project is a brainchild of Hans Ha- the end, even Ghostscript will benefit, so I can even gen, triggered mainly by the very good reception imagine those fonts ending up in the Ghostscript dis- of the Latin Modern (LM) font project by the TEX tribution.” community. After consulting other LUG leaders, The idea of preparing such font families was sug- Bogusław Jackowski and Janusz M. Nowacki, aka gested by the pdfTEX development team. Their pro- “GUST type.foundry”, were asked to formulate the pro- posal triggered a lively discussion by an informal ject. group of representatives of several TEX user groups — The next section contains its outline, as prepared notably Karl Berry (TUG), Hans Hagen (NTG), Jerzy by Bogusław Jackowski and Janusz M. Nowacki. The Ludwichowski (GUST), Volker RW Schaa (DANTE)— remaining sections were written by us. who suggested that we should approach this project as a research, technical and implementation team, and Project outline promised their help in taking care of promotion, integ- ration, supervising and financing.
    [Show full text]