A Tex/Latex Enthusiast's View
Total Page:16
File Type:pdf, Size:1020Kb

Load more
Recommended publications
-
MS Hatch-Waxman PTE REQUEST for EXTENSION of PATENT
Docket No.: 029420.0155-US02 (PATENT) IN THE UNITED STATES PATENT AND TRADEMARK OFFICE In re United States Patent of: Alan J. Korman, et aL. Patent No.: 7,605,238 Issued: October 20, 2009 For: HUMAN CTLA-4 ANTIBODIES MS Hatch-Waxman PTE Commissioner for Patents Offce of Patent Legal Administration Room MDW 7D55 600 Dulany Street (Madison Building) Alexandria, VA 223 14 REQUEST FOR EXTENSION OF PATENT TERM UNDER 35 U.S.C. §156 Sir: Pursuant to 35 U.S.C. §156 and 37 C.F.R. §§1.710-1.791, Medarex, Inc., the current address of which is Route 206 and Province Line Road, Princeton, New Jersey 08540 ("Applicant" or "Medarex"), hereby requests an extension of U.S. Patent No. 7,605,238 (the "'238 patent"). As permitted by 37 C.F.R. §1.785(b) and MPEP §2761, Applicant is concurrently fiing a request for patent term extension of U.S. Patent No. 6,984,720 based upon the same regulatory review period. Medarex represents that it is the owner and assignee of the entire interest in and to Letters Patent of the United States No. 7,605,238 (Exhibit 1) granted to Alan J. Korman, Edward L. Halk, Nils Lonberg, Yashwant M. Deo and Tibor P. Keler (the "inventors") on October 20, 2009, for "Human CTLA-4 Antibodies and Their Uses" by virtue of an assignment from the DC; 3983891.1 Patent No.: 7,605,238 - 2- Docket No.: 029420.0155-US02 Alan J. Korman, Edward L. Halk and Nils Lonberg to Medarex, recorded in the United States Patent and Trademark Offce ("PTO") on March 6, 2003 at Reel 013817, Frame 0628 and an assignment from Yashwant M. -
B2bi 2.5 Support Reference Catalog 3 Accessibility
B2Bi Version 2.5 April 2019 Support Reference Catalog Copyright © 2019 Axway All rights reserved. This documentation describes the following Axway software: Axway B2Bi 2.5 No part of this publication may be reproduced, transmitted, stored in a retrieval system, or translated into any human or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without the prior written permission of the copyright owner, Axway. This document, provided for informational purposes only, may be subject to significant modification. The descriptions and information in this document may not necessarily accurately represent or reflect the current or planned functions of this product. Axway may change this publication, the product described herein, or both. These changes will be incorporated in new versions of this document. Axway does not warrant that this document is error free. Axway recognizes the rights of the holders of all trademarks used in its publications. The documentation may provide hyperlinks to third-party web sites or access to third-party content. Links and access to these sites are provided for your convenience only. Axway does not control, endorse or guarantee content found in such sites. Axway is not responsible for any content, associated links, resources or services associated with a third-party site. Axway shall not be liable for any loss or damage of any sort associated with your use of third-party content. Contents Accessibility 4 Accessibility features of B2Bi 4 Keyboard -
Typesetting Classical Greek Philology Could Not find Anything Really Suitable for Her
276 TUGboat, Volume 23 (2002), No. 3/4 professor of classical Greek in a nearby classical high Philology school, was complaining that she could not typeset her class tests in Greek, as she could do in Latin. I stated that with LATEX she should not have any The teubner LATEX package: difficulty, but when I started searching on CTAN,I Typesetting classical Greek philology could not find anything really suitable for her. At Claudio Beccari that time I found only the excellent Greek fonts de- signed by Silvio Levy [1] in 1987 but for a variety of Abstract reasons I did not find them satisfactory for the New The teubner package provides support for typeset- Font Selection Scheme that had been introduced in LAT X in 1994. ting classical Greek philological texts with LATEX, E including textual and rhythmic verse. The special Thus, starting from Levy’s fonts, I designed signs and glyphs made available by this package may many other different families, series, and shapes, also be useful for typesetting philological texts with and added new glyphs. This eventually resulted in other alphabets. my CB Greek fonts that now have been available on CTAN for some years. Many Greek users and schol- 1 Introduction ars began to use them, giving me valuable feedback In this paper a relatively large package is described regarding corrections some shapes, and, even more that allows the setting into type of philological texts, important, making them more useful for the com- particularly those written about Greek literature or munity of people who typeset in Greek — both in poetry. -
X E TEX Live
X TE EX Live Jonathan Kew SIL International Horsleys Green High Wycombe Bucks HP14 3XL, England jonathan_kew (at) sil dot org 1 X TE EX in TEX Live in the preamble are sufficient to set the typefaces through- out the document. ese fonts were installed by simply e release of TEX Live 2007 marked a milestone for the dropping the .otf or .ttf files in the computer’s Fonts X TE EX project, as the first major TEX distribution to in- folder; no .tfm, .fd, .sty, .map, or other TEX-related files clude X TE EX (version 0.996) as an integral part. Prior to had to be created or installed. this, X TE EX was a tool that could be added to a TEX setup, Release 0.996 of X T X also provides some enhance- but version and configuration differences meant that it was E E ments over earlier, pre-T X Live versions. In particular, difficult to ensure smooth integration in all cases, and it was E there are new primitives for low-level access to glyph infor- only available for users who specifically chose to seek it out mation (useful during font development and testing); some and install it. (One exception to this is the MacTEX pack- preliminary support for the use of OpenType math fonts age, which has included X TE EX for the past year or so, but (such as the Cambria Math font shipped with MS Office this was just one distribution on one platform.) Integration 2007); and a variety of bug fixes. -
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. -
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. -
Tlaunch: a Launcher for a TEX Live System
TLaunch: a launcher for a TEX Live system Siep Kroonenberg June 29, 2017 This manual is for tlaunch, the TEX Live Launcher, version 0.5.3. Copyright © 2017 Siep Kroonenberg. Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved. This file is offered as-is, without any warranty. Contents 1 The launcher5 1.1 Introduction............................5 1.1.1 Localization........................6 1.2 Modes...............................6 1.2.1 Normal mode.......................6 1.2.2 Initializing.........................6 1.2.3 Forgetting.........................6 1.3 Using scripts............................7 1.4 The ini file.............................7 1.4.1 Location..........................7 1.4.2 Encoding..........................7 1.4.3 Syntax...........................7 1.4.4 The Strings section....................9 1.4.5 Sections for filetype associations (FTAs)........9 1.4.6 Sections for utility scripts................ 10 1.4.7 The built-in functions.................. 10 1.4.8 Menus and buttons.................... 11 1.4.9 The General section.................... 12 1.5 Editor choice............................ 12 1.6 Launcher-based installations................... 13 1.6.1 The tlaunchmode script................. 14 1.6.2 TEX Live Manager..................... 14 2 The launcher at the RUG 15 2.1 Historical.............................. 15 2.2 RES desktops........................... 16 2.3 Components of the rug TEX installation............ 16 2.4 Directory organization...................... 17 2.5 Fixes for add-ons......................... 17 2.5.1 TeXnicCenter....................... 17 2.5.2 TeXstudio......................... 18 2.5.3 SumatraPDF........................ 18 2.5.4 LyX............................. 18 3 CONTENTS 4 2.6 Moving the XeTEX font cache................. -
Oracle® Database Installation Guide
Oracle® Database Installation Guide 18c for Microsoft Windows E83888-01 August 2018 Oracle Database Installation Guide, 18c for Microsoft Windows E83888-01 Copyright © 1996, 2018, Oracle and/or its affiliates. All rights reserved. Primary Authors: Tanaya Bhattacharjee, Sunil Surabhi Contributing Authors: Prakash Jashnani, Mark Bauer, Bharathi Jayathirtha Contributors: Barb Glover, Eric Belden, Sudip Datta, David Friedman, Alex Keh, Peter LaQuerre, Rich Long, Matt McKerley, Sham Rao Pavan, Hanlin Qian, Sujatha Tolstoy, Sergiusz Wolicki, Sue Mavris, Mohammed Shahnawaz Quadri, Vishal Saxena, Krishna Itikarlapall, , Santanu Datta, Christian Shay, Aneesh Khanderwal, Michael Coulter, Robert Achacoso, Malai Stalin, David Price, Ramesh Chakravarthula This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. -
Database Globalization Support Guide
Oracle® Database Database Globalization Support Guide 19c E96349-05 May 2021 Oracle Database Database Globalization Support Guide, 19c E96349-05 Copyright © 2007, 2021, Oracle and/or its affiliates. Primary Author: Rajesh Bhatiya Contributors: Dan Chiba, Winson Chu, Claire Ho, Gary Hua, Simon Law, Geoff Lee, Peter Linsley, Qianrong Ma, Keni Matsuda, Meghna Mehta, Valarie Moore, Cathy Shea, Shige Takeda, Linus Tanaka, Makoto Tozawa, Barry Trute, Ying Wu, Peter Wallack, Chao Wang, Huaqing Wang, Sergiusz Wolicki, Simon Wong, Michael Yau, Jianping Yang, Qin Yu, Tim Yu, Weiran Zhang, Yan Zhu This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. -
The Luacode Package
The luacode package Manuel Pégourié-Gonnard <[email protected]> v1.2a 2012/01/23 Abstract Executing Lua code from within TEX with \directlua can sometimes be tricky: there is no easy way to use the percent character, counting backslashes may be hard, and Lua comments don’t work the way you expect. This package provides the \luaexec command and the luacode(*) environments to help with these problems, as well as helper macros and a debugging mode. Contents 1 Documentation1 1.1 Lua code in LATEX...................................1 1.2 Helper macros......................................3 1.3 Debugging........................................3 2 Implementation3 2.1 Preliminaries......................................4 2.2 Internal code......................................5 2.3 Public macros and environments...........................7 3 Test file 8 1 Documentation 1.1 Lua code in LATEX For an introduction to the most important gotchas of \directlua, see lualatex-doc.pdf. Before presenting the tools in this package, let me insist that the best way to manage a non- trivial piece of Lua code is probably to use an external file and source it from Lua, as explained in the cited document. \luadirect First, the exact syntax of \directlua has changed along version of LuaTEX, so this package provides a \luadirect command which is an exact synonym of \directlua except that it doesn’t have the funny, changing parts of its syntax, and benefits from the debugging facilities described below (1.3).1 The problems with \directlua (or \luadirect) are mainly with TEX special characters. Actually, things are not that bad, since most special characters do work, namely: _, ^, &, $, {, }. Three are a bit tricky but they can be managed with \string: \, # and ~. -
The Latex2ε Package Ccfonts
The LATEX 2" package ccfonts Walter Schmidt∗ (v1.2 { 2020/03/25) Contents 1 Prerequisites 1 2 Using the package 2 2.1 Package options . 3 2.2 Font encoding . 3 3 Known problems 3 4 NFSS classification of the Concrete typefaces 4 5 Implementation 4 5.1 Font setup for text mode . 4 5.2 Options . 5 5.2.1 Standard leading . 5 5.2.2 The option exscale .................. 5 5.2.3 The option slantedGreek ............... 6 5.3 The option boldsans ...................... 6 5.3.1 Processing options . 6 5.4 Font setup for math mode . 6 5.5 Initialization . 7 1 Prerequisites In order to make use of the package ccfonts, the following fonts and .fd files are required: ∗[email protected] 1 • The Concrete text fonts with traditional encoding (CTAN: fonts/ concrete/) • The Concrete text fonts with European encoding (CTAN: fonts/ ecc/) • The mathematical Concrete fonts (CTAN: fonts/concmath/) • The .fd files for the traditional and mathematical Concrete fonts (CTAN: macros/latex/contrib/supported/concmath/) • The .fd files for the European Concrete fonts, which are distributed and installed in conjunction with the ccfonts package On CTAN the fonts are available in METAFONT format. The Concrete typefaces are also provided in Type1 format from Micropress Inc, see <http://www.micropress-inc.com>. 2 Using the package The LATEX macro package ccfonts supports typesetting with the font fam- ily `Concrete'. Loading this package through \usepackage{ccfonts} will effect the following: • The default roman font family is changed to ccr, i.e. Concrete. • The default leading (\baselineskip) for the font sizes 8{12 pt is increased slightly. -
The TEX Live Guide TEX Live 2012
The TEX Live Guide TEX Live 2012 Karl Berry, editor http://tug.org/texlive/ June 2012 Contents 1 Introduction 2 1.1 TEX Live and the TEX Collection...............................2 1.2 Operating system support...................................3 1.3 Basic installation of TEX Live.................................3 1.4 Security considerations.....................................3 1.5 Getting help...........................................3 2 Overview of TEX Live4 2.1 The TEX Collection: TEX Live, proTEXt, MacTEX.....................4 2.2 Top level TEX Live directories.................................4 2.3 Overview of the predefined texmf trees............................5 2.4 Extensions to TEX.......................................6 2.5 Other notable programs in TEX Live.............................6 2.6 Fonts in TEX Live.......................................7 3 Installation 7 3.1 Starting the installer......................................7 3.1.1 Unix...........................................7 3.1.2 MacOSX........................................8 3.1.3 Windows........................................8 3.1.4 Cygwin.........................................9 3.1.5 The text installer....................................9 3.1.6 The expert graphical installer.............................9 3.1.7 The simple wizard installer.............................. 10 3.2 Running the installer...................................... 10 3.2.1 Binary systems menu (Unix only).......................... 10 3.2.2 Selecting what is to be installed...........................