DOCSLIB.ORG

Understanding Line Data Formats

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

BY DAVID STAAL Understanding Line Data Formats ince a large amount of production printing is still based on line data and its hybrids, technical Sanalysts in the print industry need to understand these line data formats, especially when trying to integrate mainframe print data with PC-based solutions. laser printers with full graphic non-proportional, that is, the characters are all the ALTHOUGH capabilities have been available for same width. more than a decade, a large amount of production printing is G use continuous feed paper (with holes on the still based on line data (or hybrids, such as Xerox LCDS). For sides), which can include blank paper, green bar this reason, technical analysts in the print industry need to paper and special forms, such as labels and thoroughly understand line data formats, especially when pre-printed checks trying to integrate mainframe print data with PC-based G move down the page in only one direction. The paper is solutions. As an instructor, I have found that many analysts moved with a tractor feed and can be advanced, but not lack this basic knowledge, largely because it is not available backed up. in any simple form. This article is intended to provide a basic and thorough Line data is data that is formatted for line printers. It description of the most common line data formats, including generally has the following characteristics: mainframe Fixed Block (FBA or FBM), Variable Block (VBA or VBM), and ASCII line data. This article will also G is text only explain the basic varieties of printer carriage control and G is stored as records or lines of data provide examples of these formats. G has some kind of “carriage control” commands that instruct Line data, or line printer data, can be defined simply as the printer on how to move down the paper, such as Line data formatted for a printer that prints one line at a time. As Feed or Page Break printers have evolved, more advanced printers (those that could support fonts and graphics) continued to support the THREE ELEMENTS OF LINE DATA data intended for the older line printers, as a backward compatibility feature. Eventually, the expression “line data” Over the years, and on different computing platforms, was coined to refer to this older data stream. For a thorough many formats evolved for storing line data. The most com- understanding of line data, it is necessary to review the mon of these formats (e.g., ASCII text, EBCDIC VBA or original target of line data, which is, of course, a line printer. VBM and EBCDIC FBA or FBM) will be discussed in detail later in this article. To interpret any line data format, it is nec- LINE PRINTERS essary to identify the following three basic elements that make up the format: Line printers, sometimes called impact printers, have the following characteristics: G Record Separation: How are the records separated or delimited? G print one line or less (one character) at a time G Carriage Control: What type of carriage control G print text only, no graphics is used? G use a fixed font because the characters are physically G Character Set: Is the data EBCDIC, ASCII or engraved on the print heads or print band. The font is something else? TECHNICAL SUPPORT • FEBRUARY 2001 ©2001 Technical Enterprises, Inc. Reproduction of this document without permission is prohibited. Record Separation FIGURE 1: CARRIAGE CONTROL Because line data is fundamentally Carriage Control Machine Machine ASA SCS ASCII record-oriented, methods of storing line w/out data with data (ANSI) CC data must allow for the separating or Do not space 03 (no op) 01 + 0D 0D delimiting of records. This ensures that the Space one line 0B09 (space) 0D 15 0D 0A program reading the data doesn’t accidentally Space two lines 13 11 0 0D 15 15 string together two or more records or break Space three lines 1B19 - 0D 15 15 15 Skip to Channel 1 8B89 1 0D 0C 0C a record into pieces. Skip to Channel 2 93 91 2 0D 04 82 The following three basic schemes are Skip to Channel 3 9B99 3 0D 04 83 used by different line data formats for Skip to Channel 4 A3 A1 4 0D 04 84 record separation: Skip to Channel 5 ABA9 5 0D 04 85 Skip to Channel 6 B3 B1 6 0D 04 86 Skip to Channel 7 BB B9 7 0D 04 87 G Fixed Length Records: This is the Skip to Channel 8 C3 C1 8 0D 04 88 most basic scheme where you arbitrarily Skip to Channel 9 CBC9 9 0D 04 89 decide on a length, such as 80 or 1331, Skip to Channel 10 D3 D1 A 0D 04 7A and all records in the file are made to Skip to Channel 11 DBD9 B 0D 04 7B Skip to Channel 12 E3 E1 C 0D 04 7C be the same length. A program processing a fixed-length file of 133-byte records, FIGURE 2: SAMPLE LINE DATA for example, can then just read 133 bytes into its buffer at a time and A TEST OF CARRIAGE CONTROL. Single Space. assume that it has read in one record. This scheme is used primarily for Double Space. mainframes, and the most common format for this is called FBA (Fixed Block with ASA/ANSI carriage control) or FBM (Fixed Block with Machine carriage control). G Record Delimiters: The record delimiter New Page scheme relies on special characters that A TEST OF CARRIAGE CONTROL. are different from normal text to mark the end of a record. The most familiar Triple Space. example of this is ASCII text, which Double Space. Single Space. uses the Carriage Return (0Dh), Line Overprint Feed (0Ah), and Form Feed (0Ch) as record delimiters. A program processing this data would read one byte at a time, FIGURE 3: LINE DATA ELEMENTS FOR FBA and when it came to one of these special Record Separation Fixed Length Records characters, it would assume it had Carriage Control ASA reached the end of the record. One Character Set EBCDIC flaw in this approach is that something unusual in the data portion of the FIGURE 4: RECORD STRUCTURE FOR FBA record (such as an escape code string) might get confused with a Record 1 Record 2 record delimiter. C Data C Data G Length Byte or Word: The most advanced and flexible scheme for Carriage Control byte separating records is to use a byte or two (a word) at the beginning of each using Length Words are VBA (Variable printer carriage control must have the fol- record to store the length of the following Blocked with ASA carriage control) or lowing two basic commands: record. This approach provides the VBM (Variable Blocked with Machine G move down a line (called Line Feed, benefit of storing variable length carriage control) and Barr S/370 format. New Line or Space One Line) records, and allows you to store any G move to top of next page (called Form type of data, not just text. For example, Carriage Control Feed, Page Break or Skip to Channel 1) applications used with Xerox printers Line data needs to have some kind of car- can store Xerox Metacode inside of a riage control, which are the instructions to Following are the four most common line data format using this scheme. Two the printer on how to move vertically down types of carriage control used in the produc- common examples of line data formats the page. At a minimum, any type of line tion printing business: 1The number 133 is derived from the old line printers that could print 132 columns wide. The record would store 1 byte of ASA carriage control followed by 132 bytes of text. ©2001 Technical Enterprises, Inc. Reproduction of this document without permission is prohibited. TECHNICAL SUPPORT • FEBRUARY 2001 G ASCII: used in the PC, Unix and FIGURE 5: HEX DUMP OF FBA Internet arenas 00000000 4E C1 40 E3 C5 E2 E3 40-D6 C6 40 C3 C1 D9 D9 C9 +A TEST OF CARRI G SCS: used in RJE, 3270, and 5250 00000010 C1 C7 C5 40 C3 D6 D5 E3-D9 D6 D3 4B 40 40 40 40 AGE CONTROL. 00000020 40 40 40 40 40 40 40 40-40 40 40 40 40 40 40 40 print streams 00000030 40 40 40 40 40 40 40 40-40 40 40 40 40 40 40 40 G ASA or ANSI: used on mainframes 00000040 40 40 40 40 40 40 40 40-40 40 40 40 40 40 40 40 00000050 40 40 40 40 40 40 40 40-40 40 40 40 40 40 40 40 and AS/400s, as well as adopted for 00000060 40 40 40 40 40 40 40 40-40 40 40 40 40 40 40 40 other platforms 00000070 40 40 40 40 40 40 40 40-40 40 40 40 40 40 40 40 00000080 40 40 40 40 40 40 E2 89-95 87 93 85 40 E2 97 81 _Single Spa G 1403/3211 Machine: native carriage 00000090 83 85 4B 40 40 40 40 40-40 40 40 40 40 40 40 40 ce. control used on mainframe channel- 000000A0 40 40 40 40 40 40 40 40-40 40 40 40 40 40 40 40 000000B0 40 40 40 40 40 40 40 40-40 40 40 40 40 40 40 40 attached line printers 000000C0 40 40 40 40 40 40 40 40-40 40 40 40 40 40 40 40 000000D0 40 40 40 40 40 40 40 40-40 40 40 40 40 40 40 40 000000E0 40 40 40 40 40 40 40 40-40 40 40 40 40 40 40 40 The table in Figure 1 shows the hexa- 000000F0 40 40 40 40 40 40 40 40-40 40 40 40 40 40 40 40 00000100 40 40 40 40 40 40 40 40-40 40 F0 C4 96 A4 82 93 0Doubl decimal values for the standard carriage 00000110 85 40 E2 97 81 83 85 4B-40 40 40 40 40 40 40 40 e Space.
Recommended publications
  • Chapter 5 Formatting Pages: Basics Page Styles and Related Features Copyright

    Chapter 5 Formatting Pages: Basics Page Styles and Related Features Copyright

    Writer 6.0 Guide Chapter 5 Formatting Pages: Basics Page styles and related features Copyright This document is Copyright © 2018 by the LibreOffice Documentation Team. Contributors are listed below. You may distribute it and/or modify it under the terms of either the GNU General Public License (http://www.gnu.org/licenses/gpl.html), version 3 or later, or the Creative Commons Attribution License (http://creativecommons.org/licenses/by/4.0/), version 4.0 or later. All trademarks within this guide belong to their legitimate owners. Contributors Jean Hollis Weber Bruce Byfield Gillian Pollack Acknowledgments This chapter is updated from previous versions of the LibreOffice Writer Guide. Contributors to earlier versions are: Jean Hollis Weber John A Smith Ron Faile Jr. Jamie Eby This chapter is adapted from Chapter 4 of the OpenOffice.org 3.3 Writer Guide. The contributors to that chapter are: Agnes Belzunce Ken Byars Daniel Carrera Peter Hillier-Brook Lou Iorio Sigrid Kronenberger Peter Kupfer Ian Laurenson Iain Roberts Gary Schnabl Janet Swisher Jean Hollis Weber Claire Wood Michele Zarri Feedback Please direct any comments or suggestions about this document to the Documentation Team’s mailing list: [email protected] Note Everything you send to a mailing list, including your email address and any other personal information that is written in the message, is publicly archived and cannot be deleted. Publication date and software version Published July 2018. Based on LibreOffice 6.0. Note for macOS users Some keystrokes and menu items are different on macOS from those used in Windows and Linux. The table below gives some common substitutions for the instructions in this book.
  • IPDS Technical Reference 1

    IPDS Technical Reference 1

    IPDS Technical Reference 1 TABLE OF CONTENTS Manuals for the IPDS card.................................................................................................................................4 Notice..................................................................................................................................................................5 Important.........................................................................................................................................................5 How to Read This Manual................................................................................................................................. 6 Symbols...........................................................................................................................................................6 About This Book..................................................................................................................................................7 Audience.........................................................................................................................................................7 Terminology.................................................................................................................................................... 7 About IPDS.......................................................................................................................................................... 8 Capabilities of IPDS............................................................................................................................................9
  • Database Globalization Support Guide

    Database Globalization Support Guide

    Oracle® Database Database Globalization Support Guide 19c E96349-05 May 2021 Oracle Database Database Globalization Support Guide, 19c E96349-05 Copyright © 2007, 2021, Oracle and/or its affiliates. Primary Author: Rajesh Bhatiya Contributors: Dan Chiba, Winson Chu, Claire Ho, Gary Hua, Simon Law, Geoff Lee, Peter Linsley, Qianrong Ma, Keni Matsuda, Meghna Mehta, Valarie Moore, Cathy Shea, Shige Takeda, Linus Tanaka, Makoto Tozawa, Barry Trute, Ying Wu, Peter Wallack, Chao Wang, Huaqing Wang, Sergiusz Wolicki, Simon Wong, Michael Yau, Jianping Yang, Qin Yu, Tim Yu, Weiran Zhang, Yan Zhu This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S.
  • UEFI Shell Specification

    UEFI Shell Specification

    UEFI Shell Specification January 26, 2016 Revision 2.2 The material contained herein is not a license, either expressly or impliedly, to any intellectual property owned or controlled by any of the authors or developers of this material or to any contribution thereto. The material contained herein is provided on an "AS IS" basis and, to the maximum extent permitted by applicable law, this information is provided AS IS AND WITH ALL FAULTS, and the authors and developers of this material hereby disclaim all other warranties and conditions, either express, implied or statutory, including, but not limited to, any (if any) implied warranties, duties or conditions of merchantability, of fitness for a particular purpose, of accuracy or completeness of responses, of results, of workmanlike effort, of lack of viruses and of lack of negligence, all with regard to this material and any contribution thereto. Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined." The Unified EFI Forum, Inc. reserves any features or instructions so marked for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. ALSO, THERE IS NO WARRANTY OR CONDITION OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, CORRESPONDENCE TO DESCRIPTION OR NON-INFRINGEMENT WITH REGARD TO THE SPECIFICATION AND ANY CONTRIBUTION THERETO. IN NO EVENT WILL ANY AUTHOR OR DEVELOPER OF THIS MATERIAL OR ANY CONTRIBUTION THERETO BE LIABLE TO ANY OTHER PARTY FOR THE COST OF PROCURING SUBSTITUTE GOODS OR SERVICES, LOST PROFITS, LOSS OF USE, LOSS OF DATA, OR ANY INCIDENTAL, CONSEQUENTIAL, DIRECT, INDIRECT, OR SPECIAL DAMAGES WHETHER UNDER CONTRACT, TORT, WARRANTY, OR OTHERWISE, ARISING IN ANY WAY OUT OF THIS OR ANY OTHER AGREEMENT RELATING TO THIS DOCUMENT, WHETHER OR NOT SUCH PARTY HAD ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES.
  • Onetouch 4.0 Sanned Documents

    Onetouch 4.0 Sanned Documents

    TO: MSPM Distribution FROM: J. H. Saltzer SUBJECT: 88.3.02 DATE: 02/05/68 This revision of BB.3.02 is because 1. The ASCII standard character set has been approved. References are altered accordingly. 2. The latest proposed ASCII standard card code has been revised slightly. Since the Multics standard card code matches the ASCII standard wherever convenient# 88.3.02 is changed. Codes for the grave accent# left and right brace, and tilde are affected. 3. One misprint has been corrected; the code for capita 1 11 S" is changed. MULTICS SYSTEM-PROGRAMMERS' MANUAL SECTION BB.3.02 PAGE 1 Published: 02/05/68; (Supersedes: BB.3.02; 03/30/67; BC.2.06; 11/10/66) Identification Multics standard card punch codes and Relation between ASCII and EBCDIC J • H • Sa 1 tze r Purpose This section defines standard card punch codes to be used in representing ASCII characters for use with Multics. Since the card punch codes are based on the punch codes defined for the IBM EBCDIC standard, automatically a correspondence between the EBCDIC and ASCII character sets is also defined. Note The Multics standard card punch codes described in this section are DQ! identical to the currently proposed ASCII punched card code. The proposed ASCII standard code is not supported by any currently available punched card equipment; until such support exists it is not a practical standard for Multics work. The Multics standard card punch code described here is based on widely available card handling equipment used with IBM System/360 computers. The six characters for which the Multics standard card code differs with the ASCII card code are noted in the table below.
  • LG Programmer’S Reference Manual

    LG Programmer’S Reference Manual

    LG Programmer’s Reference Manual Line Matrix Series Printers Trademark Acknowledgements ANSI is a registered trademark of American National Standards Institute, Inc. Code V is a trademark of Quality Micro Systems. Chatillon is a trademark of John Chatillon & Sons, Inc. Ethernet is a trademark of Xerox Corporation. IBM is a registered trademark of International Business Machines Corporation. IGP is a registered trademark of Printronix, LLC. Intelligent Printer Data Stream and IPDS are trademarks of International Business Machines Corporation. LinePrinter Plus is a registered trademark of Printronix, LLC. MS-DOS is a registered trademark of Microsoft Corporation. PC-DOS is a trademark of International Business Machines Corporation. PGL is a registered trademark of Printronix, LLC. PrintNet is a registered trademark of Printronix, LLC. Printronix is a registered trademark of Printronix, LLC. PSA is a trademark of Printronix, LLC. QMS is a registered trademark of Quality Micro Systems. RibbonMinder is a trademark of Printronix, LLC. Torx is a registered trademark of Camcar/Textron Inc. Utica is a registered trademark of Cooper Power Tools. Printronix, LLC. makes no representations or warranties of any kind regarding this material, including, but not limited to, implied warranties of merchantability and fitness for a particular purpose. Printronix, LLC. shall not be held responsible for errors contained herein or any omissions from this material or for any damages, whether direct, indirect, incidental or consequential, in connection with the furnishing, distribution, performance or use of this material. The information in this manual is subject to change without notice. This document contains proprietary information protected by copyright. No part of this document may be reproduced, copied, translated or incorporated in any other material in any form or by any means, whether manual, graphic, electronic, mechanical or otherwise, without the prior written consent of Printronix, LLC.
  • IPDS and SCS Technical Reference

    IPDS and SCS Technical Reference

    IBMNetworkPrinters12,17,24 IBMInfoprint20,21,32,40,45 IBM Infoprint 70 IBM IPDS and SCS Technical Reference S544-5312-07 IBMNetworkPrinters12,17,24 IBMInfoprint20,21,32,40,45 IBM Infoprint 70 IBM IPDS and SCS Technical Reference S544-5312-07 Note Before using this information and the product it supports, be sure to read the general information under “Notices” on page xiii. Eighth Edition (April 2000) This version obsoletes S544-5312-06. Requests for IBM publications should be made to your IBM representative or to the IBM branch office serving your locality. If you request publications from the address given below, your order will be delayed because publications are not stocked there. Many of the IBM Printing Systems Company publications are available from the web page listed below. Internet Visit our home page at: http://www.ibm.com/printers A Reader’s Comment Form is provided at the back of this publication. You may also send comments by fax to 1-800-524-1519, by e-mail to [email protected], or by regular mail to: IBM Printing Systems Department H7FE Building 003G Information Development PO Box 1900 Boulder CO USA 80301-9191 IBM may use or distribute whatever information you supply in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 1996, 2000. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Tables ...............ix Chapter 4. Device Control Command Set................23 Notices ..............xiii Acknowledgement Reply ..........23 Trademarks ..............xiii Activate Resource ............25 Resource ID example with RIDF = GRID .
  • Mountbatten Pro User Guide

    Mountbatten Pro User Guide

    User Guide Mountbatten Pro Revision 2 © Harpo Sp. z o. o. ul. 27 Grudnia 7, 61-737 Poznań, Poland www.mountbattenbrailler.com Thank you for purchasing a Mountbatten Pro. Since 1990, the Mountbatten range of Braille Writers has been offering expanded Braille writing opportunities to people all around the world. Mountbatten Braille Writers are in use in countries all over the world, bringing and supporting Braille literacy in many languages. To get the most from your new MB Pro, please read the first section, Welcome, and follow it with the second section, Exploring the MB Pro. After that, you can skip to the sections you want to read first, because you will have the most important basic information. News, resources, regular updates to this User Guide and a range of support material can be obtained from the Mountbatten website: www.mountbattenbrailler.com This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. Contents Welcome................................................................................................................................................................ 1 Reading your User Guide.................................................................................................................................. 1 Very Important!.................................................................................................................................................
  • Control Characters in ASCII and Unicode

    Control Characters in ASCII and Unicode

    Control characters in ASCII and Unicode Tens of odd control characters appear in ASCII charts. The same characters have found their way to Unicode as well. CR, LF, ESC, CAN... what are all these codes for? Should I care about them? This is an in-depth look into control characters in ASCII and its descendants, including Unicode, ANSI and ISO standards. When ASCII first appeared in the 1960s, control characters were an essential part of the new character set. Since then, many new character sets and standards have been published. Computing is not the same either. What happened to the control characters? Are they still used and if yes, for what? This article looks back at the history of character sets while keeping an eye on modern use. The information is based on a number of standards released by ANSI, ISO, ECMA and The Unicode Consortium, as well as industry practice. In many cases, the standards define one use for a character, but common practice is different. Some characters are used contrary to the standards. In addition, certain characters were originally defined in an ambiguous or loose way, which has resulted in confusion in their use. Contents Groups of control characters Control characters in standards o ASCII control characters o C1 control characters o ISO 8859 special characters NBSP and SHY o Control characters in Unicode Control characters in modern applications Character list o ASCII o C1 o ISO 8859 Categories Translations Character index Sources This article starts by looking at the history of control characters in standards. We then move to modern times.
  • International Character Code Standard for the BE2

    International Character Code Standard for the BE2

    °, , CMU-ITC-87-091 International Character Code Standard for the BE2 June 18, 1987 Tomas Centerlind Information Technology Center (ITC) Camegie Mellon University 1. Major problems with foreign languages All European languages have a set of unique characters, even Great Britain with their Pound sign. Most of these characters are static and do not change if they are in the end or in the middle of the word. The Greek sigma sign however is an example of a character that changes look depending on the position. If we move on to the non-Roman alphabets like Arabic, they have a more complex structure. A basic rule is that certain of the characters are written together if they follow each other but not otherwise. This complicates representation and requires look ahead. In addition to this many of the languages have leftwards or downwards writing. All together these properties makes it very difficult to integrate them with Roman languages. Lots of guidelines have to be established to solve these problems, and before any coding can be done a set of standards must be selected or defined. In this paper I intend to gather all that I can think of that must be considered before selecting standards. Only the basic level of the implementation will be designed, so therefore routines that for example display complex languages like Arabic must be written by the user. A basic method that dislpays Roman script correctly will be supported. 1. Standards 1.1 Existing standards Following is a list of currently existing and used standards. 1.1.1 ASCII, ISO646 The ASCII standard, that is in use ahnost anywhere, will probably have to rcmain as a basic part of the system, and without any doubt it must be possible to read and write ASCII coded documents in the foreseeable future.
  • International Register of Coded Character Sets to Be Used with Escape Sequences for Information Interchange in Data Processing

    International Register of Coded Character Sets to Be Used with Escape Sequences for Information Interchange in Data Processing

    INTERNATIONAL REGISTER OF CODED CHARACTER SETS TO BE USED WITH ESCAPE SEQUENCES 1 Introduction 1.1 General This document is the ISO International Register of Coded Character Sets To Be Used With Escape Sequences for information interchange in data processing. It is compiled in accordance with the provisions of ISO/IEC 2022, "Code Extension Technique" and of ISO 2375 "Procedure for Registration of Escape Sequences". This International Register contains coded character sets which have been registered in accordance with procedures given in ISO 2375. Its purpose is to identify widely used coded character sets and associate with each a unique escape sequence by means of which it can be designated according to ISO/IEC 2022 and ISO/IEC 4873. The publication of this International Register should promote compatibility in international information interchange and avoid duplication of effort in developing application-oriented coded character sets. Registration provides an identification for a coded character set but implies nothing about its status; it may or may not be part of a standard of an international, national or a corporate body. However, if such a standard is published subsequently to the registration, it would be appropriate for the escape sequence identifying the character set to be specified in the standard. If it is desired to register a set, application should be made to the Registration Authority through an appropriate Sponsoring Authority as specified in ISO 2375. Any character set can be a candidate for registration if it meets the requirements of ISO 2375. The Registration Authority ascertains that the proposals received are formally in accordance with this International Standard, technically in accordance with ISO/IEC 2022, and, where applicable, with ISO/IEC 646 and ISO/IEC 4873, and meet the presentation practice of the Registration Authority.
  • L2/98-354 Terminal Graphics for Unicode

    L2/98-354 Terminal Graphics for Unicode

    L2/98-354 TERMINAL GRAPHICS FOR UNICODE Frank da Cruz The Kermit Project Columbia University New York City USA [email protected] http://www.columbia.edu/kermit/ D R A F T # 4 Tue Nov 3 19:08:58 1998 THIS IS A PREFORMATTED PLAIN-TEXT ASCII DOCUMENT. IT IS DESIGNED TO BE VIEWED AS-IS IN A FIXED-PITCH FONT. ITS WIDEST LINE IS 79 COLUMNS. IT CONTAINS NO TABS. IF IT LOOKS MESSY TO YOU, PLEASE FEEL FREE TO PICK UP A CLEAN COPY OF THIS OR THE RELATED PROPOSALS BY ANONYMOUS FTP: HEX BYTE PICTURES FOR UNICODE (plain text) ftp://kermit.columbia.edu/kermit/ucsterminal/hex.txt ADDITIONAL CONTROL PICTURES FOR UNICODE (plain text) ftp://kermit.columbia.edu/kermit/ucsterminal/control.txt TERMINAL GRAPHICS FOR UNICODE (plain text) ftp://kermit.columbia.edu/kermit/ucsterminal/ucsterminal.txt Glyph Map (PDF, contributed by Michael Everson) ftp://kermit.columbia.edu/kermit/ucsterminal/terminal-emulation.pdf Clarification of SNI Glyphs (Microsoft Word 7.0) ftp://kermit.columbia.edu/kermit/ucsterminal/sni-charsets.doc Discussion (plain text) ftp://kermit.columbia.edu/kermit/ucsterminal/mail.txt (Note, the Exhibits are on paper and not available at the FTP site.) ABSTRACT A selection of terminal graphics characters is proposed for Unicode [24] and ISO 10646 [19] to allow Unicode-based terminal emulation software to display glyphs that are found on popular types of terminals but currently are not available in Unicode, and to exchange these characters with other Unicode-based applications. 1 CONTENTS 1. Introduction 2. Scope 3. Organization 4. (deleted) 5. 3270 Terminal Operator Status Indicators 6.