Lingo Alignment Guide Version 7.0

Total Page:16

File Type:pdf, Size:1020Kb

Lingo Alignment Guide Version 7.0 MadCap Lingo Alignment Guide Version 7.0 THIS USER GUIDE WAS CREATED USING MADCAP FLARE Copyright 2013 MadCap Software. All rights reserved. Information in this document is subject to change without notice. The software described in this document is fur- nished under a license agreement or nondisclosure agreement. The software may be used or copied only in accordance with the terms of those agreements. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or any means electronic or mechanical, including photocopying and recording for any purpose other than the purchaser's personal use without the written permission of MadCap Software. MadCap Software 7777 Fay Avenue La Jolla, California 92037 858-320-0387 www.madcapsoftware.com CONTENTS CHAPTER 1 Introduction 5 CHAPTER 2 Creating Alignment Projects 7 CHAPTER 3 Aligning Files 11 CHAPTER 4 Aligning Segments 17 APPENDIX PDF Guides 27 INDEX 29 Alignment Guide iii MADCAP LINGO iv Alignment Guide CHAPTER 1 Introduction You can leverage translation work previously completed outside of Lingo by using the alignment feature. EXAMPLE Let's say your company has some legacy content that was created in English using MadCap Flare (or even another tool such as Microsoft Word). Subsequently, that content was translated into German using a tool other than Lingo. Now your company has purchased Lingo and wants to use it to translate future updates to that same documentation. The problem is that you do not want to lose all of that pre- vious translation work. The solution is to launch the MadCap Align utility from Lingo and create an align- ment project. From MadCap Align, you use the Start Alignment Wizard to create the new alignment project. In the process of doing this, you select the English version of the original Flare project (or other type of pro- ject/file), as well as the German translation of that project or file. In addition, you make sure the option is selected in the wizard to automatically upload the translated segments to your translation memory. Therefore, when you translate content in future Lingo projects, that previously translated content can be used via the suggestions feature in Lingo. Alignment Guide 5 MADCAP LINGO Following are the steps involved with the alignment feature. 1. Create alignment project From the MadCap Align utility, you can create an alignment project. See "Creating Alignment Projects" on page 7. 2. Align files or segments Although translated segments can automatically be uploaded to a trans- lation memory database during the process of creating an alignment project, there might be some files or segments that require manual alignment. In MadCap Align the original and translated files and seg- ments are shown side by side, allowing you to make sure everything is correct. If any pair of files or seg- ments do not match precisely, you can manually align them. See "Aligning Files" on page 11 and "Aligning Segments" on page 17. 3. Upload segments to translation memory Once the file/segment alignment process is completed, you can manually upload the translated files or segments to your translation memory database. To do this, you can double-click any of the aligned files in the File Map window pane. Then, in the Alignment Tool, you can select specific segments and click in the local toolbar, or you can click to upload all of the segments in the file. 6 Alignment Guide CHAPTER 2 Creating Alignment Projects You can create alignment projects after launching MadCap Align. An alignment project lets you leverage trans- lation work previously completed outside of Lingo, uploading translated segments to your translation memory database. HOW TO CREATE AN ALIGNMENT PROJECT 1. Do one of the following, depending on the part of the user interface you are using. Ribbon Select the Tools ribbon. In the Launch section select MadCap Align. You can use the Options dialog to switch between ribbons and the classic menu/toolbar layout. For more information see the online Help. Keep in mind that the smaller the application window becomes, the more the options in a rib- bon shrink. Therefore, you might only see a small icon instead of text, or you might see only a section name displayed with a down arrow to access the options in it. You can hover over small icons to see tooltips that describe them. You can also enlarge the application window or click one of the section drop-downs in the ribbon to locate a hidden feature. Menu Select Tools>MadCap Align. 2. In MadCap Align do one of the following, depending on the part of the user interface you are using. Ribbon Select File>New Align Project. Menu Select File>New Align Project. Standard toolbar Click . To open the Standard toolbar from the menu view, you can select View>Tool- bars>Standard. The Start Alignment Wizard opens. Alignment Guide 7 MADCAP LINGO 3. Next to the Original Version field, click . 4. In the dialog that opens, navigate to the original project or file (in the original language) that you have already translated, and double-click the appropriate file. The various types of files that you can open to translate include: Flare projects and files; Mimic projects and movies; MadCap documents (e.g., for use in Contributor); Madcap Capture image files; MadCap packages/bundles (ZIP files); text files; HTM, HTML, and XML files; DITA files; Microsoft Word files; Adobe FrameMaker files; Adobe InDesign files; Microsoft PowerPoint files; and XLIFF files. Note: Individual image files can be selected and translated in their own Lingo pro- jects. However, if the images are included in Flare projects, you can translate the cal- lout text for those images at the same time that you are translating the other parts of the Flare project. 5. Next to the Translated Version field, click . 6. In the dialog that opens, navigate to the previously translated version of that same project or file and double-click it. 7. (Optional) If you want to automatically upload previously translated segments to translation memory, click the check box. Your translation memory database should be displayed in the field below. If it is not, you can click in the field and select it. Note: If you select this check box, any uploaded segments that are already matched 100% will not be displayed in the File Map window pane in MadCap Align. Only files with segments that require alignment will appear in that window pane. Note: If you do not use this feature, you will need to manually upload the translated segments to translation memory after the alignment project is created. Note: In order to use this feature, you must first install a translation memory data- base. 8 Alignment Guide CHAPTER 2 Creating Alignment Projects 8. Click in the next field and select a translation memory database. 9. Click Next. 10. In the Source language section, select the original language that is used in the project you are trans- lating. In the Target language section, select the language that you want to use for the translation. 11. Click Next. 12. In the Project Name field, type an appropriate name for your project. 13. By default, a path to the Documents\My Aligned Projects folder on your hard drive is entered in the Pro- ject Folder field. (This folder is created when you install the program.) All subfolders and files related to the aligned project will be placed in this folder as you work on the project. Note: In some operating systems, the folder is called "My Documents" instead of "Documents." 14. Click Finish. Alignment Guide 9 MADCAP LINGO 10 Alignment Guide CHAPTER 3 Aligning Files When you create an alignment project, the original and translated files are matched and aligned by name. Although it might not be a common occurrence, there are a variety of reasons that a file from the original project might not be aligned with the same file in the translated project. The important thing is that you identify such mis- alignments and then correct them. You can do this by using the File Map window pane in MadCap Align. The File Map window pane groups files found in both projects by file type. For each type, you can match the files together when necessary. There are a few operations for aligning files; you can shift the selected cells up and down, or swap two selected cells. After the files are aligned, you can manually upload them to your translation memory database. Alignment Guide 11 MADCAP LINGO EXAMPLE After creating an alignment project, let's say you open the File Map window pane and notice that all of the topic file rows are aligned with identical names, except for two—"Welcome.htm" and "Intro- duction.htm." To fix this you can select one of the misaligned cells (say, the "Introduction.htm" file in the first column) and click the appropriate "swap" button. 12 Alignment Guide CHAPTER 3 Aligning Files The files become aligned, like this: You can then upload the aligned files to the translation memory database. Alignment Guide 13 MADCAP LINGO You also might encounter situations where one file should actually align with two or more files. EXAMPLE Let's say that during the original translation, the topic "A1.htm" was translated into Spanish and the res- ulting topic file name was also "A1.htm." Later, however, maybe someone split the topic in the original version into two separate files—"A1.htm" and "A2.htm." In the File Map window pane of an alignment project, the results might look like this (notice that about half of the segments are in the source A1.htm file and the other half are in the source A2.htm file): You can align and upload the files in order to store all of the translated data in translation memory.
Recommended publications
  • Tinn-R Team Has a New Member Working on the Source Code: Wel- Come Huashan Chen
    Editus eBook Series Editus eBooks is a series of electronic books aimed at students and re- searchers of arts and sciences in general. Tinn-R Editor (2010 1. ed. Rmetrics) Tinn-R Editor - GUI forR Language and Environment (2014 2. ed. Editus) José Cláudio Faria Philippe Grosjean Enio Galinkin Jelihovschi Ricardo Pietrobon Philipe Silva Farias Universidade Estadual de Santa Cruz GOVERNO DO ESTADO DA BAHIA JAQUES WAGNER - GOVERNADOR SECRETARIA DE EDUCAÇÃO OSVALDO BARRETO FILHO - SECRETÁRIO UNIVERSIDADE ESTADUAL DE SANTA CRUZ ADÉLIA MARIA CARVALHO DE MELO PINHEIRO - REITORA EVANDRO SENA FREIRE - VICE-REITOR DIRETORA DA EDITUS RITA VIRGINIA ALVES SANTOS ARGOLLO Conselho Editorial: Rita Virginia Alves Santos Argollo – Presidente Andréa de Azevedo Morégula André Luiz Rosa Ribeiro Adriana dos Santos Reis Lemos Dorival de Freitas Evandro Sena Freire Francisco Mendes Costa José Montival Alencar Junior Lurdes Bertol Rocha Maria Laura de Oliveira Gomes Marileide dos Santos de Oliveira Raimunda Alves Moreira de Assis Roseanne Montargil Rocha Silvia Maria Santos Carvalho Copyright©2015 by JOSÉ CLÁUDIO FARIA PHILIPPE GROSJEAN ENIO GALINKIN JELIHOVSCHI RICARDO PIETROBON PHILIPE SILVA FARIAS Direitos desta edição reservados à EDITUS - EDITORA DA UESC A reprodução não autorizada desta publicação, por qualquer meio, seja total ou parcial, constitui violação da Lei nº 9.610/98. Depósito legal na Biblioteca Nacional, conforme Lei nº 10.994, de 14 de dezembro de 2004. CAPA Carolina Sartório Faria REVISÃO Amek Traduções Dados Internacionais de Catalogação na Publicação (CIP) T591 Tinn-R Editor – GUI for R Language and Environment / José Cláudio Faria [et al.]. – 2. ed. – Ilhéus, BA : Editus, 2015. xvii, 279 p. ; pdf Texto em inglês.
    [Show full text]
  • System Tools Reference Manual for Filenet Image Services
    IBM FileNet Image Services Version 4.2 System Tools Reference Manual SC19-3326-00 IBM FileNet Image Services Version 4.2 System Tools Reference Manual SC19-3326-00 Note Before using this information and the product it supports, read the information in “Notices” on page 1439. This edition applies to version 4.2 of IBM FileNet Image Services (product number 5724-R95) and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright IBM Corporation 1984, 2019. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About this manual 17 Manual Organization 18 Document revision history 18 What to Read First 19 Related Documents 19 Accessing IBM FileNet Documentation 20 IBM FileNet Education 20 Feedback 20 Documentation feedback 20 Product consumability feedback 21 Introduction 22 Tools Overview 22 Subsection Descriptions 35 Description 35 Use 35 Syntax 35 Flags and Options 35 Commands 35 Examples or Sample Output 36 Checklist 36 Procedure 36 May 2011 FileNet Image Services System Tools Reference Manual, Version 4.2 5 Contents Related Topics 36 Running Image Services Tools Remotely 37 How an Image Services Server can hang 37 Best Practices 37 Why an intermediate server works 38 Cross Reference 39 Backup Preparation and Analysis 39 Batches 39 Cache 40 Configuration 41 Core Files 41 Databases 42 Data Dictionary 43 Document Committal 43 Document Deletion 43 Document Services 44 Document Retrieval 44 Enterprise Backup/Restore (EBR)
    [Show full text]
  • A User's Guide to the Lout Document Formatting System
    A User’s Guide to the Lout Document Formatting System Jeffrey H. Kingston Version 3.40 June 2013 Copyright 1991, 2013 Jeffrey H. Kingston, School of Information Technologies, The University of Sydney 2006, Australia. ISBN 0 86758 9515. Preface This User’s Guide brings together in one document everything needed for the day-to-day use of Version 3 of the Lout document formatting system. There are three other documents describing Lout: the Expert’s Guide [5], which you need if you want to add new features to Lout; a journal paper on the design and implementation of Lout [3]; and a set of overhead transparencies [4]that cover much the same ground as this Guide. These documents are all distributed with the software. Lout is distributed free of charge under the GNU Public License. The primary source is ftp://ftp.it.usyd.edu.au/jeff/lout containing a gzipped tar file of the current version, and various other things including a PostScript version of this guide. The distribution contains source code, libraries,documentation, license, and installation instructions. A mailing list has been set up for discussion of all topics related to Lout. To subscribe (or unsubscribe), visit http://lists.nongnu.org/mailman/listinfo/lout-users After subscribing, to post an item send email to [email protected]; it will be forwarded to all subscribers via email. There is also a web site at http://savannah.nongnu.org/projects/lout. Lout began in 1984 as a research project into the design of a high-level language for document formatting.
    [Show full text]
  • GNU A2ps, Version 4.14 General Purpose Postscript Generating Utility Edition 4.14, 2 May 2007
    GNU a2ps, version 4.14 General Purpose PostScript Generating Utility Edition 4.14, 2 May 2007 Akim Demaille Miguel Santana Copyright c 1988-1993 Miguel Santana Copyright c 1995-2000 Akim Demaille, Miguel Santana Copyright c 2007 Akim Demaille, Miguel Santana and Masayuki Hatta Permission is granted to make and distribute verbatim copies of this manual provided the copy- right notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the condi- tions 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 another language, under the above conditions for modified versions, except that this permission notice maybe stated in a translation approved by the Free Software Foundation. i Short Contents 1 Introduction :::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 2 User's Guide :::::::::::::::::::::::::::::::::::::::::::::::::::::::: 4 3 Invoking a2ps ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 9 4 Configuration Files :::::::::::::::::::::::::::::::::::::::::::::::::: 27 5 Library Files ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 35 6 Encodings ::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 39 7 Pretty Printing ::::::::::::::::::::::::::::::::::::::::::::::::::::: 44 8 PostScript ::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 71 9 Contributions
    [Show full text]
  • Entity Linking to Wikipedia Grounding Entity Mentions in Natural Language Text Using Thematic Context Distance and Collective Search
    Entity Linking to Wikipedia Grounding entity mentions in natural language text using thematic context distance and collective search Dissertation zur Erlangung des Doktorgrades (Dr. rer. nat.) der Mathematisch-Naturwissenschaftlichen Fakultät der Rheinischen Friedrich-Wilhelms-Universität Bonn vorgelegt von Anja Pilz aus Chemnitz Bonn, 2015 Angefertigt mit Genehmigung der Mathematisch-Naturwissenschaftlichen Fakultät der Rheinischen Friedrich-Wilhelms-Universität Bonn 1. Gutachter: Prof. Dr. Stefan Wrobel 2. Gutachter: Prof. Dr. Kristian Kersting Tag der Promotion: 21.09.2015 Erscheinungsjahr: 2016 Anja Pilz Fraunhofer Institut für Intelligente Analyse und Informationssysteme IAIS und Rheinische Friedrich-Wilhelms-Universität Bonn, Institut für Informatik III Acknowledgements First and foremost, I would like to thank Prof. Dr. Stefan Wrobel and Prof. Dr. Kristian Kersting for giving me the opportunity to work on my thesis in cooper- ation with the Computer Science Department at the University of Bonn and the Knowledge Discovery Department at Fraunhofer IAIS. I would like to express my sincere gratitude to all people who have helped, inspired and accompanied me during my PhD studies. This thesis would not have been possible without the support from many other people and each of them contributed directly or indirectly to this thesis. I am very grateful for the chance to pursuit my PhD studies in the Text Mining Group at Fraunhofer IAIS and have benefited greatly from the presence of all the supportive and involved people who made this an excellent working environment. These include all the former and current members of the Text Mining, STREAM and CAML groups, especially Melanie Knapp, Gerhard Paaß, Hannes Korte, Siehyun Strobel, Andre Bergholz, Florian Schulz, Kristian Kersting and Thomas Gärtner who all offered ideas, advise and support in many different ways.
    [Show full text]
  • Pipenightdreams Osgcal-Doc Mumudvb Mpg123-Alsa Tbb
    pipenightdreams osgcal-doc mumudvb mpg123-alsa tbb-examples libgammu4-dbg gcc-4.1-doc snort-rules-default davical cutmp3 libevolution5.0-cil aspell-am python-gobject-doc openoffice.org-l10n-mn libc6-xen xserver-xorg trophy-data t38modem pioneers-console libnb-platform10-java libgtkglext1-ruby libboost-wave1.39-dev drgenius bfbtester libchromexvmcpro1 isdnutils-xtools ubuntuone-client openoffice.org2-math openoffice.org-l10n-lt lsb-cxx-ia32 kdeartwork-emoticons-kde4 wmpuzzle trafshow python-plplot lx-gdb link-monitor-applet libscm-dev liblog-agent-logger-perl libccrtp-doc libclass-throwable-perl kde-i18n-csb jack-jconv hamradio-menus coinor-libvol-doc msx-emulator bitbake nabi language-pack-gnome-zh libpaperg popularity-contest xracer-tools xfont-nexus opendrim-lmp-baseserver libvorbisfile-ruby liblinebreak-doc libgfcui-2.0-0c2a-dbg libblacs-mpi-dev dict-freedict-spa-eng blender-ogrexml aspell-da x11-apps openoffice.org-l10n-lv openoffice.org-l10n-nl pnmtopng libodbcinstq1 libhsqldb-java-doc libmono-addins-gui0.2-cil sg3-utils linux-backports-modules-alsa-2.6.31-19-generic yorick-yeti-gsl python-pymssql plasma-widget-cpuload mcpp gpsim-lcd cl-csv libhtml-clean-perl asterisk-dbg apt-dater-dbg libgnome-mag1-dev language-pack-gnome-yo python-crypto svn-autoreleasedeb sugar-terminal-activity mii-diag maria-doc libplexus-component-api-java-doc libhugs-hgl-bundled libchipcard-libgwenhywfar47-plugins libghc6-random-dev freefem3d ezmlm cakephp-scripts aspell-ar ara-byte not+sparc openoffice.org-l10n-nn linux-backports-modules-karmic-generic-pae
    [Show full text]
  • Baskerville the Annals of the UK TEX Users’ Group Guest Editor: Kaveh Bazargan Vol
    Baskerville The Annals of the UK TEX Users’ Group Guest Editor: Kaveh Bazargan Vol. 7 No. 1 ISSN 1354–5930 September 1997 Articles may be submitted via electronic mail to [email protected], or on MSDOS-compatible discs, to Sebastian Rahtz, Elsevier Science Ltd, The Boulevard, Langford Lane, Kidlington, Oxford OX5 1GB, to whom any correspondence concerning Baskerville should also be addressed. This reprint of Baskerville is set in Times Roman, with Computer Modern Typewriter for literal text; the source is archived on CTAN in usergrps/uktug. Back issues from the previous 12 months may be ordered from UKTUG for £2 each; earlier issues are archived on CTAN in usergrps/uktug. Please send UKTUG subscriptions, and book or software orders, to Peter Abbott, 1 Eymore Close, Selly Oak, Birmingham B29 4LB. Fax/telephone: 0121 476 2159. Email enquiries about UKTUG to uktug- [email protected]. Contents 1 Editorial . 2 I The Future of Document Formatting (Working Paper) :::::::::::::::::::::::::::::::::::::::::::::::::: 3 1 Abstract . 3 2 Introduction . 3 3 Requirements . 4 3.1 Editability . 4 3.2 Extensibility . 4 3.3 Generality . 6 3.4 Optimality . 6 4 Conclusion . 8 5 Acknowledgements . 8 II Standard DTDs and scientific publishing:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 10 1 Abstract . 10 2 Introduction . 10 3 Scientific publishing . 10 4 Encoding of mathematical formulas . 11 4.1 Characteristics of mathematical notation . 12 4.2 Who performs the markup of math? . 13 4.3 Feasibility of S-type notation . 14 4.4 Some problems with existing languages . 14 5 Re-using mathematical formulas . 15 6 Related problems . 15 7 Conclusions . 16 III A LATEX Tour, part 3: mfnfss, psnfss and babel::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 18 1 Introduction .
    [Show full text]
  • Lingo Getting Started Guide Version 7.0
    MadCap Lingo Getting Started Guide Version 7.0 THIS USER GUIDE WAS CREATED USING MADCAP FLARE Copyright 2013 MadCap Software. All rights reserved. Information in this document is subject to change without notice. The software described in this document is fur- nished under a license agreement or nondisclosure agreement. The software may be used or copied only in accordance with the terms of those agreements. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or any means electronic or mechanical, including photocopying and recording for any purpose other than the purchaser's personal use without the written permission of MadCap Software. MadCap Software 7777 Fay Avenue La Jolla, California 92037 858-320-0387 www.madcapsoftware.com CONTENTS CHAPTER 1 Introduction 5 File Types You Can Translate 6 Major Benefits 7 Basic Steps for Translators—If Using Lingo 8 Basic Steps for Authors—If Using a Third-Party TMS 9 Additional Help 11 CHAPTER 2 Starting a Lingo Project 13 Creating New Projects 14 Updating Projects 20 CHAPTER 3 Viewing Files Requiring Translation 21 CHAPTER 4 Translating Files 23 CHAPTER 5 Exporting Translated Projects 29 CHAPTER 6 Other Lingo Features 31 Translation Memory 32 Termbases 32 Dictionaries 32 APPENDIX PDF Guides 33 Getting Started Guide iii MADCAP LINGO iv Getting Started Guide CHAPTER 1 Introduction Welcome to MadCap Lingo—the first native XML, fully integrated computer-aided translation (CAT) tool and translation management solution (TMS). Lingo is a desktop solution that you can use to translate the following. This chapter discusses the following.
    [Show full text]
  • (12) United States Patent (10) Patent No.: US 7,798,417 B2 Snyder Et Al
    US007798417B2 (12) United States Patent (10) Patent No.: US 7,798,417 B2 Snyder et al. (45) Date of Patent: Sep. 21, 2010 (54) METHOD FOR DATA INTERCHANGE application No. 1 1/325,713, filed on Jan.5, 2006, now Pat. No. 7,118,040. (76) Inventors: David M. Snyder, 1110 Wenig Rd. NE., (60) Provisional application No. 60/294,375, filed on May Cedar Rapids, IA (US) 524.02: Bruce D. 30, 2001, provisional application No. 60/232,825, Melick, 4335 Cloverdale Rd. NE., Cedar filed on Sep. 15, 2000, provisional application No. Rapids, IA (US) 52411; Leslie D. 60/213.843, filed on Jun. 23, 2000, provisional appli Baych, 4315 Woodfield La. NE., Cedar cation No. 60/174.220, filed on Jan. 3, 2000, provi Rapids, IA (US) 524.02: Paul R. sional application No. 60/572,140, filed on May 18, Staman, 1600 G St., Amana, IA (US) 2004, provisional application No. 60/727,605, filed on 52203; Nicholas J. Peters, 3229 260' Oct. 18, 2005, provisional application No. 60/813,899, St., Williamsburg, IA (US) 52261; filed on Jun. 15, 2006, provisional application No. Gregory P. Probst, 531 Woodridge Ave., 60/834,523, filed on Aug. 1, 2006. Iowa City, IA (US) 5224.5 (51) Int. C. (*) Notice: Subject to any disclaimer, the term of this G06K 9/06 (2006.01) patent is extended or adjusted under 35 G06K 9/00 (2006.01) U.S.C. 154(b) by 390 days. (52) U.S. Cl. ....................................... 235/494; 235/487 (58) Field of Classification Search ................. 235/380, (21) Appl.
    [Show full text]
  • Manchester Forum in Linguistics 2017
    Manchester Forum in Linguistics A conference for early career researchers in linguistics University of Manchester 28-29 April 2017 www.mfilconf.co.uk [email protected] The 2017 Manchester Forum in Linguistics is supported by the University of Manchester’s Department of Linguistics and English Language, artsmethods@manchester and the Linguistics Association of Great Britain. i Contents General information ......................................... 1 Programme ............................................. 2 Plenary speakers ........................................... 4 Origin stories: Evaluating theories for the origins of Canadian raising, Amanda Cardoso . 5 Using quantitative syntactic data to assign dates of composition to Old English texts, Aaron Ecay ............................................ 6 Social media and the new frontiers of forensic authorship profiling, Andrea Nini . 7 Language structure from social practice, Péter Rácz ...................... 8 Talks ................................................. 9 Velar nasal plus in the north of (ing)land, George Bailey ................... 10 Expletives in Icelandic: A diachronic study, Hannah Booth . 11 Minimal effort and the relative order of double topics in Mandarin Chinese, Sherry Yong Chen 12 Implementing reproducibility in phonetic research: A computational workflow, Stefano Coretta 13 The syntax-pragmatics interface: Unifying contrastiveness: Evidence from North-Eastern Italian dialects (NEIDs)?, Simone De Cia ........................ 14 How many or how much? – Counting and measuring
    [Show full text]
  • Tennessee Judicial Nominating Commission Application for Nomination to Judicial Office Rev
    Tennessee Judicial Nominating Commission Application for Nomination to Judicial Office Rev. 26 November 2012 Name: Dale Conder Jr Office Address: 209 E. Main Street (including county) Jackson, Madison County, Tennessee 38301 Office Phone: 731-426-8130 Facsimile: 737-410-1326 Email Address: [email protected] Home Address: (including county) Home Phone: INTRODUCTION Tennessee Code Annotated section 17-4-101 charges the Judicial Nominating Commission with assisting the Governor and the People of Tennessee in finding and appointing the best qualified candidates for judicial offices in this State. Please consider the Commission’s responsibility in answering the questions in this application questionnaire. For example, when a question asks you to “describe” certain things, please provide a description that contains relevant information about the subject of the question, and, especially, that contains detailed information that demonstrates that you are qualified for the judicial office you seek. In order to properly evaluate your application, the Commission needs information about the range of your experience, the depth and breadth of your legal knowledge, and your personal traits such as integrity, fairness, and work habits. This document is available in word processing format from the Administrative Office of the Courts (telephone 800.448.7970 or 615.741.2687; website http://www.tncourts.gov). The Commission requests that applicants obtain the word processing form and respond directly on the form. Please respond in the box provided below each question. (The box will expand as you type in the word processing document.) Please read the separate instruction sheet prior to completing this document. Please submit the completed form to the Administrative Office of the Courts in paper format (with ink signature) and electronic format (either as an image or a word processing file and with electronic or scanned signature).
    [Show full text]
  • Ultrascale Architecture Configuration User Guide (UG570)
    UltraScale Architecture Configuration User Guide UG570 (v1.15) September 9, 2021 Revision History The following table shows the revision history for this document. Date Version Revision 09/09/2021 1.15 Added coverage of Artix UltraScale+ AU10P, AU15P, AU20P, and AU25P devices: Added these devices to Table 1-4 and Table 1-5. 06/25/2021 1.14 Added reference to UltraScale+ Devices Integrated Block for PCI Express Product Guide (PG213). Updated KU19P device data in Table 1-4. Added KU19P, VU23P, and VU57P production IDCODE revisions to Table 1-5. Clarified USR_ACCESSE2 Advanced Uses in Chapter 7. Clarified Loading Encrypted Bitstreams in Chapter 8. Added register bits [31:26] to Table 9-20 and URAM register code to Table 9-22. Added Accessing Configuration Registers through the SelectMAP Interface in Chapter 10. Clarified Persist Option in Chapter 10. 07/28/2020 1.13 Added VU57P device to Table 1-3, added KU19P, VU23P, and VU57P devices to Table 1-4 and Table 1-5. Updated Table 8-4 descriptions for R_DIS_USER, R_DIS_SEC, and R_DIS_RSA. Updated Table 9-15 description for configuration word 30026001. Added information for encrypted bitstreams using an obfuscated key with the JTAG, SelectMAP, or ICAP interfaces. 03/31/2020 1.12 Added VU19P production IDCODE revision to Table 1-5. Updated value for GLUTMASK_B in Table 9-23. 09/30/2019 1.11 Added coverage of Virtex UltraScale+ VU19P, VU47P, and VU49P devices. Updated production IDCODE revisions for Virtex UltraScale+ FPGAs in Table 1-5. Updated descriptions for INIT_B and DONE in Table 1-9. Updated Figure 9-4 and Figure 9-13.
    [Show full text]