DOCSLIB.ORG

“Creating R Packages” in Writing R Extensions

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
“Creating R Packages” in Writing R Extensions Writing R Extensions Version 4.1.1 (2021-08-10) R Core Team This manual is for R, version 4.1.1 (2021-08-10). Copyright c 1999{2021 R Core Team 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. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into an- other language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the R Core Team. i Table of Contents Acknowledgements ::::::::::::::::::::::::::::::::::::::::::::::::: 1 1 Creating R packages ::::::::::::::::::::::::::::::::::::::::::: 2 1.1 Package structure :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 3 1.1.1 The DESCRIPTION file ::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 4 1.1.2 Licensing ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 8 1.1.3 Package Dependencies::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 9 1.1.3.1 Suggested packages:::::::::::::::::::::::::::::::::::::::::::::::::::::: 12 1.1.4 The INDEX file ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 13 1.1.5 Package subdirectories ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 13 1.1.6 Data in packages::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 16 1.1.7 Non-R scripts in packages :::::::::::::::::::::::::::::::::::::::::::::::::::: 18 1.1.8 Specifying URLs ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 19 1.2 Configure and cleanup :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 19 1.2.1 Using Makevars:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 23 1.2.1.1 OpenMP support ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 26 1.2.1.2 Using pthreads :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 28 1.2.1.3 Compiling in sub-directories ::::::::::::::::::::::::::::::::::::::::::::: 29 1.2.2 Configure example ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 29 1.2.3 Using F9x code :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 31 1.2.4 Using C++ code ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 32 1.3 Checking and building packages ::::::::::::::::::::::::::::::::::::::::::::::::::: 33 1.3.1 Checking packages ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 34 1.3.2 Building package tarballs::::::::::::::::::::::::::::::::::::::::::::::::::::: 37 1.3.3 Building binary packages ::::::::::::::::::::::::::::::::::::::::::::::::::::: 39 1.4 Writing package vignettes ::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 40 1.4.1 Encodings and vignettes ::::::::::::::::::::::::::::::::::::::::::::::::::::: 41 1.4.2 Non-Sweave vignettes :::::::::::::::::::::::::::::::::::::::::::::::::::::::: 42 1.5 Package namespaces :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 43 1.5.1 Specifying imports and exports::::::::::::::::::::::::::::::::::::::::::::::: 43 1.5.2 Registering S3 methods :::::::::::::::::::::::::::::::::::::::::::::::::::::: 44 1.5.3 Load hooks :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 45 1.5.4 useDynLib ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 45 1.5.5 An example:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 48 1.5.6 Namespaces with S4 classes and methods ::::::::::::::::::::::::::::::::::::: 48 1.6 Writing portable packages::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 50 1.6.1 PDF size :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 58 1.6.2 Check timing :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 59 1.6.3 Encoding issues :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 59 1.6.4 Portable C and C++ code ::::::::::::::::::::::::::::::::::::::::::::::::::: 60 1.6.4.1 Common symbols ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 65 1.6.5 Binary distribution :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 66 1.7 Diagnostic messages :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 66 1.8 Internationalization ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 67 1.8.1 C-level messages ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 68 1.8.2 R messages :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 68 1.8.3 Preparing translations ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 68 1.9 CITATION files :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 69 ii 1.10 Package types ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 70 1.10.1 Frontend ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 70 1.11 Services ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 70 2 Writing R documentation files ::::::::::::::::::::::::::::::: 71 2.1 Rd format :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 71 2.1.1 Documenting functions::::::::::::::::::::::::::::::::::::::::::::::::::::::: 72 2.1.2 Documenting data sets ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 76 2.1.3 Documenting S4 classes and methods::::::::::::::::::::::::::::::::::::::::: 77 2.1.4 Documenting packages ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 78 2.2 Sectioning :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 78 2.3 Marking text ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 79 2.4 Lists and tables::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 81 2.5 Cross-references::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 81 2.6 Mathematics:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 82 2.7 Figures ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 82 2.8 Insertions::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 83 2.9 Indices ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 84 2.10 Platform-specific documentation ::::::::::::::::::::::::::::::::::::::::::::::::: 84 2.11 Conditional text ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 84 2.12 Dynamic pages :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 85 2.13 User-defined macros ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 86 2.14 Encoding :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 87 2.15 Processing documentation files ::::::::::::::::::::::::::::::::::::::::::::::::::: 87 2.16 Editing Rd files:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 88 3 Tidying and profiling R code :::::::::::::::::::::::::::::::: 89 3.1 Tidying R code ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 89 3.2 Profiling R code for speed::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 89 3.3 Profiling R code for memory use :::::::::::::::::::::::::::::::::::::::::::::::::: 91 3.3.1 Memory statistics from Rprof :::::::::::::::::::::::::::::::::::::::::::::::: 91 3.3.2 Tracking memory allocations ::::::::::::::::::::::::::::::::::::::::::::::::: 92 3.3.3 Tracing copies of an object ::::::::::::::::::::::::::::::::::::::::::::::::::: 92 3.4 Profiling compiled code ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 92 3.4.1 Linux :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 93 3.4.1.1 sprof :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 93 3.4.1.2 oprofile and operf ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 93 3.4.2 Solaris ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 96 3.4.3 macOS :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 96 4 Debugging ::::::::::::::::::::::::::::::::::::::::::::::::::::: 97 4.1 Browsing ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 97 4.2 Debugging R code :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 98 4.3 Checking memory access ::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 101 4.3.1 Using gctorture ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 102 4.3.2 Using valgrind :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 102 4.3.3 Using the Address Sanitizer ::::::::::::::::::::::::::::::::::::::::::::::::: 104 4.3.3.1 Using the Leak Sanitizer ::::::::::::::::::::::::::::::::::::::::::::::: 105 4.3.4 Using the Undefined Behaviour Sanitizer :::::::::::::::::::::::::::::::::::: 106 4.3.5 Other analyses with `clang' ::::::::::::::::::::::::::::::::::::::::::::::::: 107 4.3.6 Other analyses with `gcc' ::::::::::::::::::::::::::::::::::::::::::::::::::: 107 4.3.7 Using `Dr. Memory' :::::::::::::::::::::::::::::::::::::::::::::::::::::::: 107 4.3.8 Fortran array bounds checking :::::::::::::::::::::::::::::::::::::::::::::: 107 iii 4.4 Debugging compiled code :::::::::::::::::::::::::::::::::::::::::::::::::::::::: 108 4.4.1 Finding entry points in dynamically loaded code :::::::::::::::::::::::::::: 109 4.4.2 Inspecting R objects when debugging ::::::::::::::::::::::::::::::::::::::: 110 4.4.3 Debugging on macOS :::::::::::::::::::::::::::::::::::::::::::::::::::::::
Load more

Recommended publications
  • Computer Science & Information Technology 33
    Computer Science & Information Technology 33 Dhinaharan Nagamalai Sundarapandian Vaidyanathan (Eds) Computer Science & Information Technology Fifth International Conference on Computer Science, Engineering and Applications (CCSEA-2015) Dubai, UAE, January 23 ~ 24 - 2015 AIRCC Volume Editors Dhinaharan Nagamalai, Wireilla Net Solutions PTY LTD, Sydney, Australia E-mail: [email protected] Sundarapandian Vaidyanathan, R & D Centre, Vel Tech University, India E-mail: [email protected] ISSN: 2231 - 5403 ISBN: 978-1-921987-26-7 DOI : 10.5121/csit.2015.50201 - 10.5121/csit.2015.50218 This work is subject to copyright. All rights are reserved, whether whole or part of the material is concerned, specifically the rights of translation, reprinting, re-use of illustrations, recitation, broadcasting, reproduction on microfilms or in any other way, and storage in data banks. Duplication of this publication or parts thereof is permitted only under the provisions of the International Copyright Law and permission for use must always be obtained from Academy & Industry Research Collaboration Center. Violations are liable to prosecution under the International Copyright Law. Typesetting: Camera-ready by author, data conversion by NnN Net Solutions Private Ltd., Chennai, India Preface Fifth International Conference on Computer Science, Engineering and Applications (CCSEA-2015) was held in Dubai, UAE, during January 23 ~ 24, 2015. Third International Conference on Data Mining & Knowledge Management Process (DKMP 2015), International Conference on Artificial Intelligence and Applications (AIFU-2015) and Fourth International Conference on Software Engineering and Applications (SEA-2015) were collocated with the CCSEA-2015. The conferences attracted many local and international delegates, presenting a balanced mixture of intellect from the East and from the West.
    [Show full text]
  • Debian Installation Manual
    Powered by Universal Speech Solutions LLC MRCP Deb Installation Manual Administrator Guide Revision: 70 Created: February 7, 2015 Last updated: March 15, 2021 Author: Arsen Chaloyan Powered by Universal Speech Solutions LLC | Overview 1 Table of Contents 1 Overview ............................................................................................................................................... 3 1.1 Applicable Versions ............................................................................................................ 3 1.2 Supported Distributions ...................................................................................................... 3 1.3 Authentication ..................................................................................................................... 3 2 Installing Deb Packages Using Apt-Get ............................................................................................... 4 2.1 Repository Configuration ................................................................................................... 4 2.2 GnuPG Key ......................................................................................................................... 4 2.3 Repository Update .............................................................................................................. 4 2.4 UniMRCP Client Installation .............................................................................................. 5 2.5 UniMRCP Server Installation ............................................................................................
    [Show full text]
  • The Elinks Manual the Elinks Manual Table of Contents Preface
    The ELinks Manual The ELinks Manual Table of Contents Preface.......................................................................................................................................................ix 1. Getting ELinks up and running...........................................................................................................1 1.1. Building and Installing ELinks...................................................................................................1 1.2. Requirements..............................................................................................................................1 1.3. Recommended Libraries and Programs......................................................................................1 1.4. Further reading............................................................................................................................2 1.5. Tips to obtain a very small static elinks binary...........................................................................2 1.6. ECMAScript support?!...............................................................................................................4 1.6.1. Ok, so how to get the ECMAScript support working?...................................................4 1.6.2. The ECMAScript support is buggy! Shall I blame Mozilla people?..............................6 1.6.3. Now, I would still like NJS or a new JS engine from scratch. .....................................6 1.7. Feature configuration file (features.conf).............................................................................7
    [Show full text]
  • Hydra: a Declarative Approach to Continuous Integration1
    Hydra: A Declarative Approach to Continuous Integration1 Eelco Dolstra, Eelco Visser Department of Software Technology, Faculty of Electrical Engineering, Mathematics and Computer Science (EWI), Delft University of Technology, The Netherlands Abstract There are many tools to support continuous integration: the process of automatically and con- tinuously building a project from a version management repository. However, they do not have good support for variability in the build environment: dependencies such as compilers, libraries or testing tools must typically be installed manually on all machines on which automated builds are performed. In this paper we present Hydra, a continuous build tool based on Nix, a package manager that has a purely functional language for describing package build actions and their dependencies. This allows the build environment for projects to be produced automatically and deterministically, and so significantly reduces the effort to maintain a continuous integration en- vironment. 1. Introduction Hydra is a tool for continuous integration testing and software release that uses a purely func- tional language to describe build jobs and their dependencies. Continuous integration (Fowler and Foemmel 2006) is a simple technique to improve the quality of the software development process. An automated system continuously or periodically checks out the source code of a project, builds it, runs tests, and produces reports for the developers. Thus, various errors that might accidentally be committed into the code base are automatically caught. Such a system allows more in-depth testing than what developers could feasibly do manually: • Portability testing: The software may need to be built and tested on many different plat- forms.
    [Show full text]
  • Solaris 10 End of Life
    Solaris 10 end of life Continue Oracle Solaris 10 has had an amazing OS update, including ground features such as zones (Solaris containers), FSS, Services, Dynamic Tracking (against live production operating systems without impact), and logical domains. These features have been imitated in the market (imitation is the best form of flattery!) like all good things, they have to come to an end. Sun Microsystems was acquired by Oracle and eventually, the largest OS known to the industry, needs to be updated. Oracle has set a retirement date of January 2021. Oracle indicated that Solaris 10 systems would need to raise support costs. Oracle has never provided migratory tools to facilitate migration from Solaris 10 to Solaris 11, so migration to Solaris has been slow. In September 2019, Oracle decided that extended support for Solaris 10 without an additional financial penalty would be delayed until 2024! Well its March 1 is just a reminder that Oracle Solaris 10 is getting the end of life regarding support if you accept extended support from Oracle. Combined with the fact gdpR should take effect on May 25, 2018 you want to make sure that you are either upgraded to Solaris 11.3 or have taken extended support to obtain any patches for security issues. For more information on tanningix releases and support dates of old and new follow this link ×Sestive to abort the Unix Error Operating System originally developed by Sun Microsystems SolarisDeveloperSun Microsystems (acquired by Oracle Corporation in 2009)Written inC, C'OSUnixWorking StateCurrentSource ModelMixedInitial release1992; 28 years ago (1992-06)Last release11.4 / August 28, 2018; 2 years ago (2018-08-28)Marketing targetServer, PlatformsCurrent: SPARC, x86-64 Former: IA-32, PowerPCKernel typeMonolithic with dynamically downloadable modulesDefault user interface GNOME-2-LicenseVariousOfficial websitewww.oracle.com/solaris Solaris is the own operating system Of Unix, originally developed by Sunsystems.
    [Show full text]
  • Salt Documentation Release 2014.7.6
    Salt Documentation Release 2014.7.6 SaltStack, Inc. May 19, 2015 Contents 1 Introduction to Salt 1 1.1 e 30 second summary ........................................... 1 1.2 Simplicity ................................................... 1 1.3 Parallel execution ............................................... 1 1.4 Building on proven technology ....................................... 2 1.5 Python client interface ............................................ 2 1.6 Fast, flexible, scalable ............................................. 2 1.7 Open ...................................................... 2 1.8 Salt Community ................................................ 2 1.9 Mailing List .................................................. 2 1.10 IRC ....................................................... 3 1.11 Follow on Github ............................................... 3 1.12 Blogs ...................................................... 3 1.13 Example Salt States .............................................. 3 1.14 Follow on ohloh ................................................ 3 1.15 Other community links ............................................ 4 1.16 Hack the Source ................................................ 4 2 Installation 5 2.1 ick Install .................................................. 5 2.2 Platform-specific Installation Instructions ................................. 5 2.3 Dependencies ................................................. 26 2.4 Optional Dependencies ............................................ 27 2.5 Upgrading
    [Show full text]
  • Openoffice Spreadsheet Override Auto Capatilization
    Openoffice Spreadsheet Override Auto Capatilization Selfsame Randie thraws her anesthesia so debauchedly that Merwin spiles very raspingly. Mitral Gerrard condones synchronically, he catches his pitchstone very unpreparedly. Is Lon Muhammadan or associate when rematches some requisition tile war? For my monobook skin is a list of As arch Capital will change percentage setting in gorgeous Voice Settings dialog. What rate the 4 basic layout types? Class WriteExcel Documentation for writeexcel 104. OpenOfficeorg 3 Getting Started Calamo. Saving Report Output native Excel XLSX Format. Installed tax product to another precious you should attend Office Manager and. Sep 2015 How to boast Off Automatic Capitalization in Excel 2013 middot Click. ExportMode Defaults to 'xlsx' and uses the tow Office XML standards. HttpwwwopenofficeorglicensesPDLhtml with the additional caveat that anyone. The Source Documents window up the Change Summary window but easily be. Usually if you change this option it affects all components. Excel Export allows exporting ag-Grid data create Excel using Open XML format xlsx or its's own XML format. Lionel Elie Mamane fdo57640 Auto capitalization for letters wrong. Associating a document with somewhat different template 75. The Advantages of Apache OpenOffice Apache OpenOffice Wiki. Note We always prompt response keywords in first capital letters for clarity but the. It is based on code from Apache OpenOffice made available getting the. Citations that sort been inserted with automatic citation updates disabled would be inserted. Getting Started with LibreOffice 60 Dash. Ranges in A1 notation must restore in uppercase like outlook Excel. Open up office vs closed plan office advantages and. OpenDocument applications such as OpenOfficeorg let this change the format of.
    [Show full text]
  • U.S. Government Printing Office Style Manual, 2008
    U.S. Government Printing Offi ce Style Manual An official guide to the form and style of Federal Government printing 2008 PPreliminary-CD.inddreliminary-CD.indd i 33/4/09/4/09 110:18:040:18:04 AAMM Production and Distribution Notes Th is publication was typeset electronically using Helvetica and Minion Pro typefaces. It was printed using vegetable oil-based ink on recycled paper containing 30% post consumer waste. Th e GPO Style Manual will be distributed to libraries in the Federal Depository Library Program. To fi nd a depository library near you, please go to the Federal depository library directory at http://catalog.gpo.gov/fdlpdir/public.jsp. Th e electronic text of this publication is available for public use free of charge at http://www.gpoaccess.gov/stylemanual/index.html. Use of ISBN Prefi x Th is is the offi cial U.S. Government edition of this publication and is herein identifi ed to certify its authenticity. ISBN 978–0–16–081813–4 is for U.S. Government Printing Offi ce offi cial editions only. Th e Superintendent of Documents of the U.S. Government Printing Offi ce requests that any re- printed edition be labeled clearly as a copy of the authentic work, and that a new ISBN be assigned. For sale by the Superintendent of Documents, U.S. Government Printing Office Internet: bookstore.gpo.gov Phone: toll free (866) 512-1800; DC area (202) 512-1800 Fax: (202) 512-2104 Mail: Stop IDCC, Washington, DC 20402-0001 ISBN 978-0-16-081813-4 (CD) II PPreliminary-CD.inddreliminary-CD.indd iiii 33/4/09/4/09 110:18:050:18:05 AAMM THE UNITED STATES GOVERNMENT PRINTING OFFICE STYLE MANUAL IS PUBLISHED UNDER THE DIRECTION AND AUTHORITY OF THE PUBLIC PRINTER OF THE UNITED STATES Robert C.
    [Show full text]
  • View the Index
    INDEX Symbols creating the fleet, 258–264 dropping the fleet, 267 + (addition), 26 reaching bottom of * (asterisk) operator, 147 screen, 276 {} (braces), 92, 105 rebuilding the fleet, 270 / (division), 26 bullets, 246–252 ** (double asterisk) operator, 149 collisions, with aliens, == (equality operator), 72–73 268–269, 291–292 ** (exponent), 26 deleting old, 250 // (floor division), 260 firing, 249 > (greater than), 75 limiting number of, 251 >= (greater than or equal to), 75 making larger, 270 # (hash mark), for comments, 29 settings, 247 != (inequality operator), 74 speeding up, 271 < (less than), 75 classes <= (less than or equal to), 75 Alien, 256–258 % (modulo operator), 116–117, 122 Bullet, 247–248 * (multiplication), 26 Button, 280–281 \n (newline), 22 GameStats, 273 ! (not), 74 Scoreboard, 288–289 += operator, 115 Settings, 231 [] (square brackets), 34 Ship, 233–235 - (subtraction), 26 ending the game, 276 \t (tab), 22 files alien_invasion.py, 229 A bullet.py, 247 addition (+), 26 button.py, 280 aliases, 152 game_stats.py, 273 alice.py, 197–199 scoreboard.py, 288 Alien Invasion project. See also settings.py, 231 Pygame ship.bmp, 233 aliens initializing dynamic checking edges, 266 settings, 286 collisions, with bullets, levels 268–269, 291–292 adding, 285–287 collisions, with ship, 272–275 modifying speed controlling fleet settings, 285 direction, 266 resetting the speed, 287 creating an alien, 256 planning, 228 Alien Invasion project, continued asterisk (*) operator, 147 Play button attributes, 159. See also classes: adding, 280–285
    [Show full text]
  • Renaissance Receptions of Ovid's Tristia Dissertation
    RENAISSANCE RECEPTIONS OF OVID’S TRISTIA DISSERTATION Presented in Partial Fulfillment of the Requirements for the Degree Doctor of Philosophy in the Graduate School of The Ohio State University By Gabriel Fuchs, M.A. Graduate Program in Greek and Latin The Ohio State University 2013 Dissertation Committee: Frank T. Coulson, Advisor Benjamin Acosta-Hughes Tom Hawkins Copyright by Gabriel Fuchs 2013 ABSTRACT This study examines two facets of the reception of Ovid’s Tristia in the 16th century: its commentary tradition and its adaptation by Latin poets. It lays the groundwork for a more comprehensive study of the Renaissance reception of the Tristia by providing a scholarly platform where there was none before (particularly with regard to the unedited, unpublished commentary tradition), and offers literary case studies of poetic postscripts to Ovid’s Tristia in order to explore the wider impact of Ovid’s exilic imaginary in 16th-century Europe. After a brief introduction, the second chapter introduces the three major commentaries on the Tristia printed in the Renaissance: those of Bartolomaeus Merula (published 1499, Venice), Veit Amerbach (1549, Basel), and Hecules Ciofanus (1581, Antwerp) and analyzes their various contexts, styles, and approaches to the text. The third chapter shows the commentators at work, presenting a more focused look at how these commentators apply their differing methods to the same selection of the Tristia, namely Book 2. These two chapters combine to demonstrate how commentary on the Tristia developed over the course of the 16th century: it begins from an encyclopedic approach, becomes focused on rhetoric, and is later aimed at textual criticism, presenting a trajectory that ii becomes increasingly focused and philological.
    [Show full text]
  • Technology User Guide Volume III: DRC INSIGHT
    Technology User Guide Volume III: DRC INSIGHT WISCONSIN Data Recognition Corporation (DRC) 13490 Bass Lake Road Maple Grove, MN 55311 Wisconsin Service Line: 1-800-459-6530 DRC INSIGHT Portal: https://wi.drcedirect.com Email: [email protected] Revision Date: November 12, 2020 COPYRIGHT Copyright © 2020 Data Recognition Corporation The following items in DRC INSIGHT are protected by copyright law: • The User Guide. • All text and titles on the software’s entry and display, including the look and feel of the interaction of the windows, supporting menus, pop-up windows, and layout. DRC INSIGHT Online Learning System and DRC INSIGHT Portal are trademarked by Data Recognition Corporation. Any individuals or corporations who violate these copyrights and trademarks will be prosecuted under both criminal and civil laws, and any resulting products will be required to be withdrawn from the marketplace. The following are trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries: Internet Explorer Microsoft Windows Windows Vista Windows XP Windows 7 Windows 8 Windows 10 The following are trademarks or registered trademarks of Apple Corporation in the United States and/or other countries: Apple Macintosh Mac OS X and macOS iPad iPadOS iOS* *iOS is a trademark or registered trademark of Cisco in the U.S. and other countries and is used under license. Safari The following are trademarks or registered trademarks of Google Corporation in the United States and/or other countries. Chrome Chromebook Google Play The following is a trademark or registered trademark of Mozilla Corporation in the United States and/or other countries.
    [Show full text]
  • Translate's Localization Guide
    Translate’s Localization Guide Release 0.9.0 Translate Jun 26, 2020 Contents 1 Localisation Guide 1 2 Glossary 191 3 Language Information 195 i ii CHAPTER 1 Localisation Guide The general aim of this document is not to replace other well written works but to draw them together. So for instance the section on projects contains information that should help you get started and point you to the documents that are often hard to find. The section of translation should provide a general enough overview of common mistakes and pitfalls. We have found the localisation community very fragmented and hope that through this document we can bring people together and unify information that is out there but in many many different places. The one section that we feel is unique is the guide to developers – they make assumptions about localisation without fully understanding the implications, we complain but honestly there is not one place that can help give a developer and overview of what is needed from them, we hope that the developer section goes a long way to solving that issue. 1.1 Purpose The purpose of this document is to provide one reference for localisers. You will find lots of information on localising and packaging on the web but not a single resource that can guide you. Most of the information is also domain specific ie it addresses KDE, Mozilla, etc. We hope that this is more general. This document also goes beyond the technical aspects of localisation which seems to be the domain of other lo- calisation documents.
    [Show full text]