DOCSLIB.ORG

Support for Acroforms and Links, and for Document Javascript and Open

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Support for Acroforms and Links, and for Document Javascript and Open AcroTEX.Net eforms and insdljs Documentation Support for AcroForms and Links, and for Document JavaScript and Open Page Events D. P. Story © 2013 Version 2.0 http://www.acrotex.net January 19, 2013 [email protected] Table of Contents PDF Links and Forms 4 1 Package Requirement and Options 4 1.1 Package Requirements ............................. 5 1.2 Package Options ................................. 5 1.3 The preview option .............................. 5 1.4 The useui option ................................ 5 1.5 The unicode option of hyperref ....................... 6 2 Form Fields 6 2.1 Button Fields ................................... 7 • Push Buttons ................................. 7 • Check Boxes ................................. 8 • Radio Buttons ................................ 9 2.2 Choice Fields ................................... 10 • List Boxes ................................... 10 • Combo Boxes ................................. 11 2.3 Text Fields .................................... 13 2.4 Signature Fields ................................. 14 3 Link Annotations 17 4 Actions 18 4.1 Trigger Events .................................. 18 4.2 Action Types ................................... 21 5 JavaScript 25 5.1 Support of JavaScript .............................. 25 • The Convenience Command \JS ..................... 25 • Inserting Simple JavaScript ........................ 25 • Inserting Complex or Lengthy JavaScript ................ 26 5.2 Defining JavaScript Strings with \defineJSStr ............. 27 6 The useui option: A User-Friendly Interface 29 6.1 The Appearance Tab .............................. 29 6.2 The Action Tab .................................. 35 6.3 The Signed Tab .................................. 37 Setting the Tab Order 39 7 Setting the Tab Order 39 7.1 Using \setTabOrderByList ......................... 40 7.2 Using \setTabOrderByNumber ........................ 41 Table of Contents (cont.) 3 Document and Page JavaScript 43 8 Package Options 43 9 The insDLJS and insDLJS* Environments 43 9.1 What is Document Level JavaScript? ..................... 44 9.2 The insDLJS Environment .......................... 44 9.3 The insDLJS* Environment .......................... 46 9.4 Escaping ...................................... 47 9.5 Access and Debugging ............................. 48 9.6 JavaScript References .............................. 49 10 Open Action 49 11 The execJS Environment 50 12 The defineJS Environment 52 Appendices 54 A The Annotation Flag F 54 B Annotation Field flags Ff 55 C Supported Key Variables 56 References 63 4 PDF Links and Forms In this document we describe the support for Acrobat form elements in an AcroTEX document. The PDF Reference indicates there are four different categories of fields for a total of seven types of fields. 1. Button Fields (a) Push Button (b) Check Box (c) Radio Button 2. Choice Fields (a) List Box (b) Combo Box 3. Text Fields 4. Signature Fields The AcroTEX Bundle now supports signature fields. Using the command \sigField,an unsigned signature field is created. The field can be signed, either by using Acrobat, or programmatically from a LATEX source, but you need to use aeb_pro and to create the PDF using Acrobat Distiller. The hyperref Package (Rahtz, Oberdiek et al) provides support for the same set of form fields; however, not all features of these fields can be accessed through the hyperref commands. I was determined to write my own set of commands which would be sufficiently comprehensive and extendable to suit all the needs of the AcroTEX Bundle. All the quiz environments have been modified to use this new set of form commands, in this way, there is a uniform treatment of all form fields in the AcroTEX Bundle. The demo files for eForm support are eqform.tex, for those using the Acrobat Distiller to create a PDF document, and eqform_pd.tex, for those who use pdftex or dvipdfm. Online Resources: The following online resources are recommended: • Core JavaScript Reference at Mozilla Developer Center. • JavaScript for Acrobat API Reference at the Acrobat Developer Center. In the nav- igation panel on the left, select JavaScript. • AcroTEX PDF Blog, by D. P. Story. • AeB Blog, by D. P. Story. 1. Package Requirement and Options Prior to Exerquiz version 5.9, eforms was an integral part of Exerquiz. I’ve now sepa- rated the two, making eforms into a stand-alone package that is called by Exerquiz. Package Requirement and Options 5 1.1. Package Requirements The eforms package requires hyperref (a newer version) and insdljs, a package that is part of the AcroTEX Bundle. 1.2. Package Options The eforms package has the usual driver options: dvipsone, dvips, pdftex, dvipdfm, dvipdfmx, xetex The package also works correctly with the luatex executable. Informing the package what driver you are using is important, because each driver has its own code that needs to be used to create form fields. For dvips, you should use \usepackage[dvips]{eforms} The eforms package now does automatic detection of pdftex (including luatex) and xetex. If the web or exerquiz package is used, eforms will use the driver defined in these earlier included packages. A minimal document is \documentclass{article} \usepackage{eforms} % <-- the driver is pdftex or xetex \begin{document} % Content containing form fields, such as... Don’t \pushButton[\CA{Push Me}]{myButton}{}{12bp}, I fall down easily. \end{document} The eforms package brings in the hyperref package and passes it the driver, so there is no need to specify hyperref, usually. If you wish to introduce hyperref yourself with specific options, place it before eforms. If you use the exerquiz package, exerquiz brings in the eforms package and passes it to the driver. 1.3. The preview option Use the preview option if you use a dvi previewer to view your document. When preview is taken, a frame box is drawn around any form field created by eforms, mak- ing the position of the field visible in the previewer. This makes it easy to make any additional adjustments for the position of the field. Turn off this option when you build a PDF file. 1.4. The useui option The useui option includes the xkeyval package, and defines a number of key-value pairs that are used in the optional arguments of the form fields and links. These key- value pairs are more “user-friendly” to use. See Section 6, page 29, for a description of these key-value pairs. 6 1.5. The unicode option of hyperref The eforms package will obey the unicode option of hyperref. Whenever this option is taken in hyperref, for certain keys (namely, \V, \DV, \TU, \CA, \RC, and \AC), standard latex markup may be used to enter the values of these keys, for example, in a text field, you might set \V{J\"{u}rgen}. This key-value pair will produce a field value of “Jürgen” in that in that text field. 2. Form Fields The eForm support for AcroTEX defines six basic (and internal) commands for creating the six types of form elements. These six are used as “building blocks” for defining all buttons, check boxes, radio buttons and text fields used in the AcroTEX quizzes; and for defining six user-commands: \listBox, \comboBox, \pushButton, \checkBox, \radioButton and \textField. These user commands are the topic of the subsequent sections. Each of the above listed field commands has an optional first parameter that is used to modify the appearance of the field, and/or to add actions to the field. This is a “local” capability, i.e., a way of modifying an individual field. There is also a “global” mecha- nism. Each field type has its own \everyFieldTypeName command. For example, all buttons created by \pushButton can be modified using the \everyPushButton com- mand. See the sections on Check Boxes and Radio Buttons for examples and additional comments. The local modifications (the ones inserted into the field by the first parameter) are read after the global modifications, in this way, the local modifications overwrite the global ones. Key-value Pairs. The optional first parameter of each of the form and link commands take two styles of key-values: 1. eforms KVP: This is the key-value system originally developed, each KVP has the form \<key>{<val>}. Through these keys, you can set the appearance of a form or link, and set the actions as well. The \presets key is useful for developing collections of pre-defined key-value pairs for insertion into the optional parameter list. For example, \def\myFavFive{% \BC{1 0 0}\BG{0 1 0}\textColor{1 0 0}\Q{2}\CA{Push Me}} Later, a button can be created using these preset values: \pushButton[\presets{\myFavFive} \A{\JS{app.alert("AcroTeX rocks!")}}]{pb1}{}{11bp} The eforms KVP system is explained throughout the manual, a complete listing of all supported KVPs is found in the Appendices, page 54. Form Fields 7 2. xkeyval KVP: When the useui option is taken, key-value pairs are defined of the form <key>[ = <value>]. The key-value pairs are actually a value of a special eforms key, \ui. The value of \ui consists of a comma-delimited list of xkeyval key-value pairs. This style of key-value pairs also have a presets key, useful for developing col- lections of pre-defined key-value pairs for insertion into the optional parameter list. For example, \def\myFavFive{% bordercolor={1 0 0},bgcolor={0 1 0}, textcolor={1 0 0},align={right},uptxt={Push Me}} Later, a button can be created using these preset values: \pushButton[\ui{presets=\myFavFive, js={app.alert("AcroTeX rocks!")}}]{pb1}{}{11bp} The xkeyval KVP system is described in ‘The useui option: A User-Friendly Inter- face’ on page 29. The first (optional) parameter is read in first, but only after “sanitizing” certain characters that have special meaning to LATEX, these are ˜, #, and &; each of these may appear as part of a URL, or may appear in JavaScript code. Within the first parameter, these three character can be used freely, without escaping them. 2.1. Button Fields Buttons are form elements that the user interacts with using only a mouse. There are three types of buttons: push buttons, check boxes and radio buttons. • Push Buttons The push button is a button field that has no value, it is neither on or off.
Load more

Recommended publications
  • Build It with Nitrogen the Fast-Off-The-Block Erlang Web Framework
    Build it with Nitrogen The fast-off-the-block Erlang web framework Lloyd R. Prentice & Jesse Gumm dedicated to: Laurie, love of my life— Lloyd Jackie, my best half — Jesse and to: Rusty Klophaus and other giants of Open Source— LRP & JG Contents I. Frying Pan to Fire5 1. You want me to build what?7 2. Enter the lion’s den9 2.1. The big picture........................ 10 2.2. Install Nitrogen........................ 11 2.3. Lay of the land........................ 13 II. Projects 19 3. nitroBoard I 21 3.1. Plan of attack......................... 21 3.2. Create a new project..................... 23 3.3. Prototype welcome page................... 27 3.4. Anatomy of a page...................... 30 3.5. Anatomy of a route...................... 33 3.6. Anatomy of a template.................... 34 3.7. Elements............................ 35 3.8. Actions............................. 38 3.9. Triggers and Targets..................... 39 3.10. Enough theory........................ 40 i 3.11. Visitors............................ 44 3.12. Styling............................. 64 3.13. Debugging........................... 66 3.14. What you’ve learned..................... 66 3.15. Think and do......................... 68 4. nitroBoard II 69 4.1. Plan of attack......................... 69 4.2. Associates........................... 70 4.3. I am in/I am out....................... 78 4.4. Styling............................. 81 4.5. What you’ve learned..................... 82 4.6. Think and do......................... 82 5. A Simple Login System 83 5.1. Getting Started........................ 83 5.2. Dependencies......................... 84 5.2.1. Rebar Dependency: erlpass ............. 84 5.3. The index page........................ 85 5.4. Creating an account..................... 87 5.4.1. db_login module................... 89 5.5. The login form........................ 91 5.5.1.
    [Show full text]
  • LYX Frequently Asked Questions with Answers
    LYX Frequently Asked Questions with Answers by the LYX Team∗ January 20, 2008 Abstract This is the list of Frequently Asked Questions for LYX, the Open Source document processor that provides a What-You-See-Is-What-You-Mean environment for producing high quality documents. For further help, you may wish to contact the LYX User Group mailing list at [email protected] after you have read through the docs. Contents 1 Introduction and General Information 3 1.1 What is LYX? ......................... 3 1.2 That's ne, but is it useful? . 3 1.3 Where do I start? . 4 1.4 Does LYX run on my computer? . 5 1.5 How much hard disk space does LYX need? . 5 1.6 Is LYX really Open Source? . 5 2 Internet Resources 5 2.1 Where should I look on the World Wide Web for LYX stu? 5 2.2 Where can I get LYX material by FTP? . 6 2.3 What mailing lists are there? . 6 2.4 Are the mailing lists archived anywhere? . 6 2.5 Okay, wise guy! Where are they archived? . 6 3 Compatibility with other word/document processors 6 3.1 Can I read/write LATEX les? . 6 3.2 Can I read/write Word les? . 7 3.3 Can I read/write HTML les? . 7 4 Obtaining and Compiling LYX 7 4.1 What do I need? . 7 4.2 How do I compile it? . 8 4.3 I hate compiling. Where are precompiled binaries? . 8 ∗If you have comments or error corrections, please send them to the LYX Documentation mailing list, <[email protected]>.
    [Show full text]
  • A Work-Pattern Centric Approach to Building a Personal Knowledge Advantage Machine
    Graduate Theses, Dissertations, and Problem Reports 2012 A Work-Pattern Centric Approach to Building a Personal Knowledge Advantage Machine Daniel Sloan West Virginia University Follow this and additional works at: https://researchrepository.wvu.edu/etd Recommended Citation Sloan, Daniel, "A Work-Pattern Centric Approach to Building a Personal Knowledge Advantage Machine" (2012). Graduate Theses, Dissertations, and Problem Reports. 4919. https://researchrepository.wvu.edu/etd/4919 This Thesis is protected by copyright and/or related rights. It has been brought to you by the The Research Repository @ WVU with permission from the rights-holder(s). You are free to use this Thesis in any way that is permitted by the copyright and related rights legislation that applies to your use. For other uses you must obtain permission from the rights-holder(s) directly, unless additional rights are indicated by a Creative Commons license in the record and/ or on the work itself. This Thesis has been accepted for inclusion in WVU Graduate Theses, Dissertations, and Problem Reports collection by an authorized administrator of The Research Repository @ WVU. For more information, please contact [email protected]. A Work-Pattern Centric Approach to Building a Personal Knowledge Advantage Machine Daniel Sloan Thesis submitted to the College of Engineering and Mineral Resources at West Virginia University in partial fulfillment of the requirements for the degree of Master of Science in Computer Science Yenumula V. Reddy, Ph.D., Chair Bojan Cukic, Ph.D. Cynthia D. Tanner, MS. Lane Department of Computer Science and Electrical Engineering Morgantown, West Virginia 2012 Keywords: Work-patterns, file usage, semantic desktop, machine learning Copyright c 2012 Daniel Sloan Abstract A Work-Pattern Centric Approach to Building a Personal Knowledge Advantage Machine Daniel Sloan A work pattern, also known as a usage pattern, can be broadly defined as the methods by which a user typically utilizes a particular system.
    [Show full text]
  • Metadefender Core V4.12.2
    MetaDefender Core v4.12.2 © 2018 OPSWAT, Inc. All rights reserved. OPSWAT®, MetadefenderTM and the OPSWAT logo are trademarks of OPSWAT, Inc. All other trademarks, trade names, service marks, service names, and images mentioned and/or used herein belong to their respective owners. Table of Contents About This Guide 13 Key Features of Metadefender Core 14 1. Quick Start with Metadefender Core 15 1.1. Installation 15 Operating system invariant initial steps 15 Basic setup 16 1.1.1. Configuration wizard 16 1.2. License Activation 21 1.3. Scan Files with Metadefender Core 21 2. Installing or Upgrading Metadefender Core 22 2.1. Recommended System Requirements 22 System Requirements For Server 22 Browser Requirements for the Metadefender Core Management Console 24 2.2. Installing Metadefender 25 Installation 25 Installation notes 25 2.2.1. Installing Metadefender Core using command line 26 2.2.2. Installing Metadefender Core using the Install Wizard 27 2.3. Upgrading MetaDefender Core 27 Upgrading from MetaDefender Core 3.x 27 Upgrading from MetaDefender Core 4.x 28 2.4. Metadefender Core Licensing 28 2.4.1. Activating Metadefender Licenses 28 2.4.2. Checking Your Metadefender Core License 35 2.5. Performance and Load Estimation 36 What to know before reading the results: Some factors that affect performance 36 How test results are calculated 37 Test Reports 37 Performance Report - Multi-Scanning On Linux 37 Performance Report - Multi-Scanning On Windows 41 2.6. Special installation options 46 Use RAMDISK for the tempdirectory 46 3. Configuring Metadefender Core 50 3.1. Management Console 50 3.2.
    [Show full text]
  • List of Word Processors (Page 1 of 2) Bob Hawes Copied This List From
    List of Word Processors (Page 1 of 2) Bob Hawes copied this list from http://en.wikipedia.org/wiki/List_of_word_processors. He added six additional programs, and relocated the Freeware section so that it directly follows the FOSS section. This way, most of the software on page 1 is free, and most of the software on page 2 is not. Bob then used page 1 as the basis for his April 15, 2011 presentation Free Word Processors. (Note that most of these links go to Wikipedia web pages, but those marked with [WEB] go to non-Wikipedia websites). Free/open source software (FOSS): • AbiWord • Bean • Caligra Words • Document.Editor [WEB] • EZ Word • Feng Office Community Edition • GNU TeXmacs • Groff • JWPce (A Japanese word processor designed for English speakers reading or writing Japanese). • Kword • LibreOffice Writer (A fork of OpenOffice.org) • LyX • NeoOffice [WEB] • Notepad++ (NOT from Microsoft) [WEB] • OpenOffice.org Writer • Ted • TextEdit (Bundled with Mac OS X) • vi and Vim (text editor) Proprietary Software (Freeware): • Atlantis Nova • Baraha (Free Indian Language Software) • IBM Lotus Symphony • Jarte • Kingsoft Office Personal Edition • Madhyam • Qjot • TED Notepad • Softmaker/Textmaker [WEB] • PolyEdit Lite [WEB] • Rough Draft [WEB] Proprietary Software (Commercial): • Apple iWork (Mac) • Apple Pages (Mac) • Applix Word (Linux) • Atlantis Word Processor (Windows) • Altsoft Xml2PDF (Windows) List of Word Processors (Page 2 of 2) • Final Draft (Screenplay/Teleplay word processor) • FrameMaker • Gobe Productive Word Processor • Han/Gul
    [Show full text]
  • Conservative Conversion Between and Texmacs
    Conservative conversion between A L TEX and TEXMACS by Joris van der Hoevena, François Poulainb LIX, CNRS École polytechnique 91128 Palaiseau Cedex France a. Email: [email protected] b. Email: [email protected] April 15, 2014 Abstract Back and forth converters between two document formats are said to be conservative if the following holds: given a source document D, its conversion D0, a locally modied version M 0 of D0 and the back con- version M of M 0, the document M is a locally modied version of D. We will describe mechanisms for the implementation of such converters, A with the L TEX and TEXMACS formats as our guiding example. Keywords: Conservative document conversion, LATEX conversion, TEXMACS, mathematical editing A.M.S. subject classication: 68U15, 68U35, 68N99 1 Introduction The TEXMACS project [7, 10] aims at creating a free scientic oce suite with an integrated structured mathematical text editor [8], tools for graphical drawings and presentations, a spreadsheed, interfaces to various computer algebra sys- tems, and so on. Although TEXMACS aims at a typesetting quality which is at least as good as TEX and LATEX [14, 15], the system is not based on these latter systems. In particular, a new incremental typesetting engine was implemented from scratch, which allows documents to be edited in a wysiwyg and thereby more user friendly manner. This design choice made it also possible or at least easier to use TEXMACS as an interface for external systems, or as an editor for technical drawings. However, unlike existing graphical front-ends for LATEX such as LyX [2] or Scientific Workplace [23], native compatibility with LATEX is not ensured.
    [Show full text]
  • 32 Tugboat, Volume 22 (2001), No. 1/2
    32 TUGboat, Volume 22 (2001), No. 1/2 LYX — An Open Source Document Processor Laura Elizabeth Jackson and Herbert Voß Abstract LYX — the so-called front-end to LATEX, which is itself a front-end to TEX — tries to optimize some- thing that LATEX doesn’t attempt: to make a high quality layout system like (LA)TEX accessible to users who are relatively uninterested in serious typograph- ical questions. LYX is not a word processor, but a document processor, because it takes care of many of the formatting details itself, details that the user need not be bothered with. All LYX features de- scribed here apply to the current official version LYX 1.1.6fix4. The significantly expanded version 1.2 is expected this summer. 1 History Drawing on the principles of the traditional printed word, Donald Knuth1 developed a system that en- abled users to prepare professional technical publi- cations. Knuth called the first version of this system τχ, which has since come to be written TEX and pronounced “tech”. A graphical user interface is in principle not essential for LATEX; however, in today’s “all-things- bright-and-beautiful” world, the absence of a GUI makes LATEX less accessible to the masses. This lack of a GUI was recognized in 1994/95 as the opportunity to create one; it began as a master’s thesis and was first called Lyrik, then LyriX, and finally LYX. From the beginning, the main goal so that the user would be freed from having to delve into the details of (LA)TEX usage.
    [Show full text]
  • LYX Tips and Tricks
    LYX Tips and Tricks Alex Ames February 12, 2015 Contents General overview2 Purpose of LYX.......................................2 Hello, world........................................2 Using LYX on CAE lab computers............................3 Document settings....................................3 Adding graphics and tables...............................3 Further reading......................................4 Math maneuvers5 Shortcuts and special characters.............................6 Making fractions fit....................................6 Math operators......................................7 Vectors...........................................8 Matrices..........................................8 Defining your own operators..............................9 Advanced Fiddling9 What I’ve discovered (and want to record).......................9 1 General overview Purpose of LYX TL;DR: LYX makes it easy to create good-looking technical papers. LYX is designed using the WYSIWYM (what you see is what you mean) paradigm, versus standard word processors like MS Word, which use WYSIWYG (what you see is what you get). This means that when you want to add a section heading, you select ’Section’ in the drop-down menu to the top left, and LYX will take care of the formatting. It also has a very powerful and flexible math typesetting system. LYX takes a bit of adjustment, but it means that you don’t have to remember which font size you’ve been using for headings, or futz around with spacing. It isn’t always the right tool for a particular job; it’s good at making great-looking technical papers and reports, but it’s much harder to fiddle around with graphic placement and fonts like you might want to for a poster. If you’ve ever used LATEX, you should be right at home–LYX is built as a graphical interface on top of LATEX, abstracting away the class declarations and control symbols that clutter up LATEX source files and instead showing you something that’s closer to the final result.
    [Show full text]
  • LYX for Academia
    LYX for academia John R Hudson∗† 1 What is LYX? LyX is a cross-platform program which harnesses the resources of the TEX, XeTeX and LuaTeX typesetting engines and a wide variety of writing tools, including the LibreOffice dictionaries and thesauri, to enable writers, editors, copy-editors and typesetters to create superior docu- ments for web and print media. 2 TEX, LATEX and LYX TEX1, a typesetting engine written in Pascal by Donald Knuth, implements best typesetting practice as set out in the The Chicago manual of style (University of Chicago Press, 1982). Among the limitations of TEX arising from its creation before the growth of the Internet is that it does not support Unicode and offers only a limited range of typefaces. The XeTEX and LuaTEX typesetting engines seek to address these weaknesses and support for them was added in LYX 2. LATEX began as a markup language to help DEC employees to use TEX but has spawned a large number of packages to serve the diverse needs of writers, all of which are available from CTAN. No one needs them all; so selections of the most useful are distributed, notably as MacTeX for Apple computers, TexLive for Linux and MiKTeX for Windows, to which users can add whatever else they need from CTAN. LYX was created by Matthias Ettrich in 1995 as a graphical user interface for the LATEX macros. Originally, it simply hid the complexity of the most common features of LATEX so that the user could produce beautiful documents without knowing anything about LATEX. But it has gradually evolved into a flexible writing tool that can handle an increasing range of LATEX features while enabling those who understand LATEX to tweak the output in a variety of ways.
    [Show full text]
  • Microsoft Exchange 2007 Journaling Guide
    Microsoft Exchange 2007 Journaling Guide Digital Archives Updated on 12/9/2010 Document Information Microsoft Exchange 2007 Journaling Guide Published August, 2008 Iron Mountain Support Information U.S. 1.800.888.2774 [email protected] Copyright © 2008 Iron Mountain Incorporated. All Rights Reserved. Trademarks Iron Mountain and the design of the mountain are registered trademarks of Iron Mountain Incorporated. All other trademarks and registered trademarks are the property of their respective owners. Entities under license agreement: Please consult the Iron Mountain & Affiliates Copyright Notices by Country. Confidentiality CONFIDENTIAL AND PROPRIETARY INFORMATION OF IRON MOUNTAIN. The information set forth herein represents the confidential and proprietary information of Iron Mountain. Such information shall only be used for the express purpose authorized by Iron Mountain and shall not be published, communicated, disclosed or divulged to any person, firm, corporation or legal entity, directly or indirectly, or to any third person without the prior written consent of Iron Mountain. Disclaimer While Iron Mountain has made every effort to ensure the accuracy and completeness of this document, it assumes no responsibility for the consequences to users of any errors that may be contained herein. The information in this document is subject to change without notice and should not be considered a commitment by Iron Mountain. Iron Mountain Incorporated 745 Atlantic Avenue Boston, MA 02111 +1.800.934.0956 www.ironmountain.com/digital
    [Show full text]
  • Application Tips for Word Processors Introduction Formatting a Table Of
    Application Tips for Word Processors [email protected] [ updated: Monday, December 27, 2010 ] Course: BUS 302 Title: The Gateway Experience (3 units) “Man is still the most extraordinary computer of all.” ---John F. Kennedy (1917-1963) Introduction Most contemporary business students use Microsoft Word (MS-Word) for the production of their case reports and other print-based deliverables. The purpose of this document is to help BUS 302 students learn a few commands in MS-Word that are helpful in producing a quality work product. In general, MS-Word works the same way in both the Windows and MacOS environments. Similar commands exist in other word processing applications, such as OpenOffice Writer (Linux/MacOS/Windows), Lyx (Linux/MacOS/Windows), AbiWord (Linux/MacOS/Windows) and Pages (MacOS). Similar commands exist in online word processing applications, such as Google Docs, although the functionality may be limited. If this document is unclear, please contact the instructor. Formatting a Table of Contents Table of Contents typically have some text (usually a section or a component of the case report) on the left-hand side of the page and a page number on the right-hand side of the page. And in between both of those two elements lie “dot leaders.” Dot leaders connect the text on the left-hand side with the page number on the right-hand side to improve clarity and reduce ambiguity for the reader. Appendix..............................................................................................................................5 The command sequence to insert a dot leader is to 1), move the cursor to the first line of the table of contents, 2), select “Format | Tabs,” 2), insert 6 to place a tab stop at the sixth inch (or similar), 3), select “Decimal” alignment, 4), select “…” leader, 5), click “Set”, and 6), click “Close.” Now, type the text on the left-hand side of the page, press the tab key, and type the page number.
    [Show full text]
  • TUGBOAT Volume 31, Number 1 / 2010
    TUGBOAT Volume 31, Number 1 / 2010 General Delivery 3 From the president / Karl Berry 4 Editorial comments / Barbara Beeton TEX at 25; Pi Day; The @ sign as a design icon; Amusements on the Web; Videos of typography talks on the Web; Alphabet soup 6 An argument for learning LATEX: The benefits of typesetting and beyond / Evan Wessler Publishing 9 A computer scientist self-publishing in the humanities / Nicolaas Mars Typography 12 Strategies against widows / Paul Isambert 18 Theses and other beautiful documents with classicthesis / Andr´eMiede 21 Typographers’ Inn / Peter Flynn Fonts 23 Minimal setup for a (cyrillic) TrueType font / Oleg Parashchenko 26 LuaTEX: Microtypography for plain fonts / Hans Hagen 27 Mathematical typefaces in TEX documents / Amit Raj Dhawan Software & Tools 32 LuaTEX: Deeply nested notes / Hans Hagen Graphics 36 Plotting experimental data using pgfplots / Joseph Wright 50 The current state of the PSTricks project / Herbert Voß 59 From Logo to MetaPost / Mateusz Kmiecik A L TEX 64 LATEX news, issue 19 / LATEX Project Team 65 Talbot packages: An overview / Nicola Talbot 68 Tuning LATEX to one’s own needs / Jacek Kmiecik 76 Some misunderstood or unknown LATEX2ε tricks / Luca Merciadri A L TEX 3 79 LATEX3 news, issue 3 / LATEX Project Team 80 Beyond \newcommand with xparse / Joseph Wright 83 Programming key–value in expl3 / Joseph Wright ConTEXt 88 ConTEXt basics for users: Conditional processing / Aditya Mahajan Hints & Tricks 90 Glisterings: Counting; Changing the layout / Peter Wilson 94 The exact placement of superscripts
    [Show full text]