DOCSLIB.ORG

\", 22 \', 22 \(, 31, 32 \), 31, 32 \-, 26 \., 22 \=, 22 \[, 32 \], 32 \ˆ, 21, 22 \`, 22

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
\ i i i ‘beginlatex’ --- 2018/12/4 --- 23:30 --- page 289 --- #325 i Index Index See Table 2 on page xxx for the meanings of the typographic formatting used here and in the text. \", 22 \ae, 22 \', 22 \affiliation, 42 \(, 31, 32 afm2tfm, 234 \), 31, 32 textbf, 17 \-, 26 Apple Mac \., 22 editor, 189, 194 /p, 236 installation, 189 \=, 22 apt, 190 \@, 162, 164 apt-get, xxvi \[, 32 Aquamacs, 222 \], 32 \arabic, 170 \ˆ, 21, 22 ArcInfo, 96 \`, 22 textbf, 13 \ , 21, 22 array, 85 \arraybackslash, 85 10pt, 37 \arraystretch, 87 11pt, 37 article, 11, 35 12pt, 11, 37 \author, xxx, 42–44, 108, 162 AutoCAD, 95 a4paper, 36, 38 avant, 143 \AA, 22 \aa, 22 b, 100 AbiWord, 175, 177, 178 \b, 22 abstract, 44, 45 babel, 20, 30, 50, 120 \abstractname, 45 textbf, 9 abstracts, 44 textbf, 254 accents, 19 BaKoMa TEX, xxix Acrobat Reader, 185, 194, 222, 258 \baselinestretch, 133 acronym, 126 bbding, 73, 171 \addbibresource, 120 beer, 123 \addcontentsline, 52 lite, 123 \addtocontents, 53 American, 123 \AE, 22 Rogue £ Formatting Information ¢ 289 ¡ i i i i i i i ‘beginlatex’ --- 2018/12/4 --- 23:30 --- page 290 --- #326 i FORMATTING INFORMATION Chocolate Stout, 124 \centering, 29, 85, 87, 148 \begin, 20, 40, 41, 45, 74, 82, cep, 93 163, 180 chancery, 143 \bfseries, 12, 149 textbf, 247 biber, ix, 5, 19, 62, 112–114, 120– \chapter, 47, 48 122, 125 chapter, 170 biber, 247, 249 characters BIBINPUTS, 116 accented, 19 biblatex, 5, 112, 113 ASCII, 267 biblatex, ix, 5, 19, 112–114, 116– math, 31 121 special, 15, 31 biblatex-apa, 114 charmap, 21 biblatex-cheatsheet, 114 charter, 144 biblatex-chicago, 114 ChemDraw, 95 textbf, 112 Chocolate Stout, 124 bibliographies, 111 Chocolate Stout, 124 \bibliography, 121 \cite, 112, 117–119, 121, 122, \bibliographystyle, 117, 125 121 \citep, 118, 121, 122 bibtex, 5, 62, 112–114, 118, 122, \citet, 118, 121 125 textbf, 56 bibtex, 247, 249 Classes \bigskip, 132 article, 11, 35 textbf, 2, 229 book, 35 book, 35 letter, 35 book, 47 memoir, xxx bookman, 143 report, 34 boxes, 99 thesis, 34 bp (big points), 25 classes, 56 \clearpage, xxx \c, 22 \cline, 84 \c , 22 cm (centimeters), 25 Calibre, 2 \color, 58, 155 \caption, 81, 89, 111 \colorbox, 102, 156 cat, 237 colortbl, 86 cc (Ciceros), 25 colour, 155 cd, 66, 250 columns, 127 center, 11, 12, 29, 87, 88, 148 \columnsep, 127 £ ¢ 290 ¡ Formatting Information i i i i i i i ‘beginlatex’ --- 2018/12/4 --- 23:30 --- page 291 --- #327 i INDEX Command, 218 \bigskip, 132 Commands \c, 22 \", 22 \c , 22 \', 22 \caption, 81, 89, 111 \(, 31, 32 cat, 237 \), 31, 32 cd, 66, 250 \-, 26 \centering, 29, 85, 87, 148 \., 22 \chapter, 47, 48 \=, 22 \cite, 112, 117–119, 121, \@, 162, 164 122, 125 \[, 32 \citep, 118, 121, 122 \], 32 \citet, 118, 121 \ˆ, 21, 22 \clearpage, xxx \`, 22 \cline, 84 \ , 21, 22 \color, 58, 155 \AA, 22 \colorbox, 102, 156 \aa, 22 \d, 22 \abstractname, 45 \date, 42, 44, 162, 252, 253 \addbibresource, 120 \datesubmitted, 42 \addcontentsline, 52 \DeclareFontFamily, \addtocontents, 53 239 \AE, 22 \DeclareFontShape, 239, \ae, 22 240 \affiliation, 42 \def, 167 \arabic, 170 \definecolor, 155, 156 \arraybackslash, 85 del, 248 \arraystretch, 87 \documentclass, 20, 34, \author, xxx, 42–44, 108, 38, 45, 57, 152, 180 162 \doublespacing, 133 \b, 22 dvips, 97, 193 \begin, 20, 40, 41, 45, 74, 82, \EF, 162 163, 180 \emph, 154, 180 \bfseries, 12, 149 \end, 11, 39, 40, 45, 105, 180 biber, 247, 249 \enspace, 134 \bibliography, 121 \EUR, 17, 85 \bibliographystyle, exit, 139, 246 117, 121 \fancyhead, 136 bibtex, 247, 249 \fbox, 90, 101, 102, 156 £ Formatting Information ¢ 291 ¡ i i i i i i i ‘beginlatex’ --- 2018/12/4 --- 23:30 --- page 292 --- #328 i FORMATTING INFORMATION fc-cache, 139 \L, 22 fc-list, 230 \l, 22 \fcolorbox, 102, 156 \label, 77, 81, 89, 110–112 \flushleft, 148 \labelitemi, 171 \flushright, 148 \labelitemiv, 172 \fnsymbol, 108 \LARGE, 152 \fontencoding, 147 \Large, 12, 152 \fontfamily, 143, 148 \large, 152 \fontsize, 152 \LaTeX, 179 \footcite, 118, 119 latex, 8, 62, 193, 247, 249 \footnote, xxx, 103, 107, latexmk, 247, 249 108 \leftmark, 137 \footnotesize, 152 \linebreak, 166 \foreign, 154, 165 \listoffigures, 52 \foreignlanguage, 30 \listoftables, 52 \gloss, 125 ls, 227 \glossary, 125 \lstinline, 104, 106 \gls, 125 \makeatletter, 163 \graphicspath, 96, 97 \makeatother, 163 grep, 230 \makeglossary, 124 \H, 22 \makeindex, 123 .h1, 3 makeindex, 124, 247, 249 :h1, 3 \maketitle, 42–45, 52, 58, @Heading, 3 147, 162, 163, 253 \hline, 84 man, 124 \hrule, 164 \marginal, 109 \hspace, 134 \markboth, 135 \Huge, 152 \markright, 135 \huge, 152 \mbox, 27, 166 \hyphenation, 26, 27 \medskip, 132 \i, 22 mkdir, 217, 218, 231, 236 \includegraphics, 90– \multicolumn, 86, 88 93, 96, 97, 103 mv, 248 \index, 123–125, 168 \newcommand, 162, 167 \input, 125 \newcounter, 78 \item, 72 \newfontface, 146 \itshape, 149 \newfontfamily, 146 kpsewhich, 158 \newgeometry, 132 £ ¢ 292 ¡ Formatting Information i i i i i i i ‘beginlatex’ --- 2018/12/4 --- 23:30 --- page 293 --- #329 i INDEX \newglossaryentry, 125 \renewcommand, 45, 49, 87, \noindent, 98 133, 163, 170 \normalsize, 152 \RequirePackage, 152 \O, 22 \rightmark, 137 \o, 22 rm, 248 \OE, 22 \rmdefault, 238 \oe, 22 \rule, 84 \onehalfspacing, 133 \S, 110 \ovalbox, 102 \scriptsize, 152 \P, 110 \scshape, 149 \pageref, 111 \section, 3, 47, 51, 170 \pagestyle, 135, 136 \selectfont, 147, 148, 150 \par, 88, 132, 148, 152, 164 \selectlanguage, 30 \paragraph, 47, 77 \sentinel, 167, 168 \setcounter, 49 \parbox, 99–101 \setlength, 49–51, 101 \parencite, 117–119 \setmainfont, 139 \part, 47 \setmonofont, 139 \part*, 49 \setsansfont, 139 pdflatex, 247, 249 \sfdefault, 238 \person, 167, 168 \sffamily, 12, 149, 164 \printbibliography, \shadowbox, 102, 168 120 \singlespacing, 133 \printglossaries, 125 \slshape, 149 \printindex, 124 \small, 98, 152 \product, 154, 165 \smallskip, 132 \protect, 108 \ss, 22 \ProvidesPackage, 238 \subparagraph, 47, 77 \qquad, 134 \subparagraph*, 49 \quad, 25, 134 \subsection, 47 \RaggedLeft, 29 \subsubsection, 47 \raggedleft, 29, 85 sudo, 138, 191 \RaggedRight, 29 \t, 22 \raggedright, 29, 85, 100 \tableofcontents, 14, \raisebox, 171 51, 52, 250 \ref, 77, 110–112 \tablesfont, 146 \reindex, 167, 168 texconfig, 191 ren, 248 texdoc, 59 £ Formatting Information ¢ 293 ¡ i i i i i i i ‘beginlatex’ --- 2018/12/4 --- 23:30 --- page 294 --- #330 i FORMATTING INFORMATION \text, 124 \usepackage, 38, 57, 58, 91, \textbf, 150 97, 106, 155, 159, 180, \textbrokenbar, 31 231, 239, 255 \textbullet, 73 \v, 22 \textcite, 117–119 \verb, 102–106, 108 \textcolor, 155, 156 \VerbatimFootnotes, \textdegree, 32 108 \texteuro, 17 \vspace, 132, 134 \textit, 150, 154 \vspace*, 133 \textlangle, 31 xelatex, xxvii, 247, 249 \textrangle, 31 commands, 13 \textsc, 150 textbf, 16 \textsf, 150 commercial distributions, xxix \textsl, 150 textbf, 150 \textsterling, 17 Computer, 157, 206, 219 \textsuperscript, 18 concrete, 142 \texttrademark, 166 configure, 65 \texttt, 150 ConT Xt, xvii \thechapter, 170 E textbf, 11 \theenumi, 78 Counters \theenumii, 78 chapter, 170 \theenumiii, 78 enumi, 78 \theenumiv, 78 enumii, 78 \theexample, 78 \TheSbox, 168 enumiii, 78 \thesection, 170 enumiv, 78 \thinspace, 18, 19, 134 example, 78 \thispagestyle, 135 footnote, 108 \tiny, 152 secnumdepth, 11, 49 \title, 42, 44, 108, 162 section, xxx, 170, 171 \titlecite, 118 tocdepth, 49, 52 \tmproduct, 165 courier, 143 \ttdefault, 238 Crayola, xv, 155 \ttfamily, 149 cross-references, 109 \u, 22 csquotes, 120 \uline, 151 textbf, 13, 14 \upshape, 149 Cygwin, 67 \url, 104, 106, 108, 180 cypriot, 146 £ ¢ 294 ¡ Formatting Information i i i i i i i ‘beginlatex’ --- 2018/12/4 --- 23:30 --- page 295 --- #331 i INDEX \d, 22 dvips, 93, 97, 257, 259 dash, 28 dvips, 97, 193 long, 28 dvipsnames, 155 short, 28 dviview, 255 datatool, 81, 86 DynaTag, 176 \date, 42, 44, 162, 252, 253 \datesubmitted, 42 \EF, 162 DCF, 3 eiad, 142 dcolumn, 86 El Capitan, 194 dd (Didot points), 25 em (relative measure), 25 \DeclareFontFamily, 239 Emacs, xxvi, 10, 18, 86, 87, 222– \DeclareFontShape, 239, 240 224, 251, 259 \def, 167 emacs, 138 \definecolor, 155, 156 \emph, 154, 180 del, 248 empty, 135 textbf, 248 \end, 11, 39, 40, 45, 105, 180 description, 74, 75 endnote, 108 description*, 75 \enspace, 134 detex, 186 enumerate, 73 textbf, 49 enumerate*, 75, 76 dimensions, 23 enumi, 78 DOCTEX, 61 enumii, 78 DocBook, 177 enumiii, 78 DocBook 5, xxxi enumitem, 65, 74, 75, 77, 132 document, xxiii, 11, 12, 20, 41, enumiv, 78 42 environment, 72 document class, 34 environment, xxx \documentclass, 20, 34, 38, textbf, 11, 40 45, 57, 152, 180 Environments Dolphin, 62, 157, 217 abstract, 44, 45 double-spacing, 133 center, 11, 12, 29, 87, 88, \doublespacing, 133 148 draft, 37 description, 74, 75 Draw, 92, 96 description*, 75 duerer, 142 document, xxiii, 11, 12, 20, dvialw, 260 41, 42 dvieps, 260 enumerate, 73 dvihp, 260 enumerate*, 75, 76 £ Formatting Information ¢ 295 ¡ i i i i i i i ‘beginlatex’ --- 2018/12/4 --- 23:30 --- page 296 --- #332 i FORMATTING INFORMATION environment, xxx \EUR, 17, 85 equation, 32 Euro, 17 figure, 89, 148 EuroMath, 175 figure*, 127 Evince, 191, 222 flushleft, 88, 164 ex (relative measure), 25 flushright, 88 example, 78 inparaenum, 76 exit, 139, 246 itemize, 11, 73 extarticle, 38 itemize*, 75 extbook, 38 lrbox, 101 extreport, 38 minipage, 100–102, 108, extsizes, 38 168 multicols, 127 fancybox, 101, 102, 168 picture, 90, 91 fancyhdr, 135, 136 quotation, xxx, 98, 148 \fancyhead, 136 raggedleft, 29 fancyvrb, 105, 108 raggedright, 29 \fbox, 90, 101, 102, 156 Sbox, 101, 102, 168 \fboxrule, 101, 156 spacing, 133 \fboxsep, 101, 156 table, 81, 82,
Load more

Recommended publications
  • Behavior Based Software Theft Detection, CCS 2009
    Behavior Based Software Theft Detection 1Xinran Wang, 1Yoon-Chan Jhi, 1,2Sencun Zhu, and 2Peng Liu 1Department of Computer Science and Engineering 2College of Information Sciences and Technology Pennsylvania State University, University Park, PA 16802 {xinrwang, szhu, jhi}@cse.psu.edu, [email protected] ABSTRACT (e.g., in SourceForge.net there were over 230,000 registered Along with the burst of open source projects, software open source projects as of Feb.2009), software theft has be- theft (or plagiarism) has become a very serious threat to the come a very serious concern to honest software companies healthiness of software industry. Software birthmark, which and open source communities. As one example, in 2005 it represents the unique characteristics of a program, can be was determined in a federal court trial that IBM should pay used for software theft detection. We propose a system call an independent software vendor Compuware $140 million dependence graph based software birthmark called SCDG to license its software and $260 million to purchase its ser- birthmark, and examine how well it reflects unique behav- vices [1] because it was discovered that certain IBM products ioral characteristics of a program. To our knowledge, our contained code from Compuware. detection system based on SCDG birthmark is the first one To protect software from theft, Collberg and Thoborson that is capable of detecting software component theft where [10] proposed software watermark techniques. Software wa- only partial code is stolen. We demonstrate the strength of termark is a unique identifier embedded in the protected our birthmark against various evasion techniques, including software, which is hard to remove but easy to verify.
    [Show full text]
  • Rkward: a Comprehensive Graphical User Interface and Integrated Development Environment for Statistical Analysis with R
    JSS Journal of Statistical Software June 2012, Volume 49, Issue 9. http://www.jstatsoft.org/ RKWard: A Comprehensive Graphical User Interface and Integrated Development Environment for Statistical Analysis with R Stefan R¨odiger Thomas Friedrichsmeier Charit´e-Universit¨atsmedizin Berlin Ruhr-University Bochum Prasenjit Kapat Meik Michalke The Ohio State University Heinrich Heine University Dusseldorf¨ Abstract R is a free open-source implementation of the S statistical computing language and programming environment. The current status of R is a command line driven interface with no advanced cross-platform graphical user interface (GUI), but it includes tools for building such. Over the past years, proprietary and non-proprietary GUI solutions have emerged, based on internal or external tool kits, with different scopes and technological concepts. For example, Rgui.exe and Rgui.app have become the de facto GUI on the Microsoft Windows and Mac OS X platforms, respectively, for most users. In this paper we discuss RKWard which aims to be both a comprehensive GUI and an integrated devel- opment environment for R. RKWard is based on the KDE software libraries. Statistical procedures and plots are implemented using an extendable plugin architecture based on ECMAScript (JavaScript), R, and XML. RKWard provides an excellent tool to manage different types of data objects; even allowing for seamless editing of certain types. The objective of RKWard is to provide a portable and extensible R interface for both basic and advanced statistical and graphical analysis, while not compromising on flexibility and modularity of the R programming environment itself. Keywords: GUI, integrated development environment, plugin, R.
    [Show full text]
  • Fedora 14 User Guide
    Fedora 14 User Guide Using Fedora 14 for common desktop computing tasks Fedora Documentation Project User Guide Fedora 14 User Guide Using Fedora 14 for common desktop computing tasks Edition 1.0 Author Fedora Documentation Project [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/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. 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. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. For guidelines on the permitted uses of the Fedora trademarks, refer to https://fedoraproject.org/wiki/ Legal:Trademark_guidelines. 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.
    [Show full text]
  • Open Source Software Development: an Overview
    COMPUTING PRACTICES Open Source Software Development: An Overview Although some challenge the value of open source software development,its popularity cannot be disputed. This overview of open source licensing and development models describes some of the movement’s main principles. Ming-Wei Wu roprietary software vendors operate on a seeks to develop Unix-compatible software and return closed-source model: They develop their software to a state of freedom. Ying-Dar Lin own software and release that software to Stallman is both an open source evangelist and a National the public with the intention of gaining mar- major open source contributor as the principal author Chiao Tung University, ket penetration and earning a profit. The of the GNU C Compiler (GCC), GNU symbolic Taiwan Popen source movement, while still profitable in many debugger (GDB), GNU Emacs, and more. All these ways to profit-oriented companies, relies on a differ- packages provide essential tools for GNU/Linux. The ent set of practices. In the open source movement, Red Hat 7.1 distribution, which collects some 1,016 everyone capable of writing code is welcome to join packages altogether, contains 70 GNU packages. in, a strategy that—according to open source advo- The purpose of the Free Software Foundation is not cates—directly leads to more robust software and to ensure distributing software to the end user without more diverse business models. cost, but to ensure that the end user can use the soft- While some challenge the general assumptions ware freely. From the Free Software Foundation’s per- about the benefits of open source software develop- spective, the term “free software” has nothing to do ment,1 the evidence of popular buy-in cannot be dis- with price: A program is free software if you have the puted.
    [Show full text]
  • Awoken Icon Theme - Installation & Customizing Instructions 1
    Awoken Icon Theme - Installation & Customizing Instructions 1 AWOKEN ICON THEME Installation & Customizing Instructions Alessandro Roncone mail: [email protected] homepage: http://alecive.deviantart.com/ Awoken homepage (GNOME Version): link kAwoken homepage (KDE Version): link Contents 1 Iconset Credits 3 2 Copyright 3 3 Installation 3 3.1 GNOME........................................................3 3.2 KDE..........................................................4 4 Customizing Instructions 4 4.1 GNOME........................................................4 4.2 KDE..........................................................5 5 Overview of the customization script6 5.1 How to customize a single iconset..........................................7 6 Customization options 8 6.1 Folder types......................................................8 6.2 Color-NoColor.................................................... 11 6.3 Distributor Logos................................................... 11 6.4 Trash types...................................................... 11 6.5 Other Options.................................................... 11 6.5.1 Gedit icon................................................... 11 6.5.2 Computer icon................................................ 11 6.5.3 Home icon................................................... 11 6.6 Deprecated...................................................... 12 7 How to colorize the iconset 13 8 Icons that don't want to change (but I've drawed) 14 9 Conclusions 15 9.1 Changelog......................................................
    [Show full text]
  • KDE 2.0 Development
    00 8911 FM 10/16/00 2:09 PM Page i KDE 2.0 Development David Sweet, et al. 201 West 103rd St., Indianapolis, Indiana, 46290 USA 00 8911 FM 10/16/00 2:09 PM Page ii KDE 2.0 Development ASSOCIATE PUBLISHER Michael Stephens Copyright © 2001 by Sams Publishing This material may be distributed only subject to the terms and conditions set ACQUISITIONS EDITOR forth in the Open Publication License, v1.0 or later (the latest version is Shelley Johnston presently available at http://www.opencontent.org/openpub/). DEVELOPMENT EDITOR Distribution of the work or derivative of the work in any standard (paper) book Heather Goodell form is prohibited unless prior permission is obtained from the copyright holder. MANAGING EDITOR No patent liability is assumed with respect to the use of the information con- Matt Purcell tained herein. Although every precaution has been taken in the preparation of PROJECT EDITOR this book, the publisher and author assume no responsibility for errors or omis- Christina Smith sions. Neither is any liability assumed for damages resulting from the use of the information contained herein. COPY EDITOR International Standard Book Number: 0-672-31891-1 Barbara Hacha Kim Cofer Library of Congress Catalog Card Number: 99-067972 Printed in the United States of America INDEXER Erika Millen First Printing: October 2000 PROOFREADER 03 02 01 00 4 3 2 1 Candice Hightower Trademarks TECHNICAL EDITOR Kurt Granroth All terms mentioned in this book that are known to be trademarks or service Matthias Ettrich marks have been appropriately capitalized. Sams Publishing cannot attest to Kurt Wall the accuracy of this information.
    [Show full text]
  • The Theory of Relative Dependency: Higher Coupling Concentration in Smaller Modules
    featuresoftware measurement and quality The Theory of Relative Dependency: Higher Coupling Concentration in Smaller Modules A. Günes¸ Koru, University of Maryland, Baltimore County Khaled El Emam, University of Ottawa ur recent research on several large-scale software products has consis- Our observations on tently shown that smaller modules are proportionally more defect prone.1–3 large-scale software These findings challenge the common recommendations from the litera- systems lead to an ture suggesting that quality assurance (QA) and quality control (QC) re- empirically based Osources should focus on larger modules. Those recommendations are based on the un- theory that smaller founded assumption that a monotonically increasing linear relationship exists between modules will be module size and defects.1–4 Given that complexity is correlated with size,5 following proportionally more such recommendations ensures that the more formulated a testable hypothesis of relative depen- dependent compared complex modules receive greater scrutiny. How- dency (RD) for software modules: to larger ones. ever, our recent findings imply that, given limited and a fixed amount of resources, focusing on the HRD: Smaller modules are proportionally smaller modules would lead to more effective de- more coupled. fect detection.1–3 So, it’s important to understand the mechanisms behind those findings to make HRD requires us to study the size-coupling re- the case for amending current practices. lationship for software modules. So far, the em- Research has shown that higher module de- pirical evidence has shown a positive correlation pendencies, also called higher coupling, result in between module size and coupling because of more defects by increasing the likelihood of in- their monotonically increasing relationship.11–13 terface defects.6–10 “Coupling” as we use it here However, those findings aren’t enough to test corresponds to the concept of fan-out (depend- HRD because correlations don’t imply propor- ing on other modules).
    [Show full text]
  • Szövegszerkesztés
    Szövegszerkesztés Wettl Ferenc 2006. október 1. Wettl Ferenc () Szövegszerkesztés 2006. október 1. 1 / 5 Tartalom 1 Szövegszerkesztők Típusai Mit kell tudnia? Wettl Ferenc () Szövegszerkesztés 2006. október 1. 2 / 5 pl.: vi (vim, cream), emacs (XEmacs, MicroEmacs), joe, pico, Notepad (Microsoft Windows default), SimpleText (Classic Mac OS default), TextEdit (Mac OS X default), gedit (Gnome), kate és kile (KDE), ld. még a wikipediában IDE (integrated development environment, integrated design environment, integrated debugging environment), dokumentumszerkesztő (word processor, document preparation system) pl.: AbiWord, KWord, OpenOffice.org Writer, Ted, a határon: GNU TeXmacs, LyX, üzleti: MS Word, online: Writely, . (Allin Cottrell: Word Processors: Stupid and Inefficient) szedő rendszer (electronic typesetting system) pl.: troff, Groff, TEX/LATEX. (WYSIWYG, WYSIWYM). DTP (Desktop publishing) pl.: QuarkXPress, Adobe InDesign, Scribus (szabad), Microsoft Publisher, Apple Pages. Szövegszerkesztés Szövegszerkesztők típusai szövegszerkesztő (text editor) – programkód, egyszerű szöveg, vagy ember által is olvashatóan kódolt (human-readable) dokumentum (pl. wiki) írására, Wettl Ferenc () Szövegszerkesztés 2006. október 1. 3 / 5 IDE (integrated development environment, integrated design environment, integrated debugging environment), dokumentumszerkesztő (word processor, document preparation system) pl.: AbiWord, KWord, OpenOffice.org Writer, Ted, a határon: GNU TeXmacs, LyX, üzleti: MS Word, online: Writely, . (Allin Cottrell: Word Processors: Stupid
    [Show full text]
  • Glossary.Pdf
    2 Contents 1 Glossary 4 3 1 Glossary Technologies Akonadi The data storage access mechanism for all PIM (Personal Information Manager) data in KDE SC 4. One single storage and retrieval system allows efficiency and extensibility not possible under KDE 3, where each PIM component had its own system. Note that use of Akonadi does not change data storage formats (vcard, iCalendar, mbox, maildir etc.) - it just provides a new way of accessing and updating the data.</p><p> The main reasons for design and development of Akonadi are of technical nature, e.g. having a unique way to ac- cess PIM-data (contacts, calendars, emails..) from different applications (e.g. KMail, KWord etc.), thus eliminating the need to write similar code here and there.</p><p> Another goal is to de-couple GUI applications like KMail from the direct access to external resources like mail-servers - which was a major reason for bug-reports/wishes with regard to perfor- mance/responsiveness in the past.</p><p> More info:</p><p> <a href=https://community.kde.org/KDE_PIM/Akonadi target=_top>Akonadi for KDE’s PIM</a></p><p> <a href=https://en.wikipedia.org/wiki/Akonadi target=_top>Wikipedia: Akonadi</a></p><p> <a href=https://techbase.kde.org/KDE_PIM/Akonadi target=_top>Techbase - Akonadi</a> See Also "GUI". See Also "KDE". Applications Applications are based on the core libraries projects by the KDE community, currently KDE Frameworks and previously KDE Platform.</p><p> More info:</p><p> <a href=https://community.kde.org/Promo/Guidance/Branding/Quick_Guide/ target=_top>KDE Branding</a> See Also "Plasma".
    [Show full text]
  • Migration from Windows to Linux for a Small Engineering Firm "A&G Associates"
    Rochester Institute of Technology RIT Scholar Works Theses 2004 Migration from Windows to Linux for a small engineering firm "A&G Associates" Trimbak Vohra Follow this and additional works at: https://scholarworks.rit.edu/theses Recommended Citation Vohra, Trimbak, "Migration from Windows to Linux for a small engineering firm A&G" Associates"" (2004). Thesis. Rochester Institute of Technology. Accessed from This Thesis is brought to you for free and open access by RIT Scholar Works. It has been accepted for inclusion in Theses by an authorized administrator of RIT Scholar Works. For more information, please contact [email protected]. Migration from Windows to Linux for a Small Engineering Firm "A&G Associates" (H ' _T ^^L. WBBmBmBBBBmb- Windows Linux by Trimbak Vohra Thesis submitted in partial fulfillment of the requirements for the degree of Master of Science in Information Technology Rochester Institute of Technology B. Thomas Golisano College of Computing and Information Sciences Date: December 2, 2004 12/B2/28B2 14:46 5854752181 RIT INFORMATION TECH PAGE 02 Rochester Institute of Teehnology B. Thomas Golisano College of Computing and Information Sciences Master of Science in Information Technology Thesis Approval Form Student Name: Trimbak Vohra Thesis Title: Migration from Windows to Unux for a Small Engineeriog Firm "A&G Associates" Thesis Committee Name Signature Date Luther Troell luther IrQell, Ph.D ttL ",j7/Uy Chair G. L. Barido Prof. ~~orge Barido ? - Dec:. -cl7' Committee Member Thomas Oxford Mr. Thomas OxfocQ \ 2. L~( Q~ Committee Member Thesis Reproduction Permission Form Rochester Institute of Technology B. Thomas Golisano College of Computing and Information Sciences Master of Science in Information Technology Migration from Windows to Linux for a Small Engineering Firm "A&G Associates" I,Trimbak Vohra, hereby grant permission to the Wallace Library of the Rochester Institute of Technology to reproduce my thesis in whole or in part.
    [Show full text]
  • Fundamentos Tecnológicos De Información
    Fundamentos Tecnológicos de Información Facilitador: Marcos Espinoza M. [email protected] [email protected] ECOTEC 6/3/2015 1 Software Fund. Tec. de Información 6/3/2015 2 ¿Qué es un procesador de palabras? Fund. Tec. de Información 6/3/2015 3 Procesador de palabras • También llamado procesador de texto es una aplicación informática que permite crear y editar documentos de texto en una computadora. Se trata de un software de múltiples funcionalidades para la redacción, con diferentes tipografías, tamaños de letra, colores, tipos de párrafos, efectos artísticos y otras opciones. Fund. Tec. de Información 6/3/2015 4 Procesador de palabras • Los procesadores de palabras en su aplicación más simple, reemplazan a la máquina de escribir como medio para transcribir o capturar cartas, reportes y otro material escrito. Sin embargo, la moderna tecnología computacional convierte a estos programas en algo mucho más poderoso y flexible. Fund. Tec. de Información 6/3/2015 5 Procesador de palabras • A diferencia de las máquinas de escribir, los programas de cómputo permiten que los documentos se editen infinidad de veces. El texto puede ser transcrito, modificado, cortado, copiado, pegado y suprimido. • Los programas de cómputo son capaces de desplegar textos e imágenes de múltiples formas que no son posibles con las máquinas de escribir. Fund. Tec. de Información 6/3/2015 6 Procesador de palabras • Los documentos también pueden ser guardados en múltiples versiones a las que luego se puede tener nuevo acceso según se requiera. Por ejemplo, cuando una persona cambia el texto escrito por otra, los procesadores pueden comparar las mismas versiones del documento para identificar que cambios fueron efectuados.
    [Show full text]
  • Quarterly Report Q2/2009 - Q1/2010
    Quarterly Report Q2/2009 - Q1/2010 the appreciation for KDE's work on the Free Desktop, and to help the KDE e.V. to conduct all those different activities, sprints, meetings, conferences and many others also in the future. Now, without further ado, please read on for an update of the KDE e.V.'s activities over the past year. Signed, Dear KDE e.V. member, In front of you, you have another update on the activities conducted by the KDE e.V.. A lot has happened over the last year in the KDE ecosystem. Since 2009's Akademy, Cornelius Schumacher for the KDE e.V. Board KDE has released two feature releases, KDE SC 4.3 and <[email protected]> KDE SC 4.4. Those two releases verify the design of the KDE platform as a whole, but just in the same way these releases are only the result of thousands of hours put into the KDE codebase over the course of last year. In the Supported Member Activities background, we have the KDE e.V., the foundation to support the KDE community organisationally, legally and Developer Meetings and Sprints not least financially thanks to the help of many people and companies who chose to contribute not by offering their Akonadi Sprint, 3rd - 5th April 2009 time, but by chipping in with some money. With 16 participants the largest Akonadi meeting so far took place in April in the KDAB office in Berlin. Topics In particular our successful strategy to improve the KDE included discussions about core architecture such as platform, desktop and applications is to hold regular searching and virtual collections, design and development of developer sprints, and thereby making it possible for the four different email resources (IMAP, POP3, Maildir and developers who usually collaborate across the Internet to mbox), resulting in a little race to see who would get the meet, discuss, and work together on their projects in first working email folder listing, as well as planning of the person.
    [Show full text]