The Design of the Mathspad Editor

Total Page:16

File Type:pdf, Size:1020Kb

The Design of the Mathspad Editor The design of the MathSpad editor Citation for published version (APA): Verhoeven, P. H. F. M. (2000). The design of the MathSpad editor. Technische Universiteit Eindhoven. https://doi.org/10.6100/IR534418 DOI: 10.6100/IR534418 Document status and date: Published: 01/01/2000 Document Version: Publisher’s PDF, also known as Version of Record (includes final page, issue and volume numbers) Please check the document version of this publication: • A submitted manuscript is the version of the article upon submission and before peer-review. There can be important differences between the submitted version and the official published version of record. People interested in the research are advised to contact the author for the final version of the publication, or visit the DOI to the publisher's website. • The final author version and the galley proof are versions of the publication after peer review. • The final published version features the final layout of the paper including the volume, issue and page numbers. Link to publication General rights Copyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights. • Users may download and print one copy of any publication from the public portal for the purpose of private study or research. • You may not further distribute the material or use it for any profit-making activity or commercial gain • You may freely distribute the URL identifying the publication in the public portal. If the publication is distributed under the terms of Article 25fa of the Dutch Copyright Act, indicated by the “Taverne” license above, please follow below link for the End User Agreement: www.tue.nl/taverne Take down policy If you believe that this document breaches copyright please contact us at: [email protected] providing details and we will investigate your claim. Download date: 28. Sep. 2021 The Design of the Matsad Editor CIP-DATA LIBRARY TECHNISCHE UNIVERSITEIT EINDHOVEN Verhoeven, Richard The Design of the Matsad Editor / by Richard Verhoeven { Eindhoven : Eindhoven University of Technology, 2000 Proefontwerp. { ISBN 90{386-0781-4 NUGI 852 Subject headings: text processing ; mathematics / mathematics ; notation / software systems CR Subject Classification (1998): I.7.2, I.7.1, G.4, H.5.2, D.2.11, D.2.13, K.8.1 Print: UniversiteitsDrukkerij, Eindhoven c 2000 by R. Verhoeven, Schijndel, The Netherlands Cover images: c 1977 by Frank Drake (available on Voyager Golden Record). All rights reserved. No part of this publication may be reproduced, stored in a retrieval sys- tem, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without prior permission of the author. Trademarks: Frame, Photoshop and PostScript are registered to Adobe Systems Incorporated; ANSI is registered to American National Standards Institute; OpenDoc is registered to Apple Computer, Inc.; ArborText is registered to Arbor- Text, Inc.; BeOS is registered to Be Incorporated; GIF is a registered service mark of CompuServe Incorporated; Corel is registered to Corel Corporation; Adept is registered to C-TEXT, Inc.; POSIX is a certification mark registered to the Institute of Electrical and Electronics Engineers, Inc.; IBM and PowerPC are registered to International Business Machines Corporation; MatLab is registered to The MathWorks, Inc.; Microsoft, Microsoft Windows en Powerpoint are registered to Microsoft Corporation; Netscape is registered to Netscape Communications Corporation; CORBA is registered to Object Management Group, Inc.; RealAudio is registered to Progressive Networks, Inc.; IRIX is registered to Silicon Graphics, Inc.; Java, Solaris and ToolTalk are registered to Sun Microsystems, Inc.; Scientific Word is registered to TCI Software Research, Inc.; Linux is registered to Linus Torvalds; Unicode is registered to Unicode, Inc.; UNIX is registered to UNIX System Laboratories, Inc.; FreeBSD is registered to Walnut Creek CDROM, Inc.; Mathematica and MathLink are registered to Wolfram Research, Inc.; WordPerfect is registered to WordPerfect Corporation. This research was financially supported by the Eindhoven University of Technology and the Netherlands Organisation for Scientific Research (NWO). The work in this thesis has been carried out under the auspices of the research school IPA (Institute for Programming research and Algorithmics). The Design of the Matsad Editor Proefontwerp ter verkrijging van de graad van doctor aan de Technische Universiteit Eindhoven, op gezag van de Rector Magnificus, prof.dr. M. Rem, voor een commissie aangewezen door het College voor Promoties in het openbaar te verdedigen op woensdag 21 juni 2000 om 16.00 uur door Richard Verhoeven geboren te Veghel Dit proefontwerp is goedgekeurd door de promotoren: prof.dr. R.C. Backhouse en prof.dr. P.M.E. de Bra Acknowledgements There are many people who were supportive while the research described in this thesis took place. They all provided useful information on how to improve the system or were helpful in some sense. My supervisor Roland Backhouse, for providing me with this challenging mas- • ters project, which became the long lasting research project. I want to thank him for his patience, his suggestions and the effort he put in finding research funds. Furthermore, I want to thank his family for testing the system and for the Friday evening meals. The former Ph.D. students Henk Doornbos, Paul Hoogendijk, Laurens de Vries • and Ed Voermans, for sharing the room and having fruitful discussions about the different research topics. Furthermore, I want to thank them for testing the system and making suggestions. My fellow student Olaf Weber, for writing part of the system during our com- • bined masters project. The members and former members of the research group in Eindhoven: Eerke • Boiten, Lex Bijlsma, Joop van den Eijnde, Wim Feijen, Netty van Gasteren, Rik van Geldrop, Kees Hemerik, Jaap van der Woude en Gerard Zwaan. The other members of the Ph.D. committee: Professors Paul de Bra, Andries • Brouwer en Lambert Meertens, for reviewing this thesis and giving detailed and useful comments. Several members of the Computing Science department in Utrecht, especially • Lambert Meertens, for pointing out several interesting features which should be incorporated into the system. The School of Computer Science & IT at the University of Nottingham for • 1 funding the final 4 2 months of this project. The members of the Languages and Programming group in Nottingham: Paul • Blampied, Graham Hutton, Claus Reinke and Natasha Alechina, for the dis- cussions on several research topics. My family, for their support and for the regularly scheduled weekend jobs. • And everyone I forgot to mention. i ii To my parents. Contents Acknowledgements i 1 Introduction 9 1.1 The situation . 10 1.2 An example task . 10 1.3 The goal . 11 1.4 Additional goals . 13 1.5 The outline of this thesis . 13 2 Document preparation 15 2.1 Editing models . 15 2.1.1 WYSIWYG vs. markup languages . 15 2.1.2 Structured vs. unstructured. 21 2.1.3 Modal vs. modeless . 22 2.2 Mathematical documents . 24 2.2.1 WYSIWYG systems . 24 2.2.2 Markup languages . 27 2.3 Mathematical systems and theorem provers . 29 2.4 Software documentation . 31 2.5 Conclusion . 32 3 The functional design 33 3.1 Program versus user in control . 33 3.2 Text editing versus structured editing . 34 3.2.1 Text editing . 34 3.2.2 Structured editing . 35 3.3 Fixed grammar versus flexible grammar . 36 3.3.1 Fixed grammar . 36 iii iv CONTENTS 3.3.2 Flexible grammar . 37 3.4 Clipboard versus multiple selections . 37 3.4.1 The clipboard . 38 3.4.2 Multiple selections . 38 3.5 WYSIWYG versus markup codes . 39 3.5.1 WYSIWYG . 39 3.5.2 Markup codes . 41 3.6 Keyboard handling . 42 4 The technical design 43 4.1 Text structures . 43 4.2 Character encoding . 45 4.3 Mathematical expressions . 45 4.4 Combining text and expressions . 48 4.5 Displaying a document . 50 4.6 Templates . 54 4.6.1 Versions . 55 4.6.2 Stencils . 56 4.6.3 Manipulating templates . 56 4.7 Generating markup output . 59 4.8 The window environment . 61 4.8.1 The window elements . 65 4.9 Box structures . 66 4.10 Control characters . 70 4.10.1 Some examples . 72 4.11 Keyboard handling . 78 4.12 Unicode support . 80 5 Integrating tools 83 5.1 Communication between tools . 83 5.1.1 Pipes . 83 5.1.2 Helper applications . 85 5.1.3 Client { server . 86 5.1.4 Dedicated link . 87 5.1.5 Plug-In libraries . 88 5.1.6 Software bus . 89 5.1.7 Object sharing . 90 5.2 Integrating existing tools . 91 CONTENTS v 5.2.1 The interpreted language . 92 5.2.2 Plug-Ins . 97 5.2.3 Menus . 105 5.2.4 Keyboards . 106 5.2.5 Translations . 107 5.2.6 Scripting . 107 5.2.7 Missing features . 107 5.3 An example connection: PVS . 108 5.3.1 The PVS system . 108 5.3.2 The PVS interface plug-in . 110 5.3.3 The definition file . 113 6 Discussion and conclusions 115 6.1 The current system . 115 6.1.1 The learning curve . 116 6.1.2 The interface . 116 6.1.3 Converting legacy documents . 117 6.1.4 Multiple output formats . 118 6.1.5 Additional layout constructions . 119 6.1.6 LATEX and Unicode . 120 6.2 Application areas . 120 6.2.1 Markup for dummies . 120 6.2.2 Teaching and presentations . 120 6.2.3 Interface for mathematical engines . 121 6.2.4 Literate programming . 122 6.3 Rebuilding the system . 122 6.3.1 New technology .
Recommended publications
  • The Mathdeck Formula Editor
    The MathDeck Formula Editor: Interactive Formula Entry Combining LATEX, Structure Editing, and Search Yancarlos Diaz Gavin Nishizawa Behrooz Mansouri [email protected] [email protected] [email protected] Rochester Institute of Technology Rochester Institute of Technology Rochester Institute of Technology Rochester, NY, USA Rochester, NY, USA Rochester, NY, USA Kenny Davila Richard Zanibbi [email protected] [email protected] University at Buffalo Rochester Institute of Technology Buffalo, NY, USA Rochester, NY, USA Figure 1: MathDeck Search Interface. Formulas are created using the rendered formula, the LATEX string at right, formulas in tabs, and ‘chips’ on the canvas and in the ‘deck’ at bottom. Cards in the deck update for the current formula, and may be expanded to reveal descriptions. Formulas and keywords may be added to the query bar, and sent to a search engine. ABSTRACT CCS CONCEPTS Writing formulas in LATEX can be difficult, especially for complex • Information systems ! Search interfaces; • Mathematics formulas. MathDeck simplifiesA LTEX formula entry by: 1) allowing of computing ! Mathematical software. rendered formulas to be edited directly alongside their associated LATEX strings, 2) helping build formulas from smaller ones, and KEYWORDS 3) providing searchable formula cards with associated names and equation editor, structure editor, LaTeX, Mathematical Information descriptions. Cards are searchable by formula and title. Retrieval (MIR) Permission to make digital or hard copies of part or all of this work for personal or classroom use is granted without fee provided that copies are not made or distributed ACM Reference Format: for profit or commercial advantage and that copies bear this notice and the full citation Yancarlos Diaz, Gavin Nishizawa, Behrooz Mansouri, Kenny Davila, and Richard on the first page.
    [Show full text]
  • 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]
  • Web Page Design with Netscape 7.1 Walter Gajewski, Academic Computing Services Francine Vasilomanolakis, CSULB Dept
    Web Page Design with Netscape 7.1 Walter Gajewski, Academic Computing Services Francine Vasilomanolakis, CSULB Dept. of Education STEP 1: Downloading Netscape 7.1 It is possible to lay out and publish a web page with Netscape Composer, a software application included with the Netscape (version 7.0) Web Browser (free from Netscape). To install Netscape (version 7.1) on your own computer go out to the Netscape web site http://www.netscape.com and click on “Netscape 7.1” located under “Tools” and often under “Dowloads of the Day”. From the “downloads” page you can either install Netscape directly to your personal computer or have them mail you their free CD-ROM. Once Netscape is installed on your computer, you’re ready to create your first web page. STEP 2: Getting a CSULB internet (email) account Before you start authoring your on-line masterpiece you will have to apply for a campus web account. CSULB students can create an email account by going to http://www.csulb.edu/namemaster/ You will now have a user name and password. STEP 3: Creating or Editing a Web Page Note: The index.html file is the Home Page in your web site. When others visit your web site, they will automatically be directed to your index.html file. If this file is missing, all the contents of your directory will be displayed as a list so you must call the file of your home page index.html You have three options available with Netscape Composer: 1. You can create a brand new web page 2.
    [Show full text]
  • Netscape 6.2.3 Software for Solaris Operating Environment
    What’s New in Netscape 6.2 Netscape 6.2 builds on the successful release of Netscape 6.1 and allows you to do more online with power, efficiency and safety. New is this release are: Support for the latest operating systems ¨ BETTER INTEGRATION WITH WINDOWS XP q Netscape 6.2 is now only one click away within the Windows XP Start menu if you choose Netscape as your default browser and mail applications. Also, you can view the number of incoming email messages you have from your Windows XP login screen. ¨ FULL SUPPORT FOR MACINTOSH OS X Other enhancements Netscape 6.2 offers a more seamless experience between Netscape Mail and other applications on the Windows platform. For example, you can now easily send documents from within Microsoft Word, Excel or Power Point without leaving that application. Simply choose File, “Send To” to invoke the Netscape Mail client to send the document. What follows is a more comprehensive list of the enhancements delivered in Netscape 6.1 CONFIDENTIAL UNTIL AUGUST 8, 2001 Netscape 6.1 Highlights PR Contact: Catherine Corre – (650) 937-4046 CONFIDENTIAL UNTIL AUGUST 8, 2001 Netscape Communications Corporation ("Netscape") and its licensors retain all ownership rights to this document (the "Document"). Use of the Document is governed by applicable copyright law. Netscape may revise this Document from time to time without notice. THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IN NO EVENT SHALL NETSCAPE BE LIABLE FOR INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY KIND ARISING FROM ANY ERROR IN THIS DOCUMENT, INCLUDING WITHOUT LIMITATION ANY LOSS OR INTERRUPTION OF BUSINESS, PROFITS, USE OR DATA.
    [Show full text]
  • HTTP Cookie - Wikipedia, the Free Encyclopedia 14/05/2014
    HTTP cookie - Wikipedia, the free encyclopedia 14/05/2014 Create account Log in Article Talk Read Edit View history Search HTTP cookie From Wikipedia, the free encyclopedia Navigation A cookie, also known as an HTTP cookie, web cookie, or browser HTTP Main page cookie, is a small piece of data sent from a website and stored in a Persistence · Compression · HTTPS · Contents user's web browser while the user is browsing that website. Every time Request methods Featured content the user loads the website, the browser sends the cookie back to the OPTIONS · GET · HEAD · POST · PUT · Current events server to notify the website of the user's previous activity.[1] Cookies DELETE · TRACE · CONNECT · PATCH · Random article Donate to Wikipedia were designed to be a reliable mechanism for websites to remember Header fields Wikimedia Shop stateful information (such as items in a shopping cart) or to record the Cookie · ETag · Location · HTTP referer · DNT user's browsing activity (including clicking particular buttons, logging in, · X-Forwarded-For · Interaction or recording which pages were visited by the user as far back as months Status codes or years ago). 301 Moved Permanently · 302 Found · Help 303 See Other · 403 Forbidden · About Wikipedia Although cookies cannot carry viruses, and cannot install malware on 404 Not Found · [2] Community portal the host computer, tracking cookies and especially third-party v · t · e · Recent changes tracking cookies are commonly used as ways to compile long-term Contact page records of individuals' browsing histories—a potential privacy concern that prompted European[3] and U.S.
    [Show full text]
  • March/April 2006
    The newsletter for IPFW computer users Information Technology Services March-April 2006 By Joseph McCormick Manager of Client Support his spring, most Indiana counties T will observe Daylight Savings Time Data Security and Your Workstation (DST) for the first time since 1970. In 2006, DST begins at 2 a.m. on the first Sunday in April (April 2) and ends at 2 option involves a reboot which With recent security incidents at a.m. on the last Sunday in October refreshes your workstation, and the (October 29). other campuses and businesses, it has next time you log in to the network, become imperative that we all take Because of modifications to the Trend OfficeScan antivirus steps to protect data accessed through GroupWise, to accommodate the software installed on your Windows our computers. Precautions should change to Daylight Savings Time, your workstation automatically updates. also be taken to protect data stored on calendar items scheduled between April Keep your workstation up-to- any portable devices such as laptops, 2 at 2:00 a.m. and October 29 at 2:00 date with vendor patches and virus disks or flash drives. Here are a few a.m. are now showing up an hour later protection by activating updates key steps that we can all do quickly to than originally scheduled. Unfortunately, promptly when you are signaled that increase security significantly. this problem was unavoidable as we they are ready. Windows XP/2000 adjusted the system to recognize Daylight users: when you see the “msg”. at the Savings time. bottom of your tool bar that says you Your cooperation is key to The only way to correct this have new updates, please click on the providing overall campus problem is to manually change your button and add your updates.
    [Show full text]
  • Bbedit 13.5 User Manual
    User Manual BBEdit™ Professional Code and Text Editor for the Macintosh Bare Bones Software, Inc. ™ BBEdit 13.5 Product Design Jim Correia, Rich Siegel, Steve Kalkwarf, Patrick Woolsey Product Engineering Jim Correia, Seth Dillingham, Matt Henderson, Jon Hueras, Steve Kalkwarf, Rich Siegel, Steve Sisak Engineers Emeritus Chris Borton, Tom Emerson, Pete Gontier, Jamie McCarthy, John Norstad, Jon Pugh, Mark Romano, Eric Slosser, Rob Vaterlaus Documentation Fritz Anderson, Philip Borenstein, Stephen Chernicoff, John Gruber, Jeff Mattson, Jerry Kindall, Caroline Rose, Allan Rouselle, Rich Siegel, Vicky Wong, Patrick Woolsey Additional Engineering Polaschek Computing Icon Design Bryan Bell Factory Color Schemes Luke Andrews Additional Color Schemes Toothpaste by Cat Noon, and Xcode Dark by Andrew Carter. Used by permission. Additional Icons By icons8. Used under license Additional Artwork By Jonathan Hunt PHP keyword lists Contributed by Ted Stresen-Reuter. Previous versions by Carsten Blüm Published by: Bare Bones Software, Inc. 73 Princeton Street, Suite 206 North Chelmsford, MA 01863 USA (978) 251-0500 main (978) 251-0525 fax https://www.barebones.com/ Sales & customer service: [email protected] Technical support: [email protected] BBEdit and the BBEdit User Manual are copyright ©1992-2020 Bare Bones Software, Inc. All rights reserved. Produced/published in USA. Copyrights, Licenses & Trademarks cmark ©2014 by John MacFarlane. Used under license; part of the CommonMark project LibNcFTP Used under license from and copyright © 1996-2010 Mike Gleason & NcFTP Software Exuberant ctags ©1996-2004 Darren Hiebert (source code here) PCRE2 Library Written by Philip Hazel and Zoltán Herczeg ©1997-2018 University of Cambridge, England Info-ZIP Library ©1990-2009 Info-ZIP.
    [Show full text]
  • Intermediate Perl – Session 7
    1.1.2.8 – Intermediate Perl 1.1.2.8.7 Intermediate Perl – Session 7 · POD – plain old documentation · processing command line parameters · processing configuration files 9/23/2008 1.1.2.8.7 - Intermediate Perl - POD, parameters and configuration 1 1.1.2.8 – Intermediate Perl POD – plain old documentation ·embed documentation in your scripts with POD ·POD is very simple because it stands for Plain Old Documentation · it is meant to be easy to use – and it is! · POD is a simple markup language · write documentation once and export it to multiple formats · man, html, text · POD formatting codes are embedded in your script ·Pod::Usage module displays documentation for the script when the script is executed · how handy is that? 9/23/2008 1.1.2.8.7 - Intermediate Perl - POD, parameters and configuration 2 1.1.2.8 – Intermediate Perl POD structure – sections start and end pod with =pod =pod and =cut =head1 NAME script – take over the world in one line of Perl separate paragraphs by =head1 SYNOPSIS new lines script –mode EVIL|GOOD [-debug] use =head1 and =head2 =head1 DESCRIPTION for headings You can take over the world as an EVIL doer or a GOOD doer. Pick one. =head2 EVIL indent code Evil is more fun. =head2 GOOD =over and =back to =over indent text =item * advantages =item * for bullet lists none =item * disadvantages no fun =back =cut 9/23/2008 1.1.2.8.7 - Intermediate Perl - POD, parameters and configuration 3 1.1.2.8 – Intermediate Perl POD structure – ordinary paragraphs ordinary paragraphs # contents of podexample =pod representing text that =head1 EXAMPLE you'd like wrapped and justified have no This is an ordinary paragraph that will be indented, wrapped and maybe even justified.
    [Show full text]
  • Business Meeting of the Openmath Society 2018
    Business Meeting of the OpenMath Society 2018 Michael Kohlhase (President) Openmath Society http://openmath.org August 13. 2018, Hagenberg Kohlhase: Business Meeting of the OpenMath Society 2018 1 13. 8. 18, Hagenberg OpenMath 2018 Business Meeting (as required by Statutes) 1. Election of Chair of the meeting 2. Election of Secretary and two Minute Checkers (James is in Rio) 3. Annual Report 4. New Members? 5. Adoption of Balance Sheet and discharge of the Executive Committee 6. GDPR/Privacy issues for the Minutes 7. Election of the Executive Committee 8. Adoption of the second revision of the OM2 Standard 9. New OpenMath web site 10. OpenMath in JSON 11. OpenMath3 12. OMCD (management) Issues 13. Any Other Business (please come forward) Kohlhase: Business Meeting of the OpenMath Society 2018 2 13. 8. 18, Hagenberg Annual Report on Activities (2017-2018) I Last Open Business meeting, July 2017 in Edinburgh (internal ones in Spring to keep charter happy) I OM Repositories: Moved all digital assets to http://github.com/OpenMath I OM Web Site: deployed a new web site based on GH Pages (see below) I OM CD Submission Process: based on GitHub now, I OM Standard moved to separate repository, build process renovated, automated by travis. I OM2 Standard: thorough editing, more error fixing (OM binding) I OM3 Standard Effort: not started due to OM2e2 work Kohlhase: Business Meeting of the OpenMath Society 2018 3 13. 8. 18, Hagenberg New Members? I Anybody who has attended 3 OM Workshops or worked on OM for 6 months can become a member (will be generous) I please suggest new members (self-nominations encouraged) I New members proposed by OM Executive Committee I ???? Kohlhase: Business Meeting of the OpenMath Society 2018 4 13.
    [Show full text]
  • INSECURE-Mag-9.Pdf
    Another year is almost over and a plethora of information security problems are behind us. To let 2006 go out in style, we bring you a feature packed issue of (IN)SECURE. As the feature interview for this issue we had the pleasure of talking with Kurt Sauer, the CSO at Skype, one of the most well-known companies in the digital world. We’ll be back next year with many new ideas in the pipeline. Stay tuned for coverage from a few conferences including the RSA Conference in San Francisco and the Black Hat Briefings &Training in Amsterdam. If you’re attending, be sure to drop me an e-mail and we’ll grab a drink. We wish you a safe 2007! Mirko Zorz Chief Editor Visit the magazine website at www.insecuremag.com (IN)SECURE Magazine contacts Feedback and contributions: Mirko Zorz, Chief Editor - [email protected] Marketing: Berislav Kucan, Director of Marketing - [email protected] Distribution (IN)SECURE Magazine can be freely distributed in the form of the original, non modified PDF document. Distribution of modified versions of (IN)SECURE Magazine content is prohibited without the explicit permission from the editor. For reprinting information please send an email to [email protected] or send a fax to 1-866-420-2598. Copyright HNS Consulting Ltd. 2006. www.insecuremag.com New enterprise single sign-on authentication software DigitalPersona announced the latest version of its award-winning enterprise product, DigitalPersona Pro 4.0. The new and improved software delivers a complete, accurate and trusted fingerprint Enterprise Single Sign-On (ESSO) solution with more secure authentication, improved manageability and the broadest support available for the world’s leading biometrically-enabled notebooks including models from Lenovo, HP, Dell, and Toshiba.
    [Show full text]
  • Mandoc: Becoming the Main BSD Manual Toolbox
    mandoc: becoming the main BSD manual toolbox BSDCan 2015, June 13, Ottawa Ingo Schwarze <[email protected]> Cynthia Livingston’sOTTB “Bedifferent” (c) 2013 C. Livingston (with permission) > Ingo Schwarze: mandoc page 2: INTROI BSDCan 2015, June 13, Ottawa Brief history of UNIX documentation • The key point: All documentation in one place and one format. Easy to find, uniform and easy to read and write. Be correct, complete, concise. • 1964: RUNOFF/roffmarkup syntax by Jerome H. Saltzer,MIT. Unobtrusive,diff(1)-friendly,easy to hand-edit, simple tools, high quality output. • 1971: Basic manual structure by Ken Thompson and Dennis Ritchie for the AT&T Version 1 UNIX manuals, Bell Labs. • 1979: man(7) physical markup language for AT&T Version 7 UNIX. • 1989: mdoc(7) semantic markup by Cynthia Livingston for 4.3BSD-Reno. Powerful, self-contained, portable. • 1989: GNU troffbyJames Clarke. • 2001: mdoc(7) rewrite by Werner Lemberg and Ruslan Ermilovfor groff-1.17. • 2008: mandoc(1) started by Kristaps Dzonsons. • 2010: mandoc(1) is the only documentation formatter in the OpenBSD base system. • 2014: mandoc(1) used by default in OpenBSD, FreeBSD, NetBSD, illumos. 16:19:30 What is the mandoc toolbox? → < > Ingo Schwarze: mandoc page 3: INTROIIBSDCan 2015, June 13, Ottawa What is the mandoc toolbox? User perspective:man(1), the manual viewer One comprehensive tool! Normal operation always proceeds in three steps: 1. Find one or more manuals in the file system or using a database by manual name — man(1) — or by search query — apropos(1) =man -k The result of this step can be printed out with man -w.
    [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]