DOCSLIB.ORG

Microsoft Office Word 2003 Rich Text Format (RTF) Specification White Paper Published: April 2004 Table of Contents

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Microsoft Office Word 2003 Rich Text Format (RTF) Specification White Paper Published: April 2004 Table of Contents Microsoft Office Word 2003 Rich Text Format (RTF) Specification White Paper Published: April 2004 Table of Contents Introduction......................................................................................................................................1 RTF Syntax.......................................................................................................................................2 Conventions of an RTF Reader.............................................................................................................4 Formal Syntax...................................................................................................................................5 Contents of an RTF File.......................................................................................................................6 Header.........................................................................................................................................6 Document Area............................................................................................................................29 East ASIAN Support........................................................................................................................142 Escaped Expressions...................................................................................................................142 Character Set.............................................................................................................................143 Character Mapping......................................................................................................................143 Font Family................................................................................................................................143 Appendix A: Sample RTF Reader Application......................................................................................153 How to Write an RTF Reader.........................................................................................................154 A Sample RTF Reader Implementation...........................................................................................154 Notes on Implementing Other RTF Features....................................................................................158 Other Problem Areas in RTF.........................................................................................................158 Appendix B: Index of RTF Control Words............................................................................................178 Special Characters and A–B..........................................................................................................179 C-E...........................................................................................................................................185 F-L...........................................................................................................................................193 M-O..........................................................................................................................................201 P-R...........................................................................................................................................205 S-T...........................................................................................................................................213 U-Z..........................................................................................................................................223 Appendix C: Control Words introduced by other Microsoft Products........................................................225 Pocket Word..............................................................................................................................225 Exchange (Used in RTF<->HTML Conversions)................................................................................226 Microsoft Office Word 2003 Rich Text Format (RTF) Specification White Paper Published: April 2004 For the latest information, please see http://www.microsoft.com/office/ For Microsoft® MS-DOS®, Windows® , and Apple Macintosh Applications ® Version: RTF Version 1.8 Microsoft Technical Support Subject: Rich Text Format (RTF) Specification Specification Contents: 214 Pages 10/2003– Word 2003 RTF Specification Introduction Rich Text Format (RTF) is a method of encoding formatted text and graphics for use within applications or for data and formatting transfer between applications. Currently, users depend on special translation software to move word-processing documents between various applications developed by different companies. RTF serves as both a standard of data transfer between word processing software, document formatting, and a means of migrating content from one operating system to another. This document specifies the format used by RTF for text and graphics interchange. RTF uses ASCII (lower byte range – 7 bits) or the ANSI, PC-8, Macintosh, or IBM PC character sets to represent the formatting of a document. RTF files created in Microsoft Word 6.0 (and later) for the Macintosh and Power Macintosh have a file type of “RTF.” However, earlier versions of Word do not necessarily support all the RTF commands noted in this specification. You must consult prior versions of this document for each version of Word that was developed prior to Word 2003 in order to determine which RTF commands were supported for that release. However, files previously created with an earlier version of Word using RTF should be read without problem by newer versions of Word. Software that can convert a file to RTF is called an RTF writer. An RTF writer separates the application's control information from the actual text and writes a new file containing the text and the RTF command groups associated with that text. Software that reads an RTF file and is capable of displaying the formatting commands of the selected text on the screen as WYSIWIG is called an RTF reader. A sample RTF parsing reader application is available (see Appendix A: Sample RTF Reader Application in this document). This sample RTF parsing reader is designed for use in conjunction with this document to assist those interested in developing their own RTF readers. This application and its use are described in Appendix A. The sample RTF reader is not a for-sale product, and Microsoft does not provide technical support or any other kind of support for the sample RTF parsing reader code or this document. RTF version 1.7 included many new control words introduced specifically for Microsoft Word for Windows 95 version 7.0, Microsoft Word 97 for Windows, Microsoft Word 98 for the Macintosh, Microsoft Word 2000 for Windows, and Microsoft Word 2002 for Windows, as well as other Microsoft products. Version 1.8 includes new command extensions specifically for use with new features available in Microsoft Word 2003. RTF Syntax RTF files are plain text, usually 7-bit ASCII (low seven bits), and consist of clear text control words, control symbols, and groups. RTF files are easily transmitted between most PC based operating systems because of their 7-bit ASCII characters. However, converters that communicate with Microsoft Word for Windows or Microsoft Word for the Macintosh should expect data transfer as 8- bit characters. Unlike most clear text files, there is no set maximum line length for an RTF file before a carriage return/line feed is expected. In fact, a carriage return line feed is never expected to be found in an RTF file and can be overlooked by some RTF readers when found in clear text segments. Control Word An RTF control word is a specially formatted command used to mark characters for display on a monitor or characters destined for a printer. A control word cannot be longer than 32 characters. A control word commonly takes the following form: \LetterSequence<Delimiter> Example: \par Note A backslash begins each control word and the control word is also case sensitive. The LetterSequence is made up of alphabetic characters (a through z or A through Z). Control words (also known as Keywords) originally did not contain any uppercase characters, however in recent years uppercase characters have begun to appear in some newer control words. A Delimiter commonly is used to mark the end of an RTF control word, and can be one of the following: • A space. • A numeric digit or a hyphen (-), which indicates that a numeric parameter is associated with the control word. The subsequent digital sequence is then delimited by a space or any character other than a letter or a digit (commonly another control word which begins with a backslash). The parameter can be a positive or negative number. The range of the values for the number is generally –32767 through 32767. However, Word tends to restrict the range to –31680 through 31680 and also allows values in the range –2,147,483,648 to 2,147,483,648 for a small number of keywords (specifically \bin, \revdttm, and some picture properties). An RTF parser must allow an arbitrary string of digits as a legal value for a keyword (providing it does not exceed value ranges noted earlier). The control word can then be delimited by a space, nonalphabetic or nonnumeric character, or a backslash “\” in the same manner as any other control word. • Any character other than a letter or a digit. In this case, the delimiting character terminates the control word but is not actually part of the control word. Such as a
Load more

Recommended publications
  • The Microsoft Office Open XML Formats New File Formats for “Office 12”
    The Microsoft Office Open XML Formats New File Formats for “Office 12” White Paper Published: June 2005 For the latest information, please see http://www.microsoft.com/office/wave12 Contents Introduction ...............................................................................................................................1 From .doc to .docx: a brief history of the Office file formats.................................................1 Benefits of the Microsoft Office Open XML Formats ................................................................2 Integration with Business Data .............................................................................................2 Openness and Transparency ...............................................................................................4 Robustness...........................................................................................................................7 Description of the Microsoft Office Open XML Format .............................................................9 Document Parts....................................................................................................................9 Microsoft Office Open XML Format specifications ...............................................................9 Compatibility with new file formats........................................................................................9 For more information ..............................................................................................................10
    [Show full text]
  • Rich Text Editor Control in Asp Net
    Rich Text Editor Control In Asp Net Ginger te-heed his Manaus orchestrating tolerantly, but high-tension Peirce never recirculated so amazingly. Empathetic lemuroidOlin inarches Iggie bellicosely communizing while some Wait sipper always so rule open-mindedly! his exodes aggrandizing obliquely, he master so manfully. Dietetical and Find and rich text control is dependent on mobile applications which will be renamed to the asp. Net rich text editors and when working on mobile development and size can controls in. This tutorial help. Numerous optimization methods have been applied. Net ajax saving for controlling the editors, it only the access database in. Moving forward, we will see how this editor can be used in ASP. ASPNET WYSIWYG rich HTML editor for WebForms MVC and all versions of working Framework. Many formats, including HTML. Output jpeg and png picture in original format reducing file sizes substantially. Providing a Richer Means for Entering Text Data. Rich Text Editor for aspnet is by yet the fastest cleanest most powerful online wysiwyg content editor It's also project for PHP and ASP It enables aspnet web developers to clean any textboxtextarea with an intuitive word-like wysiwyg editor. Any form elements appear in kendo ui features are used to select. Use the sublime text editor control hero Power Apps Power Apps. For controlling the control into another way to your desired width. Rich Text Editor is from award-winning UI control that replaces a standard HTML. Add love to TINYMCE Editor TextBox using jQuery Uploadify Plugin in ASP. Read below for it appear showing in my aim is important for! Lite version is free.
    [Show full text]
  • Background Information History, Licensing, and File Formats Copyright This Document Is Copyright © 2008 by Its Contributors As Listed in the Section Titled Authors
    Getting Started Guide Appendix B Background Information History, licensing, and file formats Copyright This document is Copyright © 2008 by its contributors as listed in the section titled Authors. You may distribute it and/or modify it under the terms of either the GNU General Public License, version 3 or later, or the Creative Commons Attribution License, version 3.0 or later. All trademarks within this guide belong to their legitimate owners. Authors Jean Hollis Weber Feedback Please direct any comments or suggestions about this document to: [email protected] Acknowledgments This Appendix includes material written by Richard Barnes and others for Chapter 1 of Getting Started with OpenOffice.org 2.x. Publication date and software version Published 13 October 2008. Based on OpenOffice.org 3.0. You can download an editable version of this document from http://oooauthors.org/en/authors/userguide3/published/ Contents Introduction...........................................................................................4 A short history of OpenOffice.org..........................................................4 The OpenOffice.org community.............................................................4 How is OpenOffice.org licensed?...........................................................5 What is “open source”?..........................................................................5 What is OpenDocument?........................................................................6 File formats OOo can open.....................................................................6
    [Show full text]
  • Text Formatting with LATEX, Eclipse and SVN
    Formatting Text LATEX DEMO LATEX beamer Text Formatting with LATEX, Eclipse and SVN Desislava Zhekova CIS, LMU [email protected] July 1, 2013 Desislava Zhekova Text Formatting with LATEX, Eclipse and SVN Formatting Text LATEX DEMO LATEX beamer Outline 1 Formatting Text Text Editor vs. Word Processor What You See Is What You Get 2 LATEX What is LATEX? Microsoft Word vs LATEX Eclipse & SVN 3 DEMO Document Classes Document Class Options Basics Style Files/Packages LATEX for Linguists 4 LATEX beamer Desislava Zhekova Text Formatting with LATEX, Eclipse and SVN http://en.wikipedia.org/wiki/Comparison_of_text_editors Formatting Text LATEX Text Editor vs. Word Processor DEMO What You See Is What You Get LATEX beamer Text Editor vs. Word Processor Text Editors used to handle plain text (a simple character set, such as ASCII, is used to represent numbers, letters, and a small number of symbols) the only non-printing characters they support are: newline, tab, and form feed Desislava Zhekova Text Formatting with LATEX, Eclipse and SVN Formatting Text LATEX Text Editor vs. Word Processor DEMO What You See Is What You Get LATEX beamer Text Editor vs. Word Processor Text Editors used to handle plain text (a simple character set, such as ASCII, is used to represent numbers, letters, and a small number of symbols) the only non-printing characters they support are: newline, tab, and form feed http://en.wikipedia.org/wiki/Comparison_of_text_editors Desislava Zhekova Text Formatting with LATEX, Eclipse and SVN Formatting Text LATEX Text Editor vs. Word Processor DEMO What You See Is What You Get LATEX beamer Text Editors Notepad Bundled with Microsoft Windows Desislava Zhekova Text Formatting with LATEX, Eclipse and SVN Formatting Text LATEX Text Editor vs.
    [Show full text]
  • Sharing Files with Microsoft Office Users
    Sharing Files with Microsoft Office Users Title: Sharing Files with Microsoft Office Users: Version: 1.0 First edition: November 2004 Contents Overview.........................................................................................................................................iv Copyright and trademark information........................................................................................iv Feedback.................................................................................................................................... iv Acknowledgments......................................................................................................................iv Modifications and updates......................................................................................................... iv File formats...................................................................................................................................... 1 Bulk conversion............................................................................................................................... 1 Opening files....................................................................................................................................2 Opening text format files.............................................................................................................2 Opening spreadsheets..................................................................................................................2 Opening presentations.................................................................................................................2
    [Show full text]
  • Document Conversion Technical Manual Version: 10.3.0
    Kofax Communication Server KCS Document Conversion Technical Manual Version: 10.3.0 Date: 2019-12-13 © 2019 Kofax. All rights reserved. Kofax is a trademark of Kofax, Inc., registered in the U.S. and/or other countries. All other trademarks are the property of their respective owners. No part of this publication may be reproduced, stored, or transmitted in any form without the prior written permission of Kofax. Table of Contents Chapter 1: Preface...................................................................................................................................... 7 Purpose...............................................................................................................................................7 Third Party Licenses................................................................................................................7 Usage..................................................................................................................................................7 Feature Comparison (Links Versus TWS)......................................................................................... 8 Conversion Tools................................................................................................................................ 8 Imgio.......................................................................................................................................10 File Formats......................................................................................................................................10
    [Show full text]
  • The Journal of Transport and Land Use: Guidelines for Authors
    The Journal of Transport and Land Use: Guidelines for Authors Summer 2018 Revision These guidelines are provided to assist authors in preparing article manuscripts for publication in the Journal of Transport and Land Use. Careful preparation of your manuscript will avoid many potential problems and delays in the publication process and help ensure that your work is presented accurately and effectively. The guidelines cover the following major areas of manuscript preparation and editorial policy: 1. Preparing text 2. Preparing graphics and tables 3. Documentation (citations and references) 4. Data availability 5. Copyright and licensing 1 Preparing text 1.1 Style guides The Publication Manual of the American Psychological Association (APA), 6th ed. is the standard editorial reference for the Journal; it contains comprehensive guidelines on style and grammar. In addition to the printed edition, APA resources are available online at www.apastyle.org. 1.2 Software and file formats Initial submissions of articles for consideration must be made in PDF format. All submissions must be typed, double spaced, and in 12 point Times font or equivalent. Accepted manuscripts provided for typesetting: after authors have made any modifications requested by the editorial board, a new electronic copy of the article is required for typesetting. The following text formats are acceptable: • Microsoft Word or OpenOffice Word documents are preferred. • Unicode text: Unicode is a text encoding system that can represent many more characters (including accented characters and typographic symbols) than standard ASCII text. Many word processors, including recent versions of Microsoft Word, can save documents as Unicode text. The UTF-8 or UTF-16 encoding schemes are acceptable.
    [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]
  • Revisiting XSS Sanitization
    Revisiting XSS Sanitization Ashar Javed Chair for Network and Data Security Horst G¨ortzInstitute for IT-Security, Ruhr-University Bochum [email protected] Abstract. Cross-Site Scripting (XSS) | around fourteen years old vul- nerability is still on the rise and a continuous threat to the web applica- tions. Only last year, 150505 defacements (this is a least, an XSS can do) have been reported and archived in Zone-H (a cybercrime archive)1. The online WYSIWYG (What You See Is What You Get) or rich-text editors are now a days an essential component of the web applications. They allow users of web applications to edit and enter HTML rich text (i.e., formatted text, images, links and videos etc) inside the web browser window. The web applications use WYSIWYG editors as a part of comment functionality, private messaging among users of applications, blogs, notes, forums post, spellcheck as-you-type, ticketing feature, and other online services. The XSS in WYSIWYG editors is considered more dangerous and exploitable because the user-supplied rich-text con- tents (may be dangerous) are viewable by other users of web applications. In this paper, we present a security analysis of twenty five (25) pop- ular WYSIWYG editors powering thousands of web sites. The anal- ysis includes WYSIWYG editors like Enterprise TinyMCE, EditLive, Lithium, Jive, TinyMCE, PHP HTML Editor, markItUp! universal markup jQuery editor, FreeTextBox (popular ASP.NET editor), Froala Editor, elRTE, and CKEditor. At the same time, we also analyze rich-text ed- itors available on very popular sites like Twitter, Yahoo Mail, Amazon, GitHub and Magento and many more.
    [Show full text]
  • File Format Guidelines for Management and Long-Term Retention of Electronic Records
    FILE FORMAT GUIDELINES FOR MANAGEMENT AND LONG-TERM RETENTION OF ELECTRONIC RECORDS 9/10/2012 State Archives of North Carolina File Format Guidelines for Management and Long-Term Retention of Electronic records Table of Contents 1. GUIDELINES AND RECOMMENDATIONS .................................................................................. 3 2. DESCRIPTION OF FORMATS RECOMMENDED FOR LONG-TERM RETENTION ......................... 7 2.1 Word Processing Documents ...................................................................................................................... 7 2.1.1 PDF/A-1a (.pdf) (ISO 19005-1 compliant PDF/A) ........................................................................ 7 2.1.2 OpenDocument Text (.odt) ................................................................................................................... 3 2.1.3 Special Note on Google Docs™ .......................................................................................................... 4 2.2 Plain Text Documents ................................................................................................................................... 5 2.2.1 Plain Text (.txt) US-ASCII or UTF-8 encoding ................................................................................... 6 2.2.2 Comma-separated file (.csv) US-ASCII or UTF-8 encoding ........................................................... 7 2.2.3 Tab-delimited file (.txt) US-ASCII or UTF-8 encoding .................................................................... 8 2.3
    [Show full text]
  • A Brief LATEX Tutorial
    A brief LATEX tutorial. Henri P. Gavin Department of Civil and Environmental Engineering Duke University Durham, NC 27708{0287 [email protected] September 30, 2002 Abstract LATEX is a very powerful text processing system available to all students through the university's network of Unix work stations. Versions of LATEX which run on PC's and Mac's are available through the Internet. LATEX is becoming the \standard" text processor for publications in science, engineering, and mathematics. LATEX has many features, including: • The printed output is BEAUT IFUL! • Equations are relatively easy to enter, once you get the hang of it. • LATEX automatically numbers the sections, subsections, figures, tables, footnotes, equations, theorems, lemmas, and the references of your paper. When you add a new section or sub-section, or a new reference, every item is re-numbered au- tomatically! It can create its own table of contents and indices automatically as well. • It can easily manage very long documents, like theses and books. The down-side of LATEX is that it is somewhat cumbersome to use and can be difficult to learn. Many LATEX manuals are not written for the rank beginner, and don't make it terribly clear how to make simple formatting changes such as margins, font size, or line spacing. For many people, learning LATEX through examples is the easiest way to go. The purpose of this document is to illustrate what LATEX can do for you, and (without getting into too much detail) show you how to do it, so that you can learn to use LATEX quickly and easily.
    [Show full text]
  • Use Word to Open Or Save a File in Another File Format
    Use Word to open or save a file in another file format You can use Microsoft Word 2010 to open or save files in other formats. For example, you can open a Web page and then upgrade it to access the new and enhanced features in Word 2010. Open a file in Word 2010 You can use Word 2010 to open files in any of several formats. 1. Click the File tab. 2. Click Open. 3. In the Open dialog box, click the list of file types next to the File name box. 4. Click the type of file that you want to open. 5. Locate the file, click the file, and then click Open. Save a Word 2010 document in another file format You can save Word 2010 documents to any of several file formats. Note You cannot use Word 2010 to save a document as a JPEG (.jpg) or GIF (.gif) file, but you can save a file as a PDF (.pdf) file. 1. Click the File tab. 2. Click Save As. 3. In the Save As dialog box, click the arrow next to the Save as type list, and then click the file type that you want. For this type of file Choose .docx Word Document .docm Word Macro-Enabled Document .doc Word 97-2003 Document .dotx Word Template .dotm Word Macro-Enabled Template .dot Word 97-2003 Template .pdf PDF .xps XPS Document .mht (MHTML) Single File Web Page .htm (HTML) Web Page .htm (HTML, filtered) Web Page, Filtered .rtf Rich Text Format .txt Plain Text .xml (Word 2007) Word XML Document .xml (Word 2003) Word 2003 XML Document odt OpenDocument Text .wps Works 6 - 9 4.
    [Show full text]