DOCSLIB.ORG

Interface for Integration of Language Checking Tools to Text Editing Software

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Interface for Integration of Language Checking Tools to Text Editing Software Masaryk University Faculty of Informatics Interface for Integration of Language Checking Tools to Text Editing Software Bachelor’s Thesis Jan Tojnar Brno, Spring 2018 Masaryk University Faculty of Informatics Interface for Integration of Language Checking Tools to Text Editing Software Bachelor’s Thesis Jan Tojnar Brno, Spring 2018 This is where a copy of the official signed thesis assignment and a copy ofthe Statement of an Author is located in the printed version of the document. Declaration Hereby I declare that this paper is my original authorial work, which I have worked out on my own. All sources, references, and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Jan Tojnar Advisor: RNDr. Adam Rambousek, Ph.D. i Acknowledgements I would like to thank my advisor RNDr. Adam Rambousek, Ph.D. for his patience, and my parents for their support and proofreading. iii Abstract In this thesis, we propose a library that unifies various text check- ing tools behind a single interface for easier integration of grammar checking into applications. The library is modular and supports dif- ferent providers; a grammar checking provider using LanguageTool and a spell checking provider using Enchant were developed as ex- amples. Additionally, AbiWord text editor was modified to use our library. iv Keywords grammar checking, spell checking, text editor integration, linguistic framework, freedesktop v Contents 1 Introduction 1 2 Overview of existing checkers 3 2.1 Elixir ............................. 3 2.2 Enchant ............................ 3 2.3 Link Grammar ........................ 3 2.4 LanguageTool ......................... 4 2.5 After the Deadline ....................... 4 2.6 Other checkers ......................... 5 3 Design of provider API 7 3.1 Annotations .......................... 7 3.2 Linking annotations to the text ................ 8 3.3 Scope of checked text ..................... 9 3.4 Choosing module system ................... 10 4 Provider implementation 13 4.1 On choice of language ..................... 13 4.2 Anatomy of provider ..................... 13 4.3 Implementing a basic provider ................ 17 4.4 Implementing more providers ................. 20 5 Library design 23 5.1 Library API .......................... 23 5.2 AbiWord integration ..................... 24 6 Conclusion and future work 27 6.1 Conclusion .......................... 27 6.2 Future work .......................... 27 A Source code 29 Bibliography 31 vii 1 Introduction To help prevent users from making mistakes, most of the software that allows composition of longer texts also integrates a spell checker. Spell checkers, however, usually only check whether each word of the text exists in their built-in dictionary, completely ignoring the word’s surroundings. Without accounting for the context of the word, many obvious mistakes are impossible to discover – especially for non-native speakers, non-word errors may actually account only for a small fraction of errors. [8, Table 2, p. 415] For that reason, advanced text processors often offer additional tools which can detect awider variety of problems, including mistakes in grammar, typography or even style. These tools are commonly called grammar checkers. AbiWord … Firefox gedit LanguageTool … Grammarly enchant Figure 1.1: Supporting common checkers in common applications would entail significant effort. There are many different checkers of varying quality1 for different languages: AbiWord uses Link Grammar2; LibreOffice has plug-ins for After the Deadline3, LightProof4 and LanguageTool5; not to for- get plethora of proprietary services like Grammarly6 and Antidote7. What is more, the checkers offer distinct, mutually incompatible in- terfaces. On the other hand, we have applications. Each application 1. See this slightly dated comparison of grammar checkers: http://www. serenity-software.com/pages/comparisons.html 2. https://www.abisource.com/projects/link-grammar/ 3. http://afterthedeadline.com/ 4. https://code.launchpad.net/lightproof 5. https://languagetool.org/ 6. https://grammarly.com/ 7. http://www.antidote.info/en 1 1. Introduction could, in theory, implement a number of most common checking li- braries but that would be far from efficient use of resources, which open-source applications often have a very limited amount. In prac- tice, it would be simply infeasible. This was one of the reasons why Enchant8, a common interface for spell checkers, was designed. Applications can request a dictio- nary for certain language and Enchant will supply them with an ab- straction of one of the checkers it supports. The support for checkers is provided by so-called providers. This allows application creators to target a single checker library and the authors of checker libraries to benefit from integration into many applications. The goal of this thesis is the creation of a library integrating gram- mar checkers in a similar way to how Enchant integrates spell check- ers. To continue with the naming scheme, we will be calling the li- brary Patronus. In the next chapter, we will compare the interfaces of selected open-source grammar checkers. Then we will design an interface for the providers integrating these checkers, and describe authoring of the checkers. Finally, we will design the external library interface and cover AbiWord integration. 8. https://abiword.github.io/enchant/ 2 2 Overview of existing checkers 2.1 Elixir In 2006, Elixir, a new library for integrating grammar checkers was proposed. [15] It aimed to provide a unified interface for grammar checkers similarly to how Enchant did it for spell checkers. It was, however, never released. 2.2 Enchant Enchant is a de facto standard when it comes to text checking libraries; it is widely used by open-source applications, especially in GNOME and KDE desktop environments (via gspell1 and Sonnet2, respectively). Since it so widely supported, extending it to check grammar might sound appealing. Unfortunately, it concerns itself with spell check- ing only, and its API allows checking just one word at a time. It also returns merely the information whether given word exists in the dic- tionary (with the possibility to request suggestions separately). [9] Modifying the checking function to parse blocks of text and return detailed annotations with descriptions of the issues would result in a completely different and incompatible API. 2.3 Link Grammar Link Grammar works on the sentence level, constructing every possi- ble graph of relations between words in a given sentence. [10] A sen- tence is assumed not to be correct when no linkages can be found. It is not a grammar checker per se – it can only determine that a sentence is not a grammatically correct, not provide any information about the exact nature of the issue or suggest fixes. 1. https://wiki.gnome.org/Projects/gspell 2. https://api.kde.org/frameworks/sonnet/html/ 3 2. Overview of existing checkers 2.4 LanguageTool The LanguageTool HTTP API provides two endpoints. /languages for listing the names and codes of supported languages, and /check which facilitates the checking itself. In addition to specifying the primary language, it allows to set user’s native language to check for false friends3 The API returns set of annotations, each containing a position of the problem in text, a short description of the problem, a longer ex- planation and a list of suggested replacements. Additionally, a wider context is provided; for example, the whole sentence would be pro- vided for subject – verb agreement error. Finally, there is a type of the rule that matched the problem, its general description and an identi- fier that can be used for disabling the rule. [3] 2.5 After the Deadline After the Deadline has an API endpoint for checking grammar with spelling, one for checking grammar without spelling, and another for getting statistics of errors in a document. Additionally, there is an end- point providing a HTML document describing an error in detail. The response of checking includes the type and description of the error and a link to a HTML page with more details. Each error also has a list of suggested replacements sorted by relevance. Unlike Lan- guageTool’s API, After the Deadline does not provide the locations of errors. Instead, it lists the matched phrase and the preceding word(s), the annotations are added to text by traversing the text and matching the errors from a queue. [2] This method can unfortunately lead to a misplaced annotation – consider the following text: “You and I are bad. I are bad.” The first instance of “I are” will be marked instead of the intended incorrect second occurrence. 3. Words that look similar in two languages but actually mean different, or even opposite things. 4 2. Overview of existing checkers 2.6 Other checkers Of the remaining checkers that were mentioned, Lightproof is not considered because it is not available as a standalone library, only as an extension for LibreOffice. Antidote does support multiple applica- tions but it is a commercial product for which no trial version is of- fered. Finally, Grammarly is an online service but it does not provide a public API, [5] and while it could be reverse engineered, without stability guarantees, it could stop working any time. 5 3 Design of provider API Since we probably will want to be able to install new providers on de- mand, and recompiling Patronus every time would not be very con- venient, the providers will have to take a form of dynamically loaded modules. Generally, a provider receives a text and returns a list of an- notations. Even here, there are many things to consider: the content of the annotations, the way they are paired with the text, the form mod- ules will take and the form of the communication between Patronus and the modules. 3.1 Annotations As we saw in chapter 2, there are several types of checkers – [11] iden- tifies rule-based checking, that we have seen in LanguageTool, and syntax-based checking used, for example, by link-grammar.
Load more

Recommended publications
  • Enchant 1300
    ENCHANT 1300 Quick Start Guide For more information, please visit harmankardon.com / 1. WHAT’S IN THE BOX Soundbar Remote Control VOL Power Cables* HDMI Cable AUX cable Optical Cable (4ft, 1200mm) (4ft, 1200mm) (4ft, 1200mm) (4ft, 1200mm) Wall-Mount Brackets Product Information & Wall-mounted guide * Power cable quantities vary by region / 2. PLACE YOUR SOUNDBAR 2a. Place the soundbar on the table TV 2B. Wall mount the soundbar Use tape to stick the wall-mounted paper guide on the wall, push a pen tip through the center to mark the wall-mounted bracket location and remove the paper. 1 TV WALLMOUNTED PAPER GUIDE Using the appropriate anchors, screw the wall mount brackets on the pen mark; Fix the screws at the back of soundbar; then hook the soundbar on the wall. 3 2 x3 4 TV / 3. CONNECT YOUR SOUNDBAR 3a. Connect to your TV Option 1 (Best): HDMI TV HDMI OUT HDMI (ARC) (TV ARC) Option 2: OPTICAL TV OPTICAL OUT OPTICAL IN 3b. Connect to other devices HDMI 1 HDMI 2 HDMI 3 HDMI OUT / 4. POWER YOUR SYSTEM 1 2 3 After the power cord is plugged in, the soundbar will take about 30 seconds to start up and then will enter standby mode, ready to use. / 5. CONNECT TO WI-FI 1 2 3 HK ENCHANT 1300 Once the soundbar connects to the internet for the first time, it may detect a software update to improve performance. This update may take a few minutes to complete. / 6. CONTROL YOUR SOUNDBAR 6a. Top Panel Volume Volume Power Down Up Source Display 6b.
    [Show full text]
  • Red Hat Enterprise Linux 6 Developer Guide
    Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Dave Brolley William Cohen Roland Grunberg Aldy Hernandez Karsten Hopp Jakub Jelinek Developer Guide Jeff Johnston Benjamin Kosnik Aleksander Kurtakov Chris Moller Phil Muldoon Andrew Overholt Charley Wang Kent Sebastian Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Edition 0 Author Dave Brolley [email protected] Author William Cohen [email protected] Author Roland Grunberg [email protected] Author Aldy Hernandez [email protected] Author Karsten Hopp [email protected] Author Jakub Jelinek [email protected] Author Jeff Johnston [email protected] Author Benjamin Kosnik [email protected] Author Aleksander Kurtakov [email protected] Author Chris Moller [email protected] Author Phil Muldoon [email protected] Author Andrew Overholt [email protected] Author Charley Wang [email protected] Author Kent Sebastian [email protected] Editor Don Domingo [email protected] Editor Jacquelynn East [email protected] Copyright © 2010 Red Hat, Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
    [Show full text]
  • Simplifying the Scientific Writing and Review Process with Sciflow
    Future Internet 2010, 2, 645-661; doi:10.3390/fi2040645 OPEN ACCESS future internet ISSN 1999-5903 www.mdpi.com/journal/futureinternet Article Simplifying the Scientific Writing and Review Process with SciFlow Frederik Eichler and Wolfgang Reinhardt ? Computer Science Education Group, University of Paderborn, Fuerstenallee 11, 33102 Paderborn, Germany; E-Mail: [email protected] ? Author to whom correspondence should be addressed; E-Mail: [email protected]; Tel.: +49-5251-60-6603; Fax: +49-5251-60-6336. Received: 13 September 2010; in revised form: 30 November 2010 / Accepted: 2 December 2010 / Published: 6 December 2010 Abstract: Scientific writing is an essential part of a student’s and researcher’s everyday life. In this paper we investigate the particularities of scientific writing and explore the features and limitations of existing tools for scientific writing. Deriving from this analysis and an online survey of the scientific writing processes of students and researchers at the University of Paderborn, we identify key principles to simplify scientific writing and reviewing. Finally, we introduce a novel approach to support scientific writing with a tool called SciFlow that builds on these principles and state of the art technologies like cloud computing. Keywords: scientific writing; survey; word processors; cloud computing 1. Introduction Scientific writing is an essential part of a student’s and researcher’s life. Depending on the particular field of study, papers have to be written and written assignments have to be handed in. As the end of studies approaches, most students are asked to prove their ability to work in a scientific manner by writing a thesis.
    [Show full text]
  • Developer Guide
    Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Last Updated: 2017-10-20 Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Robert Krátký Red Hat Customer Content Services [email protected] Don Domingo Red Hat Customer Content Services Jacquelynn East Red Hat Customer Content Services Legal Notice Copyright © 2016 Red Hat, Inc. and others. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent.
    [Show full text]
  • A Zahlensysteme
    A Zahlensysteme Außer dem Dezimalsystem sind das Dual-,dasOktal- und das Hexadezimalsystem gebräuchlich. Ferner spielt das Binär codierte Dezimalsystem (BCD) bei manchen Anwendungen eine Rolle. Bei diesem sind die einzelnen Dezimalstellen für sich dual dargestellt. Die folgende Tabelle enthält die Werte von 0 bis dezimal 255. Be- quemlichkeitshalber sind auch die zugeordneten ASCII-Zeichen aufgeführt. dezimal dual oktal hex BCD ASCII 0 0 0 0 0 nul 11111soh 2102210stx 3113311etx 4 100 4 4 100 eot 5 101 5 5 101 enq 6 110 6 6 110 ack 7 111 7 7 111 bel 8 1000 10 8 1000 bs 9 1001 11 9 1001 ht 10 1010 12 a 1.0 lf 11 101 13 b 1.1 vt 12 1100 14 c 1.10 ff 13 1101 15 d 1.11 cr 14 1110 16 e 1.100 so 15 1111 17 f 1.101 si 16 10000 20 10 1.110 dle 17 10001 21 11 1.111 dc1 18 10010 22 12 1.1000 dc2 19 10011 23 13 1.1001 dc3 20 10100 24 14 10.0 dc4 21 10101 25 15 10.1 nak 22 10110 26 16 10.10 syn 430 A Zahlensysteme 23 10111 27 17 10.11 etb 24 11000 30 18 10.100 can 25 11001 31 19 10.101 em 26 11010 32 1a 10.110 sub 27 11011 33 1b 10.111 esc 28 11100 34 1c 10.1000 fs 29 11101 35 1d 10.1001 gs 30 11110 36 1e 11.0 rs 31 11111 37 1f 11.1 us 32 100000 40 20 11.10 space 33 100001 41 21 11.11 ! 34 100010 42 22 11.100 ” 35 100011 43 23 11.101 # 36 100100 44 24 11.110 $ 37 100101 45 25 11.111 % 38 100110 46 26 11.1000 & 39 100111 47 27 11.1001 ’ 40 101000 50 28 100.0 ( 41 101001 51 29 100.1 ) 42 101010 52 2a 100.10 * 43 101011 53 2b 100.11 + 44 101100 54 2c 100.100 , 45 101101 55 2d 100.101 - 46 101110 56 2e 100.110 .
    [Show full text]
  • Design Decisions for a Structured Front End to LATEX Documents
    Design decisions for a structured front end to LATEX documents Barry MacKichan MacKichan Software, Inc. barry dot mackichan at mackichan dot com 1 Logical design Procedural Scientific WorkPlace and Scientific Word are word processors that have been designed from the start to TeX handle mathematics gracefully. Their design philos- PostScript ophy is descended from Brian Reid’s Scribe,1 which emphasized the separation of content from form and 2 was also an inspiration for LATEX. This logical de- sign philosophy holds that the author of a document should concern him- or herself with the content of the document, and with identifying the role that each bit of text plays, such as a header, a footnote, Structured or a quote. The details of formatting should be ig- Unstructured nored by the author, and handled instead by a pre- defined (or custom) style specification. LaTeX There are several very compelling reasons for the separation of content from form. • The expertise of the author is in the content; PDF the expertise of the publisher is in the presen- tation. Declarative • Worrying and fussing about the presentation is wasted effort when done by the author, since Thus, PostScript is a powerful programming the publisher will impose its own formatting on language, but it was later supplemented by PDF, the paper. which is not a programming language, but instead contains declarations of where individual characters • Applying formatting algorithmically is the eas- are placed. PDF is not structured, but Adobe has iest way to assure consistency of presentation. been adding a structural overlay. LATEX is quite • When a document is re-purposed it can be re- structured, but it still contains visible signs of the formatted automatically for its new purpose.
    [Show full text]
  • Why Be a KDE Project? Martin Klapetek David Edmundson
    Why be a KDE Project? Martin Klapetek David Edmundson What is KDE? KDE is not a desktop, it's a community „Community of technologists, designers, writers and advocates who work to ensure freedom for all people through our software“ --The KDE Manifesto What is a KDE Project? Project needs more than just good code What will you get as a KDE Project? Git repository Git repository plus „scratch repos“ (your personal playground) Creating a scratch repo git push –all kde:scratch/username/reponame Git repository plus web interface (using GitPHP) Git repository plus migration from Gitorious.org Bugzilla (the slightly prettier version) Review Board Integration of git with Bugzilla and Review Board Integration of git with Bugzilla and Review Board Using server-side commit hooks ● BUG: 24578 ● CCBUG: 29456 ● REVIEW: 100345 ● CCMAIL: [email protected] Communication tools Mailing lists Wiki pages Forums Single sign-on to all services Official IRC channels #kde-xxxxx (on Freenode) IRC cloak me@kde/developer/mklapetek [email protected] email address Support from sysadmin team Community support Development support Translations (71 translation teams) Testing support (Active Jenkins and EBN servers, plus Quality Team) Project continuation (when you stop developing it) KDE e.V. support Financial and organizational help Trademark security Project's licence defense via FLA Promo support Stories in official KDE News site (Got the Dot?) Your blog aggregated at Planet KDE Promo through social channels Web hosting under kde.org domain Association with one of the best
    [Show full text]
  • Central Skagit Rural Partial County Library District Regular Board Meeting Agenda April 15, 2021 7:00 P.M
    DocuSign Envelope ID: 533650C8-034C-420C-9465-10DDB23A06F3 Central Skagit Rural Partial County Library District Regular Board Meeting Agenda April 15, 2021 7:00 p.m. Via Zoom Meeting Platform 1. Call to Order 2. Public Comment 3. Approval of Agenda 4. Consent Agenda Items Approval of March 18, 2021 Regular Meeting Minutes Approval of March 2021 Payroll in the amount of $38,975.80 Approval of March 2021 Vouchers in the amount of $76,398.04 Treasury Reports for March 2021 Balance Sheet for March 2021 (if available) Deletion List – 5116 Items 5. Conflict of Interest 5. Communications 6. Director’s Report 7. Unfinished Business A. Library Opening Update B. Art Policy (N or D) 8. New Business A. Meeting Room Policy (N) B. Election of Officers 9. Other Business 10. Adjournment There may be an Executive Session at any time during the meeting or following the regular meeting. DocuSign Envelope ID: 533650C8-034C-420C-9465-10DDB23A06F3 Legend: E = Explore Topic N = Narrow Options D = Decision Information = Informational items and updates on projects Parking Lot = Items tabled for a later discussion Current Parking Lot Items: 1. Grand Opening Trustee Lead 2. New Library Public Use Room Naming Jeanne Williams is inviting you to a scheduled Zoom meeting. Topic: Board Meeting Time: Mar 18, 2021 07:00 PM Pacific Time (US and Canada) Every month on the Third Thu, until Jan 20, 2022, 11 occurrence(s) Mar 18, 2021 07:00 PM Apr 15, 2021 07:00 PM May 20, 2021 07:00 PM Jun 17, 2021 07:00 PM Jul 15, 2021 07:00 PM Aug 19, 2021 07:00 PM Sep 16, 2021 07:00 PM Oct 21, 2021 07:00 PM Nov 18, 2021 07:00 PM Dec 16, 2021 07:00 PM Jan 20, 2022 07:00 PM Please download and import the following iCalendar (.ics) files to your calendar system.
    [Show full text]
  • PIC Licensing Information User Manual
    Oracle® Communications Performance Intelligence Center Licensing Information User Manual Release 10.1 E56971 Revision 3 April 2015 Oracle Communications Performance Intelligence Center Licensing Information User Manual, Release 10.1 Copyright © 2003, 2015 Oracle and/or its affiliates. All rights reserved. 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, the following notices are 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. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • Taft to the Negroes
    " A u 1 I iH ifl M M v ,1 ii U. B. WEATHER BUREAU, September 15. Last 24 Hours Rainfall, .05. :! SUGAR. 96 Degree Test Centrifugals, 3.90c Per Ton, $78.00. Temperature, Max. 82; 71. Weather, cloudy. Mia. 83 Analysis Beets, 9s. 64. Per Ton, $79.80. ESTABLISHED JULY 2, 1856. I 8145. HONOLULU, HAWAII TERRITORY, WEDNESDAY, SEPTEMBER VOL. XLVIIL, NO. 16, 1908. PRICE FIVE CENTS ATM SON HARD AT RKANSAS DEMOCRATS r WORK TO PUT PARTY ROLL UP OF ? V. il N FIGHTING TRI SIXTY FIVE THOUSAND tl 1 f;-- looking After a Good Campaign Committee Portland, Ore., Goes Republican by a Good I 4 and a Republican Senate Gossip on the MarginNew York Democrats t Advertiser Photo. Harmonize Chas. Clark. J. D. Holt. L. L. McCandless. Rialto About Candidates. Hughes Renominated. ft WHAT CAN THEY BE TALKING ABOUT? a "I am interested in seeing the have removed from the active zone of BROKE IIP TIE COLLEGE OF (Associated Press Cablegrams.) party get a campaign com- politics and it was further thought that he would retire from official life at LITTLE ROCK, Arkansas, September 16. The Democrats mittee that will inspire confidence the end of his regime atthe head of have carried aniong all classes of voters in the Re- the police department. The Sheriff an- HAWAII OPEN Arkansas by 65,000 majority. publican party," said Chairman A. L. nounced several months ago that he C Atkinson of the Republican Terri- would not be a candidate for Sheriff. nijoni The following statistics of previous elections are from the World Almanac: About that .
    [Show full text]
  • Open Architecture for Multilingual Parallel Texts M.T
    Open architecture for multilingual parallel texts M.T. Carrasco Benitez Luxembourg, 28 August 2008, version 1 1. Abstract Multilingual parallel texts (abbreviated to parallel texts) are linguistic versions of the same content (“translations”); e.g., the Maastricht Treaty in English and Spanish are parallel texts. This document is about creating an open architecture for the whole Authoring, Translation and Publishing Chain (ATP-chain) for the processing of parallel texts. 2. Summary 2.1. Next steps The next steps should be: • Administrative organisation: create a coordinating organisation and approach the existing organisations that might cooperate; e.g., IETF, LISA, OASIS, W3C. • Public discussion: with an emailing list (or similar) to reach a rough consensus, in particular on aspects such as the required specifications. Organise the necessary meeting(s). • Tools: implement some tools. This might be done simultaneously with the public discussion to better illustrate the approach and support the discussion. 2.2. Best approaches To obtain the best quality, speed and the lowest possible cost (QSC) in the production of parallel texts, one should aim for: • Generating all the linguistic versions ready for publication, from linguistic resources. Probably one of the best approaches. • Seamless ATP-chain implementations. • Authoring: Computer-aided authoring (CAA) tools with a controlled authoring environment; it should deliver source texts prepared for translation. • Translation: Computer-aided translation (CAT) tools to allow translators to focus only in translating and unburden translators from auxiliary tasks such as formatting. These tools should have functionalities such as side-by-side editor and the re-use of previous translations. • Publishing: Computer-aided publishing (CAP) tools to minimise human intervention.
    [Show full text]
  • Classicthesis.Pdf
    andré miede & ivo pletikosic´ ACLASSICTHESISSTYLE [ June 3, 2018 at 15:29 – classicthesis v4.6 ] [ June 3, 2018 at 15:29 – classicthesis v4.6 ] ACLASSICTHESISSTYLE andré miede & ivo pletikosic´ An Homage to The Elements of Typographic Style June 2018 – classicthesis v4.6 [ June 3, 2018 at 15:29 – classicthesis v4.6 ] André Miede & Ivo Pletikosi´c: A Classic Thesis Style, An Homage to The Elements of Typographic Style, c June 2018 [ June 3, 2018 at 15:29 – classicthesis v4.6 ] Ohana means family. Family means nobody gets left behind, or forgotten. — Lilo & Stitch Dedicated to the loving memory of Rudolf Miede. 1939 – 2005 [ June 3, 2018 at 15:29 – classicthesis v4.6 ] [ June 3, 2018 at 15:29 – classicthesis v4.6 ] ABSTRACT Short summary of the contents in English. a great guide by Kent Beck how to write good abstracts can be found here: https://plg.uwaterloo.ca/~migod/research/beckOOPSLA.html ZUSAMMENFASSUNG Kurze Zusammenfassung des Inhaltes in deutscher Sprache. vii [ June 3, 2018 at 15:29 – classicthesis v4.6 ] [ June 3, 2018 at 15:29 – classicthesis v4.6 ] PUBLICATIONS This is just an early This might come in handy for PhD theses: some ideas and figures – and currently ugly – have appeared previously in the following publications: test! [1] Tobias Isenberg, André Miede, and Sheelagh Carpendale. “A Buffer Framework for Supporting Responsive Interaction in Information Visualization Interfaces.” In: Proceedings of the Fourth International Conference on Creating, Connecting, and Collaborating through Computing (C 5 2006). IEEE, 2006, pp. 262–269. isbn: 978- 0-7695-2563-1. [2] Ulrich Lampe, Markus Kieselmann, André Miede, Sebastian Zöller, and Ralf Steinmetz.
    [Show full text]