DOCSLIB.ORG

PTOCA Reference (Presentation Text Object Content Architecture

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Advanced Function Presentation Consortium Data Stream and Object Architectures Presentation Text Object Content Architecture Reference AFPC-0009-03 Note: Before using this information, read the information in “Notices” on page 171. AFPC-0009-03 Fourth Edition (March 2016) This edition applies to the Presentation Text Object Content Architecture (PTOCA). It is the first edition produced by the AFP Consortium™(AFPC™) and replaces and makes obsolete the previous edition, SC31-6803-02, published by the IBM® Corporation. This edition remains current until a new edition is published. Specific changes are indicated by a vertical bar to the left of the change. For a detailed list of the changes, see “Summary of Changes” on page ix. Internet Visit our home page: www.afpcinc.org Copyright © AFP Consortium 1997, 2016 ii Preface This book describes the functions and services associated with the Presentation Text Object Content Architecture (PTOCA) architecture. This book is a reference, not a tutorial. It complements individual product publications, but does not describe product implementations of the architecture. Who Should Read This Book This book is for systems programmers and other developers who need such information to develop or adapt a product or program to interoperate with other presentation products. Copyright © AFP Consortium 1997, 2016 iii AFP Consortium AFP Consortium (AFPC) The Advanced Function Presentation™(AFP™) architectures began as the strategic, general purpose document and information presentation architecture for the IBM Corporation. The first specifications and products go back to 1984. Although all of the components of the architecture have grown over the years, the major concepts of object-driven structures, print integrity, resource management, and support for high print speeds were built in from the start. In the early twenty-first century, IBM saw the need to enable applications to create color output that is independent from the device used for printing and to preserve color consistency, quality, and fidelity of the printed material. This need resulted in the formation, in October 2004, of the AFP Color Consortium™ (AFPCC™). The goal was to extend the object architectures with support for full-color devices including support for comprehensive color management. The idea of doing this via a consortium consisting of the primary AFP architecture users was to build synergism with partners from across the relevant industries, such as hardware manufacturers that produce printers as well as software vendors of composition, work flow, viewer, and transform tools. Quickly more than 30 members came together in regular meetings and work group sessions to create the AFP Color Management Object Content Architecture™ (CMOCA™). A major milestone was reached by the AFP Color Consortium with the initial official release of the CMOCA specification in May 2006. Since the cooperation between the members of the AFP Color Consortium turned out to be very effective and valuable, it was decided to broaden the scope of the consortium efforts and IBM soon announced its plans to open up the complete scope of the AFP architecture to the consortium. In June 2007, IBM's role as founding member of the consortium was transferred to the InfoPrint® Solutions Company, an IBM/Ricoh® joint venture. In February 2009, the consortium was incorporated under a new set of bylaws with tiered membership and shared governance resulting in the creation of a formal open standards body called the AFP Consortium (AFPC). Ownership of and responsibility for the AFP architectures was transferred at that time to the AFP Consortium. How to Use This Book This book is divided into six chapters, three appendixes, and a glossary. • Chapter 1, “Overview of Presentation Architecture” introduces the AFP presentation architectures and positions Presentation Text Object Content Architecture as a strategic object content architecture. • Chapter 2, “Introduction to PTOCA” briefly states the purpose and function of PTOCA. • Chapter 3, “Overview of PTOCA” introduces the concepts that form the basis of PTOCA and provides a brief description of the data structures. • Chapter 4, “Data Structures in PTOCA” provides the detailed syntax, semantics, and pragmatics of the data structures found in PTOCA. • Chapter 5, “Exception Handling in PTOCA” describes how exceptions are handled in PTOCA and lists the exception codes. • Chapter 6, “Compliance with PTOCA” describes how products may be valid generators or receivers of PTOCA. • Appendix A, “MO:DCA Environment” describes the Presentation Text object in the context of a MO:DCA™ data stream. • Appendix B, “IPDS Environment” describes the Presentation Text object in the context of an IPDS™ data stream. • Appendix C, “PTOCA Retired Functions” describes the retired PTOCA functions. • The “Glossary” on page 173 defines some of the terms used within this book. iv PTOCA Reference How to Use This Book How to Read the Syntax Diagrams Throughout this book, syntax is described using the structure defined below. Six basic data types are used in the syntax descriptions: CODE Architected constant CHAR Character string, which may consist of any code points BITS Bit string UBIN Unsigned binary SBIN Signed binary UNDF Undefined type Syntax for PTOCA is shown in tables like the following: Offset Type Name Range Meaning M/O Def Ind The field's offset, data Name of field if Range of Meaning or purpose of type, or both applicable valid values if the data element applicable M/O M means mandatory. O means optional. Def Y means that a default value is defined for the field. N means that there is no default value defined for the field. Ind Y means that the field defaults to a hierarchical default value when the default indicator (X'F..F') is present. N means that the default indicator semantic is not valid for the field. The following is an example of PTOCA syntax for the Begin Line (BLN) control sequence as it appears in this book: Offset Type Name Range Meaning M/O Def Ind 0 CODE PREFIX X'2B' Control sequence Prefix M N N 1 CODE CLASS X'D3' Control sequence class M N N 2 UBIN LENGTH 2 Control sequence length M N N 3 CODE TYPE X'D8' – X'D9' Control sequence M N N function type Please refer to “Control Sequence Detailed Descriptions” on page 45 for a more detailed description of PTOCA syntax. PTOCA Reference v Related Publications Related Publications Several other publications can help you understand the architecture concepts described in this book. AFP Consortium publications and a few other AFP publications are available on the AFP Consortium web site, http://www.afpcinc.org. Table 1. AFP Consortium Architecture References AFP Architecture Publication Book Identification AFP Programming Guide and Line Data Reference S544-3884 (IBM) Bar Code Object Content Architecture™ Reference AFPC-0005 Color Management Object Content Architecture Reference AFPC-0006 Font Object Content Architecture Reference AFPC-0007 Graphics Object Content Architecture for Advanced Function Presentation Reference AFPC-0008 Image Object Content Architecture Reference AFPC-0003 Intelligent Printer Data Stream™ (IPDS) Reference AFPC-0001 Metadata Object Content Architecture Reference AFPC-0013 Mixed Object Document Content Architecture™ (MO:DCA) Reference AFPC-0004 Presentation Text Object Content Architecture Reference AFPC-0009 Table 2. Additional AFP Consortium Documentation AFPC Publication Book Identification AFP Color Management Architecture™ (ACMA™) AFPC-0015 AFPC Company Abbreviation Registry AFPC-0012 AFPC Font Typeface Registry AFPC-0016 BCOCA™ Frequently Asked Questions AFPC-0011 MO:DCA-L:The OS/2 PM Metafile (.met) Format AFPC-0014 Presentation Object Subsets for AFP AFPC-0002 Recommended IPDS Values for Object Container Versions AFPC-0017 Table 3. AFP Font-Related Documentation Publication Book Identification Character Data Representation Architecture Reference and Registry; SC09-2190 (IBM) please refer to the online version for the most current information: http://www-01.ibm.com/software/globalization/cdra/index.html Font Summary for AFP Font Collection S544-5633 (IBM) How To Use TrueType and OpenType Fonts in an AFP System G544-5876 (IBM) Technical Reference for Code Pages S544-3802 (IBM) vi PTOCA Reference Related Publications Table 4. UP3I™ Architecture Documentation UP3I Publication Book Identification Universal Printer Pre- and Post-Processing Interface (UP3I) Specification; Version 1.20 please refer to the online version: http://www.afpcinc.org PTOCA Reference vii Related Publications viii PTOCA Reference Summary of Changes Summary of Changes This fourth edition of the PTOCA Reference contains the following changes: • The description of font usage in PTOCA has been expanded to include TrueType/Open Type fonts. • The definition of control sequences to support the processing of complex scripts: – Glyph Advance Run (GAR) – Glyph ID Run (GIR) – Glyph Layout Control (GLC) – Glyph Offset Run (GOR) – Unicode Complex Text (UCT) • The definition of a new PTOCA subset - PT4 - that consists of the PT3 subset plus the new control sequences listed above • The Precision byte in the Set Text Color control sequence has been retired; this is documented in a new PTOCA Migration Functions appendix • Editorial updates and clarifications • An updated glossary • Information about the AFP Consortium • IBM product-specific information has been removed (CCS, CPI, CUA, MO:DCA-P, SAA, etc.) • Style changes to make this book more consistent with other AFPC publications As stated in the
Recommended publications
  • International Language Environments Guide

    International Language Environments Guide

    International Language Environments Guide Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A. Part No: 806–6642–10 May, 2002 Copyright 2002 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, docs.sun.com, AnswerBook, AnswerBook2, Java, XView, ToolTalk, Solstice AdminTools, SunVideo and Solaris are trademarks, registered trademarks, or service marks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. SunOS, Solaris, X11, SPARC, UNIX, PostScript, OpenWindows, AnswerBook, SunExpress, SPARCprinter, JumpStart, Xlib The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry.
  • Development Production Line the Short Story

    Development Production Line the Short Story

    Development Production Line The Short Story Jene Jasper Copyright © 2007-2018 freedumbytes.dev.net (Free Dumb Bytes) Published 3 July 2018 4.0-beta Edition While every precaution has been taken in the preparation of this installation manual, the publisher and author assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein. This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License. To get an idea of the Development Production Line take a look at the following Application Integration overview and Maven vs SonarQube Quality Assurance reports comparison. 1. Operating System ......................................................................................................... 1 1.1. Windows ........................................................................................................... 1 1.1.1. Resources ................................................................................................ 1 1.1.2. Desktop .................................................................................................. 1 1.1.3. Explorer .................................................................................................. 1 1.1.4. Windows 7 Start Menu ................................................................................ 2 1.1.5. Task Manager replacement ........................................................................... 3 1.1.6. Resource Monitor .....................................................................................
  • Higher Quality 2D Text Rendering

    Higher Quality 2D Text Rendering

    Journal of Computer Graphics Techniques Vol. 2, No. 1, 2013 Higher Quality 2D Text Rendering http://jcgt.org Higher Quality 2D Text Rendering Nicolas P. Rougier INRIA No hinting Native hinting Auto hinting Vertical hinting Figure 1. When displaying text on low-resolution devices (DPI < 150), one typically has to decide if one wants to respect the pixel grid (e.g., Cleartype technology / Microsoft / native hinting) for crisp rendering or, to privilege glyph shapes (Quartz technology / Apple / no hinting) at the cost of blurring. There is, however, a third way that may combine the best of the two technologies (vertical hinting). Abstract Even though text is pervasive in most 3D applications, there is surprisingly no native sup- port for text rendering in OpenGL. To cope with this absence, Mark Kilgard introduced the use of texture fonts [Kilgard 1997]. This technique is well known and widely used and en- sures both good performances and a decent quality in most situations. However, the quality may degrade strongly in orthographic mode (screen space) due to pixelation effects at large sizes and to legibility problems at small sizes due to incorrect hinting and positioning of glyphs. In this paper, we consider font-texture rendering to develop methods to ensure the highest quality in orthographic mode. The method used allows for both the accurate render- ing and positioning of any glyph on the screen. While the method is compatible with complex shaping and/or layout (e.g., the Arabic alphabet), these specific cases are not studied in this article. 50 Journal of Computer Graphics Techniques Vol.
  • Proposal for Addition of Group Mark Symbol Introduction

    Proposal for Addition of Group Mark Symbol Introduction

    Proposal for addition of Group Mark symbol Ken Shirriff github.com/shirriff/groupmark Feb 14, 2015 Abstract The group mark symbol was part of the character set of important computers of the 1960s and 1970s, such as the IBM 705, 7070, 1401 and 1620. Books about these computers and manuals for them used the symbol to represent the group mark in running text. Unfortunately, this symbol does not exist in Unicode, making it difficult to write about technical details of these historical computers. Introduction The group mark was introduced in the 1950s as a separator character for I/O operations. In written text, the group mark is indicated by the symbol: . Unicode doesn't include this symbol, which is inconvenient when writing about the group mark or the character set of these computers. The group mark became part of IBM's Standard BCD Interchange Code (BCDIC) in 1962. [1, page 20 and figure 56]. This standard was used by the IBM 1401, 1440, 1410, 1460, 7010, 7040, and 7044 data processing systems [2]. The BCDIC standard provided consistent definitions of codes and the relation between these codes and printed symbols, including uniform graphics for publications.[2, page A-2]. Unicode can represent all the characters in BCDIC, except for the group mark. This proposal is for a Unicode code point for the group mark for use in running text with an associated glyph . This is orthogonal to the use of the group mark as a separator in data files. While the proposed group mark could be used in data files, that is not the focus of this proposal.
  • Accordance Fonts(November 2010)

    Accordance Fonts(November 2010)

    Accordance Fonts (November 2010) Contents Installing the Fonts . 2. OS X Font Display in Accordance and above . 2. Font Display in Other OS X Applications . 3. Converting to Unicode . 4. Other Font Tips . 4. Helena Greek Font . 5. Additional Character Positions for Helena . 5. Helena Greek Font . 6. Yehudit Hebrew Font . 7. Table of Hebrew Vowels and Other Characters . 7. Yehudit Hebrew Font . 8. Notes on Yehudit Keyboard . 9. Table of Diacritical Characters(not used in the Hebrew Bible) . 9. Table of Accents (Cantillation Marks, Te‘amim) — see notes at end . 9. Notes on the Accent Table . 1. 2 Peshitta Syriac Font . 1. 3 Characters in non-standard positions . 1. 3 Peshitta Syriac Font . 1. 4 Syriac vowels, other diacriticals, and punctuation: . 1. 5 Rosetta Transliteration Font . 1. 6 Character Positions for Rosetta: . 1. 6 Sylvanus Uncial/Coptic Font . 1. 8 Sylvanus Uncial Font . 1. 9 MSS Font for Manuscript Citation . 2. 1 MSS Manuscript Font . 2. 2 Salaam Arabic Font . 2. 4 Characters in non-standard positions . 2. 4 Salaam Arabic Font . 2. 5 Arabic vowels and other diacriticals: . 2. 6 Page 1 Accordance Fonts OS X font Seven fonts are supplied for use with Accordance: Helena for Greek, Yehudit for Hebrew, Peshitta for Syriac, Rosetta for files transliteration characters, Sylvanus for uncial manuscripts, and Salaam for Arabic . An additional MSS font is used for manuscript citations . Once installed, the fonts are also available to any other program such as a word processor . These fonts each include special accents and other characters which occur in various overstrike positions for different characters .
  • Font Features for Scheherazade

    Font Features for Scheherazade

    Font Features for Scheherazade The Scheherazade font includes a number of optional features that provide alternative rendering that might be preferable for use in some contexts. The chart below enumerates the details of these features. Whether these features are available to users will depend on both the application and the rendering technology (Graphite or OpenType) being used. Most features are available in both Graphite and OpenType, though there may be minor differences in their implementation. In LibreOffice 3.4.2+ (http://www.libreoffice.org/download/) or OpenOffice 3.2+ (http://www.openoffice.org/download/) the features are available only when Graphite rendering is enabled (the default). Features can be turned on by choosing the font (i.e., Scheherazade), followed by a colon, followed by the feature ID, and then followed by the feature setting. So, for example, if the “Kurdish-style Heh” is desired, the font selection would be “Scheherazade:cv48=3”. If you wish to apply two (or more) features, you can separate them with an “&”. Thus, “Scheherazade:cv48=3&cv44=1” would apply the “Kurdish-style Heh” plus the “Sindhi-style Meem” feature. In Mozilla Firefox, with either Graphite or OpenType rendering, features can be accessed using the appropriate CSS markup. A description of how to use the font features in Mozilla Firefox can be found here: http://scripts.sil.org/cms/scripts/page.php?site_id=projects&item_id=graphite_firefox#cf8a0574 (the technique described there works for both Graphite and OpenType). Ideally the selection of these font features is done in application programs, but many applications do not yet support this functionality.
  • Javatm Internationalization Roadmap

    Javatm Internationalization Roadmap

    JavaTM Internationalization Roadmap by Brian Beck – [email protected] Stuart Gill – [email protected] Norbert Lindenberg – [email protected] John O’Conner – [email protected] Sun Microsystems Inc. Introduction The Java 2 platform as available today provides a strong foundation for the development of internationalized and multilingual applications. The functionality it provides covers all the core areas of internationalization: • It uses Unicode 2.1 as its built-in character data type. • The Locale class lets applications identify locales, allowing for truly multilingual applications. • The ResourceBundle class provides the foundation for localization, including localization for multiple locales in a single application container. • The Date, Calendar, and TimeZone classes provide the basis for time handling around the globe. • The String and Character classes as well as the java.text package contain rich functionality for text processing, formatting, and parsing. • Text stream input and output classes support converting text between Unicode and other character encodings. • Keyboard handling and the input method framework allow for text input in many languages. • The Java 2D™ system supports text rendering for many of the major languages, including bidirectional text handling for Arabic and Hebrew. • The text components in the Swing user interface toolkit provide plug-and-play text editing functionality that takes full advantage of the input method framework and the 2D rendering system. • Component orientation support lets applications switch their user interfaces between left- to-right and right-to-left layouts. To date, most of our internationalization support has been focused on European, Middle Eastern, and Far East Asian locales. Those locales are now reasonably well supported so we have begun to turn our attention to the locales of South and Southeast Asia.
  • INDIAN LANGUAGE SUPPORT in GNOME-TERMINAL B.Tech Information Technology

    INDIAN LANGUAGE SUPPORT in GNOME-TERMINAL B.Tech Information Technology

    INDIAN LANGUAGE SUPPORT IN GNOME-TERMINAL A Project Report Submitted by Kulkarni Swapnil 110708035 Kulkarni Mihir 110708033 DigeSourabh 110708020 in partial fulfilment for the award of the degree of B.Tech Information Technology Under the guidance of Prof. Abhijit A.M. College of Engineering, Pune DEPARTMENT OF COMPUTER ENGINEERING AND INFORMATION TECHNOLOGY, COLLEGE OF ENGINEERING, PUNE-5 May, 2011 Acknowledgements We would sincerely like to acknowledge the following people who played a very im- portant role in the success of the project. They guided us from time to time and helped us whenever we were stuck at any point. We deeply appreciate their commitment and dedication towards the spread of Open Source and the Free Software Movement in general. Prof. Abhijit A.M. - Our guide and mentor throughout the project. We thank him for giving us the opportunity to work with him and in particular on this project and for spending invaluable time in critical moments of our project. Praveen Arimbrathodiyil, Pravin Satpute, Santhosh Thottingal - For provid- ing timely help and guidance. We would also like to thank Dr. Jibi Abraham [HOD Computer Engg. and Information Technology, COEP] and all the staff of Computer Engg. and Information Technology Department. Last but not the least, we would like to thank the whole FOSS community and the people involved in Indic Langauge Computing throughtout the world without whom this project would not have been a reality. DEPARTMENT OF COMPUTER ENGINEERING AND INFORMATION TECHNOLOGY, COLLEGE OF ENGINEERING, PUNE CERTIFICATE Certified that this project, titled “INDIAN LANGUAGE SUPPORT IN GNOME- TERMINAL” has been successfully completed by Kulkarni Swapnil 110708035 Kulkarni Mihir 110708033 DigeSourabh 110708020 and is approved for the partial fulfilment of the requirements for the degree of “B.Tech.
  • Middle East-I 9 Modern and Liturgical Scripts

    Middle East-I 9 Modern and Liturgical Scripts

    The Unicode® Standard Version 13.0 – Core Specification To learn about the latest version of the Unicode Standard, see http://www.unicode.org/versions/latest/. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and the publisher was aware of a trade- mark claim, the designations have been printed with initial capital letters or in all capitals. Unicode and the Unicode Logo are registered trademarks of Unicode, Inc., in the United States and other countries. The authors and publisher have taken care in the preparation of this specification, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. The Unicode Character Database and other files are provided as-is by Unicode, Inc. No claims are made as to fitness for any particular purpose. No warranties of any kind are expressed or implied. The recipient agrees to determine applicability of information provided. © 2020 Unicode, Inc. All rights reserved. This publication is protected by copyright, and permission must be obtained from the publisher prior to any prohibited reproduction. For information regarding permissions, inquire at http://www.unicode.org/reporting.html. For information about the Unicode terms of use, please see http://www.unicode.org/copyright.html. The Unicode Standard / the Unicode Consortium; edited by the Unicode Consortium. — Version 13.0. Includes index. ISBN 978-1-936213-26-9 (http://www.unicode.org/versions/Unicode13.0.0/) 1.
  • Complex Text Layout Language Support in the Solaris Operating Environment

    Complex Text Layout Language Support in the Solaris Operating Environment

    Complex Text Layout Language Support in the Solaris Operating Environment Sun Microsystems, Inc. 901 San Antonio Road Palo Alto, CA 94303-4900 U.S.A. Part Number 806-5583 May 2000 Copyright 2000 Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, California 94303-4900 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, docs.sun.com, AnswerBook, AnswerBook2, and Solaris are trademarks, registered trademarks, or service marks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The OPEN LOOK and SunTM Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements.
  • Harmattan Font Features Guide

    Harmattan Font Features Guide

    Harmaan Features The Harmaan font includes a number of oponal features that provide alternave rendering that might be preferable for use in some contexts. The chart below enumerates the details of these features. Whether these features are available to users will depend on both the applicaon and the rendering technology (Graphite or OpenType) being used. Most features are available in both Graphite and OpenType, though there may be minor differences in their implementaon. Features When Harmaan is used in applicaons that support Graphite or OpenType, and that provide an appropriate user interface, various user-controllable font features are available allowing access to alternavely-designed glyphs. The table below gives a visual representaon of the featured character glyphs in the font. Note that within each feature the top-most value is the de- fault. The other lines show the first alternate and, if available, the second or third alternates. List of Graphite features and OpenType Character Variants Feature Name Feature ID Feature Setting (top-most Character Shapes Implementation in each section is default) Notes1 Alef diacritic placement cv02 0=Standard G,O,T (U+0623, U+0625, U+0627, U+064E, أإاَ ِاأإل ٔالإ (U+0650, U+0654, U+0655 1=Hamza touching أإاَ ِاأإل ٔالإ 2=Touching أإَاِاأإل ٔالإ Jeem/Hah cv08 0=Standard G,O,T (U+062C, U+062D, U+062E, U+0682, U+0683, U+0684, U+0685, U+0686, ج ججج ح ححح خ خخخ ڂ ڂڂڂ ڃ ڃڃڃ ڄ ڄڄڄ څ څڅڅ چ ,U+06BF, U+0757, U+0758, U+08A2 چچچ ڿ ڿڿڿ U+08C1, U+08C5, U+08C6) ࣆࣆࣆ ࣆ ࣅࣅࣅ ࣅ ࣁࣁࣁ ࣁ ࢢࢢࢢ ࢢ ݘݘݘ ݘ ݗݗݗ ݗ 1=Handwritten ج ججج ح ححح خ خخخ ڂ ڂڂڂ ڃ ڃڃڃ ڄ ڄڄڄ څ څڅڅ چ چچچ ڿ ڿڿڿ ࣆࣆࣆ ࣆ ࣅࣅࣅ ࣅ ࣁࣁࣁ ࣁ ࢢࢢࢢ ࢢ ݘݘݘ ݘ ݗݗݗ ݗ 1 Implementation Notes: G=Implemented in Graphite; O=Implemented in OpenType; T=Implemented in TypeTuner (command line version: http://scripts.sil.org/TypeTuner and web-based version: http://scripts.sil.org/ttw) .
  • The Unicode Standard, Version 3.0, Issued by the Unicode Consor- Tium and Published by Addison-Wesley

    The Unicode Standard, Version 3.0, Issued by the Unicode Consor- Tium and Published by Addison-Wesley

    The Unicode Standard Version 3.0 The Unicode Consortium ADDISON–WESLEY An Imprint of Addison Wesley Longman, Inc. Reading, Massachusetts · Harlow, England · Menlo Park, California Berkeley, California · Don Mills, Ontario · Sydney Bonn · Amsterdam · Tokyo · Mexico City Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and Addison-Wesley was aware of a trademark claim, the designations have been printed in initial capital letters. However, not all words in initial capital letters are trademark designations. The authors and publisher have taken care in preparation of this book, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. The Unicode Character Database and other files are provided as-is by Unicode®, Inc. No claims are made as to fitness for any particular purpose. No warranties of any kind are expressed or implied. The recipient agrees to determine applicability of information provided. If these files have been purchased on computer-readable media, the sole remedy for any claim will be exchange of defective media within ninety days of receipt. Dai Kan-Wa Jiten used as the source of reference Kanji codes was written by Tetsuji Morohashi and published by Taishukan Shoten. ISBN 0-201-61633-5 Copyright © 1991-2000 by Unicode, Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or other- wise, without the prior written permission of the publisher or Unicode, Inc.