DOCSLIB.ORG

Cork' Math Font Encoding?

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Cork' Math Font Encoding? Introduction Text font encodings Math font encodings OpenType math Summary Do we need a ‘Cork’ math font encoding? Dr. Ulrik Vieth Stuttgart, Germany TUG 2008, Cork, Ireland Introduction Text font encodings Math font encodings OpenType math Summary What’s in this talk? • Some history of font encodings • Some review of recent developments • Some discussion of future plans • Font encodings (Unicode) • Font technology (OpenType) • New math fonts for new TEX engines Introduction Text font encodings Math font encodings OpenType math Summary Situation at Cork 1990 • TEX was undergoing major transition phase in 1989–90 • TEX version 3.0 just released in early 1990 • Support for multiple languages added • Support for 8-bit font encodings added • European TEX users groups founded in 1989–90 • European users strongly interested in new features • Better hyphenation of accented languages • Better font support of accented languages • European users started to work on fonts and encodings • European users agreed font encoding for 8-bit fonts ⇒ ‘Cork’ encoding, named after conference site Introduction Text font encodings Math font encodings OpenType math Summary Benefits of the ‘Cork’ encoding • Success of the ‘Cork’ encoding • provided model for further 8-bit text font encoding • provided support for many/most European languages • started further developments in font encodings • Some design decisions done right • provided complete 7-bit ASCII subset (no exceptions) • consistent encoding for all font shapes (no variations) • consistent organization of uppercase/lowercase codes • no inter-dependencies between text and math fonts Introduction Text font encodings Math font encodings OpenType math Summary Shortcomings of the ‘Cork’ encoding • Some design shortcomings and their consequences • did not follow any standards (e.g. ISO Latin 1 or 2) ⇒ discrepancies between input and output encodings ⇒ solved in 1993–94 by LATEX 2ε inputenc, fontenc • tried to support many languages, but couldn’t support all ⇒ local encodings (QX, CS, L7X) used besides ‘Cork’ ⇒ solved in recent years by Latin Modern/TEX Gyre fonts • did not leave room for text symbols in font table ⇒ workarounds involving encoding switches to 7-bit fonts ⇒ solved in 1995 by adding text symbol encoding (TS1) • did not consider available glyph set of PS fonts ⇒ virtual fonts needed to fake some glyphs ⇒ 2 virtual fonts (T1, TS1) needed on top of real fonts ⇒ alternative encodings (LY1) proposed besides ‘Cork’ Introduction Text font encodings Math font encodings OpenType math Summary Summary of text font encodings today • What became of the ‘Cork’ encoding • adopted and followed by additional encodings (Tn) • supplemented by text symbol encoding (TS1) • complemented by local encodings (QX, CS, L7x) • complemented by alternative encodings (LY1) • Font encoding mess in current TEX systems • no single 8-bit font encoding can serve all needs • many different 8-bit font encodings needed instead • resolved only by moving to Unicode/OpenType • Latin Modern and TEX Gyre fonts • provide consistent implementations of many encodings • full glyph set available only in Unicode/OpenType fonts • many subsets available in 8-bit encodings/Type 1 fonts Introduction Text font encodings Math font encodings OpenType math Summary Situation at Cork 2008 • TEX is undergoing another major transition phase • Recent developments • PDF output has largely replaced DVI and PS output • Scalable fonts have largely replaced bitmap PK fonts • Ongoing developments • Unicode and OpenType are starting to replace 8-bit fonts • Unicode and OpenType supported by new fonts and engines • New TEX fonts (Latin Modern, TEX Gyre) widely adopted • New TEX engines (X TE EX, LuaTEX) are becoming available • What’s missing? • Support for OpenType math in new TEX engines • Development of math fonts for Latin Modern, TEX Gyre Introduction Text font encodings Math font encodings OpenType math Summary History of math font encodings • Developments of math fonts • 7-bit text and math fonts developed simultaneously, driven by need to typeset books like TAOCP • 8-bit text font encodings developed by themselves, driven by need to support European languages • Need for 8-bit math fonts recognized early on, but not driven by specific user needs • Reasons for new math fonts • remove inter-dependencies between text and math fonts • improve organization of new 8-bit math font encodings • support more symbols in same number of fonts (16 x 256) • provide consistent encodings for different font families Introduction Text font encodings Math font encodings OpenType math Summary Progress on math font encodings • The ’Aston’ proposal (1993) • Research work on math fonts organized by LATEX3 project • Results presented at TUG 1993 (Aston University, UK) • Proposal for organization of 8-bit math font encodings • Activities discontinued after a few months • The ‘newmath’ prototype (1997–98) • Development work driven by some individual volunteers • Implementation based on ideas of ‘Aston’ proposal • Prototype based on METAFONT and fontinst work • Several font families supported (CM, Euler, MathTime) • Results presented at EuroTEX 1998 (St. Malo, France) • Activities side-tracked by other developments Introduction Text font encodings Math font encodings OpenType math Summary Progress on math font encodings • The Unicode math efforts (1998–2002) • Project to bring math symbols into Unicode (driven by AMS) • Research work to collect references of math symbol • Committee work to get symbols accepted in Unicode • Results are part of Unicode standard since 3.2 • The STIX fonts (1998–current) • Project to develop Unicode math fonts by science publishers • 1st beta in late 2007, 2nd beta expected in mid 2008 • Organization of fonts still under development • TEX support still missing, still to be developed Introduction Text font encodings Math font encodings OpenType math Summary Recent developments on math font technology • OpenType math in MS Office 2007 • Outside developments continued while waiting for STIX fonts • Microsoft implemented math support in MS Office 2007 • OpenType font format extended by new MATH table • Cambria Math font commissioned as reference implementation • Acceptance of OpenType math • many concepts and ideas from TEX adopted by Microsoft • officially still experimental, but already de facto standard • widely deployed to installations of MS Office 2007 • adopted by independent font developers (Asana Math) • adopted and supported by FontForge font editor • adopted and supported by new TEX engines (X TE EX) Introduction Text font encodings Math font encodings OpenType math Summary Recent developments on math font technology • OpenType math support in new TEX engines • X TE EX support for OpenType math added since late 2007 • X TE EX support widely available soon with TEX Live 2008 • LuaTEX support still to be developed, but likely to follow • OpenType math support in new TEX fonts ? • likely agreement to adopt OpenType math in new TEX engines • likely agreement to adopt OpenType math in new TEX fonts • font encoding becomes non-issue with Unicode math ⇒ no more need for a ‘Cork’ math font encoding • font technology becomes all-important with OpenType math Introduction Text font encodings Math font encodings OpenType math Summary Features of OpenType math • OpenType font format • developed jointly by Adobe and Microsoft • not really open, but vendor-controlled format • based on concepts from PS (CFF) and TT fonts • uses extensible table structure from TT fonts • supports ‘advanced’ typographic features • glyph positioning (GPOS table) • glyph substitutions (GSUB table) • options controlled at user-level by feature tags • encoding based on glyph names from Unicode • possible to have unencoded glyph variants • MATH table just another optional table meaningful only by interpretation in software Introduction Text font encodings Math font encodings OpenType math Summary OpenType MATH table • Font-specific (global) parameters • essential for spacing of big operators, fractions, indices, etc • similar to fontdimen parameters in TEX fonts (Appendix G) • some OpenType parameters correspond to TEX parameters • some OpenType parameters generalize TEX default values • a few TEX parameters don’t have clear correspondence • internal mapping in TEX engines some workarounds • Glyph-specific metric information • encoded in TEX math fonts by overloading existing TFM fields • provided in OpenType MATH table in clear data structures • some generalization of TEX concepts (cut-ins in 4 corners) Introduction Text font encodings Math font encodings OpenType math Summary Horizontal and vertical constructions • Math extension fonts use special TFM features • one code point = series of next-larger glyph variants • optionally followed by recipe for extensible symbol • TFM features used only in limited contexts in TEX • big operators: 2 vertical sizes • big delimiters: n vertical sizes + extensible version • wide accents: n horizontal sizes, but no extensible • Concepts generalized in OpenType math • vertical variants and constructions (operators, delimiters) • horizontal variants and constructions (wide accents) • also applicable to overbrace/underbrace or long arrows • variant glyphs remain unencoded, accessed only indirectly Introduction Text font encodings Math font encodings OpenType math Summary Math alphabets • Math fonts in TEX organized into 16 families of 8-bit fonts • one alphabet per family (roman, italic, script, etc) • selection of symbols distributed across remaining slots
Load more

Recommended publications
  • 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]
  • Latex2ε Font Selection
    LATEX 2" font selection © Copyright 1995{2021, LATEX Project Team.∗ All rights reserved. March 2021 Contents 1 Introduction2 1.1 LATEX 2" fonts.............................2 1.2 Overview...............................2 1.3 Further information.........................3 2 Text fonts4 2.1 Text font attributes.........................4 2.2 Selection commands.........................7 2.3 Internals................................8 2.4 Parameters for author commands..................9 2.5 Special font declaration commands................. 10 3 Math fonts 11 3.1 Math font attributes......................... 11 3.2 Selection commands......................... 12 3.3 Declaring math versions....................... 13 3.4 Declaring math alphabets...................... 13 3.5 Declaring symbol fonts........................ 14 3.6 Declaring math symbols....................... 15 3.7 Declaring math sizes......................... 17 4 Font installation 17 4.1 Font definition files.......................... 17 4.2 Font definition file commands.................... 18 4.3 Font file loading information..................... 19 4.4 Size functions............................. 20 5 Encodings 21 5.1 The fontenc package......................... 21 5.2 Encoding definition file commands................. 22 5.3 Default definitions.......................... 25 5.4 Encoding defaults........................... 26 5.5 Case changing............................. 27 ∗Thanks to Arash Esbati for documenting the newer NFSS features of 2020 1 6 Miscellanea 27 6.1 Font substitution..........................
    [Show full text]
  • Baskerville Volume 9 Number 2
    Baskerville The Annals of the UK TEX Users Group Guest Editor: Dominik Wujastyk Vol. 9 No. 2 ISSN 1354–5930 August 1999 Baskerville is set in Monotype Baskerville, with Computer Modern Typewriter for literal text. Editing, production and distribution are undertaken by members of the Committee. Contributions and correspondence should be sent to [email protected]. Editorial The Guest Editor of the last issue of Baskerville, James Foster, maintainer of this FAQ, many people have contributed to it, explained in that issue how members of the UK-TUG Com- as is explained in the introduction below. mittee have assumed editorial responsibility for the prepara- The TEX FAQ has been published in Baskerville twice be- tion and formatting of individual numbers of the newsletter. fore, in 1994 and 1995. These are the issues of Baskerville Like James, I am deeply grateful for, and awed by, the amount which I have most often lent or recommended to other TEX of work and expertise which Sebastian Rahtz has put into users. In fact, I currently do not have the 1995 FAQ issue past issues of Baskerville. Thanks, Sebastian! because I gave it away to someone who needed it as a mat- James also mentioned the hard work which Robin ter of urgency! I am confident that this newly updated TEX Fairbairns has done over the years in producing and distrib- FAQ, now expanded to cover 126 questions, will be every bit uting Baskerville. Although Robin is now liberated from these as popular and useful as its predecessors, and will save TEX particular tasks, he is still heavily involved in supporting the users many hours of valuable time.
    [Show full text]
  • TEX Support for the Fontsite 500 Cd 30 May 2003 · Version 1.1
    TEX support for the FontSite 500 cd 30 May 2003 · Version 1.1 Christopher League Here is how much of TeX’s memory you used: 3474 strings out of 12477 34936 string characters out of 89681 55201 words of memory out of 263001 3098 multiletter control sequences out of 10000+0 1137577 words of font info for 1647 fonts, out of 2000000 for 2000 Copyright © 2002 Christopher League [email protected] Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. The FontSite and The FontSite 500 cd are trademarks of Title Wave Studios, 3841 Fourth Avenue, Suite 126, San Diego, ca 92103. i Table of Contents 1 Copying ........................................ 1 2 Announcing .................................... 2 User-visible changes ..................................... 3 3 Installing....................................... 5 3.1 Find a suitable texmf tree............................. 5 3.2 Copy files into the tree .............................. 5 3.3 Tell drivers how to use the fonts ...................... 6 3.4 Test your installation ................................ 7 3.5 Other applications .................................. 8 3.6 Notes for Windows users ............................ 9 3.7 Notes for Mac users................................. 9 4 Using ......................................... 10 4.1 With TeX ........................................ 10 4.2 Accessing expert sets ............................... 11 4.3 Using CombiNumerals ............................
    [Show full text]
  • A Practical Guide to LATEX Tips and Tricks
    Luca Merciadri A Practical Guide to LATEX Tips and Tricks October 7, 2011 This page intentionally left blank. To all LATEX lovers who gave me the opportunity to learn a new way of not only writing things, but thinking them ...Claudio Beccari, Karl Berry, David Carlisle, Robin Fairbairns, Enrico Gregorio, Stefan Kottwitz, Frank Mittelbach, Martin M¨unch, Heiko Oberdiek, Chris Rowley, Marc van Dongen, Joseph Wright, . This page intentionally left blank. Contents Part I Standard Documents 1 Major Tricks .............................................. 7 1.1 Allowing ............................................... 10 1.1.1 Linebreaks After Comma in Math Mode.............. 10 1.2 Avoiding ............................................... 11 1.2.1 Erroneous Logic Formulae .......................... 11 1.2.2 Erroneous References for Floats ..................... 12 1.3 Counting ............................................... 14 1.3.1 Introduction ...................................... 14 1.3.2 Equations For an Appendix ......................... 16 1.3.3 Examples ........................................ 16 1.3.4 Rows In Tables ................................... 16 1.4 Creating ............................................... 17 1.4.1 Counters ......................................... 17 1.4.2 Enumerate Lists With a Star ....................... 17 1.4.3 Math Math Operators ............................. 18 1.4.4 Math Operators ................................... 19 1.4.5 New Abstract Environments ........................ 20 1.4.6 Quotation Marks Using
    [Show full text]
  • Bibliography and Index
    TLC2, ch-end.tex,v: 1.39, 2004/03/19 p.963 Bibliography [1] Adobe Systems Incorporated. Adobe Type 1 Font Format. Addison-Wes- ley, Reading, MA, USA, 1990. ISBN 0-201-57044-0. The “black book” contains the specifications for Adobe’s Type 1 font format and describes how to create a Type 1 font program. The book explains the specifics of the Type 1 syntax (a subset of PostScript), including information on the structure of font programs, ways to specify computer outlines, and the contents of the various font dictionaries. It also covers encryption, subroutines, and hints. http://partners.adobe.com/asn/developer/pdfs/tn/T1Format.pdf [2] Adobe Systems Incorporated. “PostScript document structuring conven- tions specification (version 3.0)”. Technical Note 5001, 1992. This technical note defines a standard set of document structuring conventions (DSC), which will help ensure that a PostScript document is device independent. DSC allows PostScript language programs to communicate their document structure and printing requirements to document managers in a way that does not affect the PostScript language page description. http://partners.adobe.com/asn/developer/pdfs/tn/5001.DSC_Spec.pdf [3] Adobe Systems Incorporated. “Encapsulated PostScript file format specifi- cation (version 3.0)”. Technical Note 5002, 1992. This technical note details the Encapsulated PostScript file (epsf) format, a standard format for importing and exporting PostScript language files among applications in a variety of heteroge- neous environments. The epsf format is based on and conforms to the document structuring conventions (DSC) [2]. http://partners.adobe.com/asn/developer/pdfs/tn/5002.EPSF_Spec.pdf [4] Adobe Systems Incorporated.
    [Show full text]
  • ISDI Metadata Profile Volume 1
    ISDI Metadata Profile (spatial data sets and data set series) Irish Spatial Data Infrastructure ISDI Metadata Profile Version 1.2 Volume 1 Spatial Dataset and Spatial Dataset Series Department of Environment, Community And Local Government 2013 1 ISDI Metadata Profile (spatial data sets and data set series) Purpose of this Document The purpose of this document is to provide the outline of the partner agreed ISDI Metadata Profile and to identify the metadata elements required to accurately describe a spatial dataset or a spatial dataset series managed by the organisations in the Irish Spatial Data Infrastructure. Revision History Version Description Author Date 1.0 ISDI Metadata Profile (spatial Trevor Alcorn 31/05/2011 datasets and dataset series) version 1.0 1.1 Ad-hoc edits Gareth John 01/10/2012 1.2 Version 1.2 revision Trevor Alcorn 07/01/2013 Gareth John 2 ISDI Metadata Profile (spatial data sets and data set series) Contents 1. Overview of ISDI Metadata Profile....................................................5 2 ISDI Metadata Profile for spatial dataset and spatial dataset series...............................................................................................8 2.1 ISDI “dataset” Metadata Profile of ISO 19115:2005 ....................8 2.2 Metadata for geographic data ................................................9 2.3 Metadata sections ...............................................................9 3 Metadata section descriptions ........................................................10 3.1 Metadata entity set
    [Show full text]
  • The Stix2 Package
    The stix2 package STI Pub Companies∗ Version 2.0.2, 2021/01/14 Contents 1 Introduction 2 2 Background 2 3 Usage 3 3.1 Options.............................................3 3.2 Compatibility with other packages..............................3 3.3 Feedback............................................3 4 Math alphabets 4 5 Math symbols 4 5.1 Alphabetics...........................................4 5.2 Ordinary symbols.......................................5 5.3 Binary operators........................................9 5.4 Relations............................................ 11 5.5 Punctuation.......................................... 19 5.6 Integrals............................................ 19 5.7 Big operators.......................................... 20 5.8 Delimiters........................................... 20 5.9 Other bracess.......................................... 22 5.10 Accents............................................. 22 5.11 Over and under brackets.................................... 23 5.12 Radicals............................................. 23 6 Font tables 24 6.1 Text fonts............................................ 24 6.2 Math fonts........................................... 31 ∗This package was developed by Khaled Hosny on behalf of the STI Pub companies, who gratefully acknowledge his eorts. 1 1 Introduction The STIX fonts are a set of OpenType fonts designed for use with typesetting engines such as X TE EX or LuaTEX that directly support Unicode and modern font technologies. When used with one of these engines, no extra support is needed beyond the unicode-math package. This is the recommended way of using the STIX fonts with TEX. The most recent version of the STIX fonts can be found at https: //github.com/stipub/stixfonts. The stix2 package provides support for versions of TEX that are limited to TFM les, Type 1 PostScript fonts, and 8-bit font encodings. Version 2.0.0 of the STIX fonts are being released in this format in hopes of easing the transition from legacy TEX engines to modern fully Unicode-compatible systems.
    [Show full text]
  • GLP-1 Action in the Mouse Bed Nucleus of the Stria Terminalis
    Neuropharmacology 131 (2018) 83e95 Contents lists available at ScienceDirect Neuropharmacology journal homepage: www.elsevier.com/locate/neuropharm GLP-1 action in the mouse bed nucleus of the stria terminalis Diana L. Williams a, Nicole A. Lilly a, Ian J. Edwards b, Pallas Yao b, 1, James E. Richards b, * Stefan Trapp b, a Psychology Department & Program in Neuroscience, Florida State University, USA b Centre for Cardiovascular and Metabolic Neuroscience, Department of Neuroscience, Physiology & Pharmacology, University College London, London, WC1E 6BT, UK article info abstract Article history: Glucagon-like peptide-1 (GLP-1) injected into the brain reduces food intake. Similarly, activation of Received 6 June 2017 preproglucagon (PPG) cells in the hindbrain which synthesize GLP-1, reduces food intake. However, it is Received in revised form far from clear whether this happens because of satiety, nausea, reduced reward, or even stress. Here we 13 October 2017 explore the role of the bed nucleus of the stria terminalis (BNST), an area involved in feeding control as Accepted 3 December 2017 well as stress responses, in GLP-1 responses. Available online 6 December 2017 Using cre-expressing mice we visualized projections of NTS PPG neurons and GLP-1R-expressing BNST cells with AAV-driven Channelrhodopsin-YFP expression. The BNST displayed many varicose YFPþ PPG Keywords: Glucagon-like peptide-1 receptor axons in the ventral and less in the dorsal regions. Mice which express RFP in GLP-1R neurons had þ Electrophysiology RFP cells throughout the BNST with the highest density in the dorsal part, suggesting that PPG neuron- Channelrhodopsin derived GLP-1 acts in the BNST.
    [Show full text]
  • Towards Lucida Opentype Afm2tfm
    TUGboat, Volume 32 (2011), No. 2 169 Another incarnation of Lucida: now be set up for use with TEX using fontinst or Towards Lucida OpenType afm2tfm. This development continued when PDFTEX was Ulrik Vieth and Mojca Miklavec developed and on-screen viewing of PDF files came Abstract into common use in the late 1990s. While the use of METAFONT-generated bitmap TEX has been in existence for more than 30 years. fonts packaged into Type 3 fonts was still acceptable During this time, TEX engines and device drivers for printing, such bitmap fonts turned out to be in- have gone through multiple generations of font tech- adequate for screen rendering in PDF viewers. As a nology: METAFONT, PostScript Type 1, and Open- result, the use of METAFONT fonts became unpop- Type. While choices for text fonts have greatly in- ular, and efforts were undertaken to provide Type 1 creased, there have always been few choices for math replacements for METAFONT fonts. fonts and even fewer for complete font families. In this era, choices of text fonts were increased The Lucida family of typefaces by Bigelow & significantly, but choices of math fonts remained lim- Holmes is a notable exception, as it provides not ited. Besides CM and AMS Euler, converted from only a math font, but also a complete font family, METAFONT, there were only the commercial offer- consisting of a large repertoire of serif, sans-serif, ings of MathTime and Lucida New Math at first. monospace, and fancy variants. Unfortunately, the It was only much later in this era that more current distribution of Lucida fonts dates back to choices of math fonts eventually became available, 1993 and is limited by the use of PostScript Type 1 such as txfonts, pxfonts, mathpazo, fourier, and fonts, which support only 8-bit character sets.
    [Show full text]
  • The Kerntest Package
    The kerntest package Harald Harders [email protected] Version v1.32 (2004/04/14), printed 14th April 2004 Abstract This class makes it easy to generate tables that show many different kerning pairs of an arbitrary font, usable by LATEX. It shows the kerning values that are used by the the font by default. In addition, this class enables the user to alternate the kernings and to observe the results. Kerning pairs can be defined for groups of similar glyphs at once. Automatically, an mtx file is generated that can be loaded by fontinst to introduce the user-made kernings into the virtual font for LATEX. Contents 1 Introduction 2 2 Usage of the class 3 2.1 Introduction . 3 2.2 Most features by example . 5 2.3 Encoding-dependent parameters . 8 2.4 Advanced features . 9 3 Configuration file 10 4 Kerning pairs that are often missing 10 4.1 Character combinations . 11 4.2 Quotation marks . 11 5 An example of how to optimize a font 12 6 The implementation 16 6.1 Class file . 17 6.1.1 Glyph classes . 33 6.1.2 Extra commands for special encodings . 40 6.2 Footer of mtx file . 40 6.3 Class option files . 41 6.3.1 T1 encoding . 41 6.3.2 TS1 encoding . 47 6.3.3 OT1 encoding . 52 6.3.4 T2A encoding . 58 1 6.3.5 T2A encoding . 63 6.3.6 LY1 encoding . 68 6.4 Templates . 72 6.4.1 T1 encoding . 73 6.4.2 TS1 encoding .
    [Show full text]
  • Language and Fonts TEX in Polish
    language and fonts TEX in Polish Erik Frambach Jak masz na imie?˛ Jak sie, Pani nazywa? = What’s your Faculty of Economics name? University of Groningen Miło mi cie˛ (pana, pania)˛ poznac´ = Nice meeting you [email protected] Jak sie,˛ masz? Jak sie˛ pan ma? = How are you? Dobrze = Good abstract Zle´ = Bad Writing in Polish with TEX requires a few tricks. In Polish you Tak sobie; Jako tako = Alright need several accents that are often not available in ‘standard’ Gdzie jest toaleta? = Where is the toilet? fonts. Some TEX macros can solve this problem more or less. We will show the pros and cons. Another ‘problem’ is input encoding. One can use 8-bit input Polish problems in combination with the corresponding codepage definition, or a 7-bit encoding with a few extras to make typing easier. When writing Polish text in TEX we have to deal with the Both methods will be discussed. following problems: This article reflects the content of a lecture held at the NTG meeting on 11 November 1999. TEX accents: The acute accent is used a lot: e.g. n,´ s,´ c,´ ó. The dot ac- keywords cent is also used in Polish: ˙z.Both are readily available in Polish, ogonek, input encoding all fonts and can be accessed using the standard TEX com- mands \’ and \. respectively. These accents are acceptable but could be improved. E.g., the dot accent may seem too thick and the \’ accent should be flattened slightly when Dzien´ dobry! applied to capitals. There is a Polish version of the Com- Any idea what the following text means? puter Modern fonts that implements these changes.
    [Show full text]