MFPIC: Pictures in TEX with Metafont and Metapost∗ Daniel H

Total Page:16

File Type:pdf, Size:1020Kb

Load more

MFPIC: Pictures in TEX with Metafont and MetaPost∗ Daniel H. Luecking† Thomas E. Leathrum Geoffrey Tobin 2012/12/03 Contents 1 Introduction1 1.1 Why?.........................................1 1.2 Who?.........................................1 1.3 What?.........................................1 1.4 How?.........................................2 2 Options. 5 2.1 metapost, metafont, \usemetapost, \usemetafont................5 2.2 mplabels, \usemplabels, \nomplabels.......................5 2.3 overlaylabels, \overlaylabels, \nooverlaylabels................6 2.4 truebbox, \usetruebbox, \notruebbox.......................6 2.5 clip, \clipmfpic, \noclipmfpic...........................6 2.6 centeredcaptions, \usecenteredcaptions, \nocenteredcaptions.......6 2.7 raggedcaptions, \useraggedcaptions, \noraggedcaptions...........7 2.8 debug, \mfpicdebugtrue, \mfpicdebugfalse...................7 2.9 clearsymbols, \clearsymbols, \noclearsymbols.................7 2.10 draft, final, nowrite, \mfpicdraft, \mfpicfinal, \mfpicnowrite........7 2.11 mfpreadlog, \mfpreadlog...............................8 2.12 Scoping Rules.....................................8 3 METAFONT and METAPOST Data Types.9 3.1 Numerics and pairs...................................9 3.2 Colors..........................................9 3.3 Paths, pictures and booleans.............................. 10 4 The Macros. 11 4.1 Files and Environments................................ 11 4.2 Common objects.................................... 13 4.2.1 Points, lines, and rectangles......................... 14 4.2.2 A word about list arguments......................... 15 4.2.3 Axes, axis marks, and grids......................... 16 4.2.4 Circles, arcs and ellipses........................... 20 4.2.5 Curves.................................... 23 4.2.6 Bar charts and pie charts........................... 24 4.2.7 Braces..................................... 26 MFPIC version: 1.10. ∗Copywrite 2002–2012, Daniel H. Luecking †[email protected]: Communications regarding MFPIC should be sent to this author. Any first-person references in this manual refer to Dr. Luecking. i CONTENTS ii 4.3 Colors in MFPIC.................................... 26 4.3.1 METAPOST color functions.......................... 26 4.3.2 Establishing MFPIC default colors...................... 28 4.3.3 Defining a color name............................ 29 4.3.4 METAFONT colors.............................. 29 4.4 Modifying the figures................................. 29 4.4.1 Closure of paths............................... 30 4.4.2 Reversal, connection and other path modifications............. 31 4.4.3 Arrows.................................... 33 4.5 Rendering figures.................................... 35 4.5.1 Drawing.................................... 35 4.5.2 Shading, filling, erasing, clipping, hatching................. 37 4.5.3 Changing the default rendering........................ 41 4.5.4 Examples................................... 41 4.6 Functions and Plotting................................. 41 4.6.1 Defining functions.............................. 41 4.6.2 Plotting functions............................... 42 4.6.3 Plotting external data files.......................... 46 4.7 Labels and Captions.................................. 49 4.7.1 Setting text.................................. 49 4.7.2 Curves surrounding text........................... 53 4.8 Saving and Reusing an MFPIC Picture......................... 54 4.9 Picture Frames..................................... 55 4.10 Affine Transforms................................... 55 4.10.1 Transforming the METAFONT coordinate system.............. 55 4.10.2 Transforming paths.............................. 56 4.11 Parameters....................................... 59 4.12 For Advanced Users.................................. 63 4.12.1 Splines.................................... 63 4.12.2 Béziers.................................... 64 4.12.3 Raw METAFONT code............................ 65 4.12.4 Creating METAFONT variables........................ 65 4.12.5 Miscelaneous pair expressions........................ 68 4.12.6 Manipulating METAFONT picture variables................. 69 4.12.7 METAFONT loops.............................. 71 4.12.8 Miscellaneous................................ 73 5 Appendices 79 5.1 Acknowledgements................................... 79 5.2 Changes History.................................... 79 5.3 Summary of Options.................................. 79 5.4 Plotting Styles for \plotdata............................. 80 5.5 Special Considerations When Using METAFONT................... 81 5.6 Special Considerations When Using METAPOST................... 81 5.6.1 Required support............................... 81 5.6.2 METAPOST is not METAFONT ........................ 82 5.6.3 Graphic inclusion............................... 83 5.7 MFPIC and the Rest of the World........................... 84 CONTENTS iii 5.7.1 The literature................................. 84 5.7.2 Other programs................................ 85 5.8 Index of commands, options and parameters..................... 86 5.9 List of commands by type............................... 91 5.9.1 Figures.................................... 91 5.9.2 Renderings.................................. 91 5.9.3 Arrows.................................... 91 5.9.4 Modifying figures.............................. 92 5.9.5 Lengths.................................... 92 5.9.6 Coordinate transformation.......................... 92 5.9.7 Symbols, axes, grids, marks......................... 92 5.9.8 Symbol names................................ 93 5.9.9 Setting options................................ 93 5.9.10 Setting values................................. 93 5.9.11 Setting colors................................. 93 5.9.12 Defining arrays................................ 93 5.9.13 Changing behavior.............................. 94 5.9.14 Files and environments............................ 94 5.9.15 Text...................................... 94 5.9.16 Miscellaneous................................ 94 1 Introduction 1.1 Why? Tom got the idea for MFPIC1 mostly out of a feeling of frustration. Different output mechanisms for printing or viewing TEX DVI files each have their own ways to include pictures. More often than not, there are provisions for including graphic objects into a DVI file using TEX \special’s. However, this technique seemed far from TEX’s ideal of device independence because different TEX output drivers recognize different \special’s, and handle them in different ways. LATEX’s picture environment has a hopelessly limited supply of available objects to draw—if you want to draw a graph of a polynomial curve, you’re out of luck. There was, of course, PICTEX, which was wonderfully flexible and general, but its most obvious feature was its speed—or rather lack of it. Processing a single picture in PICTEX (in those days) could often take several seconds. It occurred to Tom that it might be possible to take advantage of the fact that METAFONT is designed for drawing things. The result of pursuing this idea was MFPIC, a set of macros for TEX and METAFONT which incorporate METAFONT-drawn pictures into a TEX file. With the creation of METAPOST by John Hobby, and the almost universal availability of free POSTSCRIPT interpreters like GHOSTSCRIPT, some MFPIC users wanted to run their MFPIC output through METAPOST, to produce POSTSCRIPT pictures. Moreover, users wanted to be able to use pdfTEX, which did not get along well with PK fonts, but was quite happy with METAPOST pictures. So METAPOST support was added to MFPIC. This got us a little bit away from device independence, but many users were not much concerned with that: they just wanted a convenient way to have text and pictures described in the same document file. With the extra capabilities of POSTSCRIPT (e.g., color) and the corresponding abilities of META- POST, there was a demand for some MFPIC interface to access them. Consequently, switches (op- tions) have been added to access some of them. When these are used, output files may no longer be compatible with METAFONT. 1.2 Who? The original MFPIC (and still the core of the current version) was written primarily by Tom Leathrum during the late (northern hemisphere) spring and summer of 1992, while at Dartmouth College. Different versions were being written and tested for nearly two years after that, during which time Tom finished his Ph.D. and took a job at Berry College, in Rome, GA. Between fall of 1992 and fall of 1993, much of the development was carried out by others. Those who helped most in this process are credited in the Acknowledgements. Somewhere in the mid 1990’s the development passed to Geoffrey Tobin who kept things going for several years. The addition of METAPOST support was carried out by Dan Luecking around 1997–99. He is also responsible for all other additions and changes since then, with help from Geoffrey and a few others mentioned in the Acknowledgements. 1.3 What? See the README file for a list of files in the distribution and a brief explanation of each. Only three are actually needed for full access to MFPIC’s capabilities: mfpic.dtx, mfpic.ins and grafbase.dtx. Running LATEX on mfpic.ins creates the only required files: mfpic.tex and mfpic.sty, the latter required only for LATEX. grafbase.mf, required only if METAFONT will be processing figures. 1‘MFPIC’ is pronounced by spelling the first two letters: ‘em-eff-pick’. 1 1.4 HOW? 2 grafbase.mp, dvipsnam.mp and mfpicdef.tex, needed only if METAPOST will
Recommended publications
  • Resources Ton 'QX Repository (For Details, Contact Peter Ab- Bott, E-Mail Address Above)

    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.
  • Font HOWTO Font HOWTO

    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
  • Surviving the TEX Font Encoding Mess Understanding The

    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.
  • CM-Super: Automatic Creation of Efficient Type 1 Fonts from Metafont

    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.
  • Using Fonts Installed in Local Texlive - Tex - Latex Stack Exchange

    Using Fonts Installed in Local Texlive - Tex - Latex Stack Exchange

    27-04-2015 Using fonts installed in local texlive - TeX - LaTeX Stack Exchange sign up log in tour help TeX ­ LaTeX Stack Exchange is a question and answer site for users of TeX, LaTeX, ConTeXt, and related Take the 2­minute tour × typesetting systems. It's 100% free, no registration required. Using fonts installed in local texlive I have installed texlive at ~/texlive . I have installed collection­fontsrecommended using tlmgr . Now, ~/texlive/2014/texmf­dist/fonts/ has several folders: afm , cmap , enc , ... , vf . Here is the output of tlmgr info helvetic package: helvetic category: Package shortdesc: URW "Base 35" font pack for LaTeX. longdesc: A set of fonts for use as "drop­in" replacements for Adobe's basic set, comprising: ­ Century Schoolbook (substituting for Adobe's New Century Schoolbook); ­ Dingbats (substituting for Adobe's Zapf Dingbats); ­ Nimbus Mono L (substituting for Abobe's Courier); ­ Nimbus Roman No9 L (substituting for Adobe's Times); ­ Nimbus Sans L (substituting for Adobe's Helvetica); ­ Standard Symbols L (substituting for Adobe's Symbol); ­ URW Bookman; ­ URW Chancery L Medium Italic (substituting for Adobe's Zapf Chancery); ­ URW Gothic L Book (substituting for Adobe's Avant Garde); and ­ URW Palladio L (substituting for Adobe's Palatino). installed: Yes revision: 31835 sizes: run: 2377k relocatable: No cat­date: 2012­06­06 22:57:48 +0200 cat­license: gpl collection: collection­fontsrecommended But when I try to compile: \documentclass{article} \usepackage{helvetic} \begin{document} Hello World! \end{document} It gives an error: ! LaTeX Error: File `helvetic.sty' not found. Type X to quit or <RETURN> to proceed, or enter new name.
  • About Basictex-2021

    About Basictex-2021

    About BasicTeX-2021 Richard Koch January 2, 2021 1 Introduction Most TeX distributions for Mac OS X are based on TeX Live, the reference edition of TeX produced by TeX User Groups across the world. Among these is MacTeX, which installs the full TeX Live as well as front ends, Ghostscript, and other utilities | everything needed to use TeX on the Mac. To obtain it, go to http://tug.org/mactex. 2 Basic TeX BasicTeX (92 MB) is an installation package for Mac OS X based on TeX Live 2021. Unlike MacTeX, this package is deliberately small. Yet it contains all of the standard tools needed to write TeX documents, including TeX, LaTeX, pdfTeX, MetaFont, dvips, MetaPost, and XeTeX. It would be dangerous to construct a new distribution by going directly to CTAN or the Web and collecting useful style files, fonts and so forth. Such a distribution would run into support issues as the creators move on to other projects. Luckily, the TeX Live install script has its own notion of \installation packages" and collections of such packages to make \installation schemes." BasicTeX is constructed by running the TeX Live install script and choosing the \small" scheme. Thus it is a subset of the full TeX Live with exactly the TeX Live directory structure and configuration scripts. Moreover, BasicTeX contains tlmgr, the TeX Live Manager software introduced in TeX Live 2008, which can install additional packages over the network. So it will be easy for users to add missing packages if needed. Since it is important that the install package come directly from the standard TeX Live distribution, I'm going to explain exactly how I installed TeX to produce the install package.
  • The TEX Font Panel

    The TEX Font Panel

    The TEX Font Panel Nelson H. F. Beebe (chair) Center for Scientific Computing University of Utah Department of Mathematics, 322 INSCC 155 S 1400 E RM 233 Salt Lake City, UT 84112-0090 USA Email: [email protected], [email protected], [email protected], [email protected] (Internet) WWW URL: http://www.math.utah.edu/~beebe Telephone: +1 801 581 5254 FAX: +1 801 585 1640, +1 801 581 4148 Internet: [email protected] Introduction Since most programming languages, operating systems, file systems, and even computer I/O and The TUG’2001 Font Panel convened on Thursday, CPU chips, have character knowledge designed into August 16, 2001, with members William Adams, them, changing the character set has huge ramifica- Nelson H. F. Beebe (chair), Barbara Beeton, Hans tions for the computing industry and for worldwide Hagen, Alan Hoenig, and Ross Moore, with active business data processing, data exchange, and record participation by several attendees in the audience. keeping. The list of topics that was projected on the screen Fortunately, a particular encoding scheme makes up the sectional headings in what follows, and called UTF-8 makes it possible for files encoded in the topics are largely independent. pure ASCII to also be Unicode in UTF-8 encoding, Any errors or omissions in this article are solely easing the transition to the new character set. the fault of the panel chair. Up to version 2.0 in 1996, the Unicode character repertoire could be fit into a table of 216 = 65 536 en- Unicode tries. Version 3.0 in 2000 increased the count to over The work of the Unicode Consortium, begun in a million, although just under 50 000 are assigned 1988, and first reported on for the TEX community and tabulated in the book.
  • Proposal to Represent the Slashed Zero Variant of Empty

    Proposal to Represent the Slashed Zero Variant of Empty

    L2/15-268 Title: Proposal to Represent the Slashed Zero Variant of Empty Set Source: Barbara Beeton (American Mathematical Society), Asmus Freytag (ASMUS, Inc.), Laurențiu Iancu and Murray Sargent III (Microsoft Corporation) Status: Individual contribution Action: For consideration by the Unicode Technical Committee Date: 2015-10-30 Abstract As of Unicode Version 8.0, the symbol for empty set is encoded as the character U+2205 EMPTY SET, with no standardized variation sequences. In scientific publications, the symbol is typeset in one of three var- iant forms, chosen by notational style: a slashed circle, ∅, a slashed wide oval in the shape a letter, ∅, or a slashed narrow oval in the shape of a digit zero, . The slashed circle and the slashed zero forms are the most widely used, and correspond to the LaTeX commands \varnothing and \emptyset, respectively. Having one Unicode representation to map to, fonts that provide glyphs for more than one form of the symbol typically implement a stylistic variant or a mapping to a PUA code point. However, the wide- spread use of the slashed zero variant and its mapping to the main LaTeX command for the symbol, \emptyset, make it a candidate for a dedicated means to distinctly represent it in Unicode. This document evaluates three approaches for representing in Unicode the slashed zero variant of the empty set symbol and proposes a solution based on a variation sequence. Additional related characters resulting from the investigation and needed to complete the solution are also proposed for encoding. 1. The empty set symbol 1.1. Historical references The introduction of the modern symbol for the empty set is attributed to André Weil of the Nicholas Bourbaki group.
  • Metatype Project: Creating Truetype Fonts Based on M

    Metatype Project: Creating Truetype Fonts Based on M

    Metatype project: creating TrueType fonts based on Metafont Serge Vakulenko Cronyx Engineering, Moscow Russia [email protected] http://www.vak.ru/proj/metatype Abstract The purpose of Metatype project is the development of freeware TrueType fonts for generic user community. Metafont language is chosen for creating character glyphs. Currently, glyph im- ages are converted to cubic outlines using bitmap tracing algorithm, and then to conic outlines. Two font families are currently been under development as a part of Metatype project: 1. TeX font family, based on Computer Modern fonts by Donald E. Knuth, retaining their “look and feel”. A rich set of typefaces is available, including Roman, Sans Serif, Monotype and Math faces with Normal, Bold, Italic, Bold Italic, Narrow and Wide variations. 2. Maestro font family is designed, as a Times-lookalike. It also uses Computer Mod- ern sources, with a lot of modifications. Why TrueType? representation of text strings. Far-seeing operational sys- tems, such as Windows NT, provide support Unicode at The world becomes closer. Now we observe, how the a kernel level. Word-processors use Unicode for stor- Internet and globalization of economics cause increase age of documents (XML, RTF and other formats). The of intensity of contacts between representatives of dif- amount of Internet sites with Unicode encoding grows ferent peoples, cultures, races. The world becomes more every day. Cellular telephones use Unicode for Inter- and more multilingual. The computer branch for a long net browsing (WAP). The world is slowly moving toward time has realized this fact: the draft variant of standard Unicode. And TrueType seems to be a natural result of Unicode is dated 1989 [1].
  • Making Type 1 and Opentype Fonts with Metatype1 and Fontforge

    Making Type 1 and OpenType fonts with MetaType1 and FontForge Karel Píška Institute of Physics, Academy of Sciences Prague, Czech Republic 24 August 2008 2nd ConTEXt Meeting Bohinj, Slovenija Contents Type 1 v.s. OpenType OpenType fonts today TEX text OpenType fonts OpenType math fonts today Stage 1: Font creating with MetaType1 Examples with Latin Modern Stage 2: From Type 1 to OpenType Construction of OpenType Conclusion and suggestions Conclusion and suggestions TEX Gyre fonts and math OpenType tables Last comments Type 1 v.s. OpenType (probably everybody knows) Limitations in Type 1 I max.number of encoded glyphs – 256 I we need many encoding files to cover various languages and their encodings (9 or more in today’s Latin Modern and TEX Gyre) I metrics data (also ligatures, kernings, . ) in additional separated files (× the number of encodings) OpenType fonts I can cover all characters together with metrics and “advances typographic facilities” I are available for XeTEX, LuaTEX I allow to unify access to glyphs, hyphenation patterns, . OpenType fonts today TEX text OpenType fonts I Latin Modern (LMRoman10-Regular) old style digits present I TEX Gyre (TeXGyreTermes-Regular) old style digits, small caps I Antykwa Torunska I Iwona I Kurier and, maybe, other OpenType fonts today OpenType math fonts I Cambria Math [MicroSoft] I old style digits I math symbols I letters: regular, bold, (math) italic, small caps, subscript, superscript, script-script, etc. I see (MS specification) I Minion Math [Jonannes Küster] I Asana Math [Apostolos Syropoulos] (glyph list) special optical sizes for scripts and scriptscrips are absent (?) I STIX not available after beta-testing (?) I other OpenType math ? Stage 1: Font creating with MetaType1 The fonts can be generated with the MetaType1 package [authors B.
  • THE MATHALPHA, AKA MATHALFA PACKAGE the Math Alphabets

    THE MATHALPHA, AKA MATHALFA PACKAGE the Math Alphabets

    THE MATHALPHA, AKA MATHALFA PACKAGE MICHAEL SHARPE The math alphabets normally addressed via the macros \mathcal, \mathbb, \mathfrak and \mathscr are in a number of cases not well-adapted to the LATEX math font structure. Some suffer from one or more of the following defects: • font sizes are locked into a sequence that was appropriate for metafont{generated rather than scalable fonts; • there is no option in the loading package to enable scaling; • the font metrics are designed for text rather than math mode, leading to awkward spacing, subscript placement and accent placement when used for the latter; • the means of selecting a set of math alphabets varies from package to package. The goal of this package is to provide remedies for the above, where possible. This means, in effect, providing virtual fonts with my personal effort at correcting the metric issues, rewriting the font-loading macros usually found in a .sty and/or .fd files to admit a scale factor in all cases, and providing a .sty file which is extensible and from which any such math alphabet may be specified using a standard recipe. For example, the following fonts are potentially suitable as targets for \mathcal or \mathscr and are either included as part of TEXLive 2011, as free downloads from CTAN or other free sources, or from commercial sites. cm % Computer Modern Math Italic (cmsy) euler % euscript rsfs % Ralph Smith Formal Script---heavily sloped rsfso % based on rsfs, much less sloped lucida % From Lucida New Math (commercial) mathpi % Adobe Mathematical Pi or clones thereof
  • Optimal Use of Fonts on Linux

    Optimal Use of Fonts on Linux

    Optimal Use of Fonts on Linux Avi Alkalay Donovan Rebbechi Hal Burgiss Copyright © 2006 Avi Alkalay, Donovan Rebbechi, Hal Burgiss 2007−04−15 Revision History Revision 2007−04−15 15 Apr 2007 Revised by: avi Included support to SUSE installation for the RPM scriptlets on template spec file, listed SUSE as a BCI−enabled distro. Revision 2007−02−08 08 Feb 2007 Revised by: avi Fixed some typos, updated Luc's page URL, added DejaVu sections, added link to FC6 Freetype RPMs, added link to Debian MS Core fonts, and added reference to the gnome−font−properties command. Revision 2006−07−02 02 Jul 2006 Revised by: avi Included link to Debian FreeType BCI package, improved the glossary with Latin1 descriptions, more clear links on the webcore fonts section, instructions on how to rebuild source RPM packages in the BCI appendix, updated the freetype recompilation appendix to cover new versions of the lib, authorship section reorganized. Revision 2006−04−02 02 Apr 2006 Revised by: avi Included link to FC5 Freetype.bci contribution by Cody DeHaan. Revision 2006−03−25 25 Mar 2006 Revised by: avi Updated link to BCI Freetype RPMs to be more distro version specific. Revision 2005−07−19 19 May 2005 Revised by: avi Renamed Microsoft Fonts to Webcore Fonts, and links updated.Added X.org Subsystems section. Revision 2005−05−25 25 May 2005 Revised by: avi Comment related to web pages in the Microsoft Fonts section Revision 2005−05−10 10 May 2005 Revised by: avi Old section−based glossary converted to real DocBook glossary.Modernized terms and explanations on the glossary.Included concepts as charsets, Unicode and UTF−8 in the glossary.