Rainer's DHTML Library

Total Page:16

File Type:pdf, Size:1020Kb

Rainer's DHTML Library · ©2002 Rainer Su . All rights reserved . Introduction To CSS2 CSS Cascading Style Sheet () (Linking to a Style Sheet) .cssHTMLlink <head> <title></title> <link rel=stylesheet href="http://www.dhtmlet.com/dhtmlet.css" type="text/css"> </head> XML <? xml-stylesheet type="text/css" href="http://www.dhtmlet.com/dhtmlet.css" ?> (Embedding a Style Block) HTML<HTML><BODY><STYLE>...</STYLE> <html> <head> <title></title> <style type="text/css"> <!-- body {font: 10pt "Arial"} h1 {font: 15pt/17pt "Arial"; font-weight: bold; color: maroon} h2 {font: 13pt/15pt "Arial"; font-weight: bold; color: blue} p {font: 10pt/12pt "Arial"; color: black} --> </style> </head> <body> styletype"text/css" (Inline Styles) style <p style="margin-left: 0.5in; margin-right:0.5in"><p> (CSS Syntax) Selector { property: value } Selector -- property : value -- (:)(;) (The ' Inherit ' Value) Inherit Introduction To This Book Rainer's DHTML Library CSS2.0 ( Properties)( At-Rules)( Pseudo-Classes)( Pseudo-Elements)( Declarations)( Units)( Selectors C CSS2.0 Internet Explorer Netscape —— Internet Explorer (Dynamic Properties)(Filters)(Behaviors) HTML(ObjectElement)HTML(Attributes)(Properties) http://www.rainersu.com [email protected] End User License Agreement """""""" http://www.rainersu.com [email protected] www.rainersu.com (Rainer Su) 1996.07-2000.03 (CAOSC) 2000.03-2000.08 (www.chineseall.com) 2000.09-2001.05 (www.rongshu.com) UI 2001.05-2002.04 (Erry) 2002.04-? (Bertelsmann) () [email protected] www.rainersu.com - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - © (Rainer Su)2002 | [email protected] - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - fontCSS1/CSS2 IE4+ NS4+ font : font-style || font-variant || font-weight || font-size || line-height || font- family font : caption | icon | menu | message-box | small-caption | status-bar font-style :� CSS1 font-style font-variant font-variant :� CSS1 font-weight font-weight :� CSS1 font-size :� CSS1 font-size line-height :� CSS1 line-height font-family font-family :� CSS1 caption :� CSS2 () icon :� CSS2 menu :� CSS2 message-box :� CSS2 small-caption :� CSS2 status-bar :� CSS2 normal normal normal medium normal "Times New Roman" @font-face font p { font: italic small-caps 600 12pts/18pts ; } p { font: italic small-caps 600 12pts/150% Courier; } p { font: italic small-caps 600 12pts/1.5 Courier; } p { font: italic small-caps 600 12pts/18pts Courier; } p { font: /18pts serif; } p { font: oblique 100 24pts; } H1 { font: 15pt/17pt bold "Arial" normal } colorCSS1 IE4+ NS4+ color : color color :� color RGB currentStyle color div {color: #345456; } div { color: rgb(100,14,200); } div {color: menu; } div {color: red; } font-familyCSS1 IE4+ NS4+ font-family : name font-family :ncursive | fantasy | monospace | serif | sans-serif name :� fantasy "Times New Roman" @font-face currentStyle fontFamily div.fixedwidth { font-family: Courier, "Courier New", monospace } font-sizeCSS1 IE4+ NS4+ font-size : xx-small | x-small | small | medium | large | x-large | xx-large | larger | smaller | length xx-small :� x-small :� small :� medium :� large :� x-large :� xx-large :� larger :� em smaller :� em | length :� currentStyle fontSize p { font-style: normal; } p { font-size: 12px; } p { font-size: 20%; } font-size-adjustCSS2 font-size-adjust : none | number none :� number :� fontSizeAdjust p { font-family: arial, courier; font-size-adjust: none; } p { font-family: verdana, courier; font-size-adjust: .56; } font-stretchCSS2 font-stretch : normal | narrower | wider | ultra-condensed | extra-condensed | condensed | semi-condensed | semi-expanded | expanded | extra-expanded | ultra-expanded normal :� narrower :� wider :� fontStretch p { font-stretch: wider; } p { font-stretch: ultra-expanded; } font-styleCSS1 IE4+ NS4+ font-style : normal | italic | oblique normal :� italic :� oblique oblique :� IE Internet currentStyle fontStyle p { font-style: normal; } p { font-style: italic; } p { font-style: oblique; } font-weightCSS1 IE4+ NS4+ font-weight : normal | bold | bolder | lighter | 100 | 200 | 300 | 400 | 500 | 600 | 700 | 800 | 900 normal :� 400 bold :� 700 b bolder :� normal > lighter :� normal > 100 :� 200 100 300 200 :� 200 400 300 :� 400 :� normal 400 600 500 :� 500 700 600 :� 700 :� bold 700 900 800 :� 900 :� 800 IE4.0 normal bold currentStyle fontWeight span { font-weight:800; } text-decorationCSS1 IE4+ NS4+ text-decoration : none || underline || blink || overline || line-through none :� blink :� underline :� line-through :� overline :� href a u ins underline strike s del line-through none text-decoration: underline overline blink none text- decoration: none ( img )(<EM></EM>) body none a a IE4+ overline blink blink currentStyle textDecoration div { text-decoration : underline; } div { text-decoration : underline overline; } text-underline-positionIE5.5+ text-underline-position : below | above below :� above :� text-decoration currentStyle textUnderlinePosition p { text-underline-position: above; text-decoration: underline; } text-shadowCSS2 text-shadow : color || length || length || opacity color :� length :� length :� length 0 opacity :� :first-letter :first-line textShadow p { text-shadow: 0px 0px 20px yellow, 0px 0px 10px orange, red 5px -5px; } p:first-letter { font-size: 36px; color: red; text-shadow: red 0px 0px 5px;} font-variantCSS1 IE4+ NS6+ font-variant : normal | small-caps normal :� small-caps :� IE4.0 small-caps currentStyle fontVariant span { font-variant: small-caps; } text-transformCSS1 IE4+ NS4+ text-transform : none | capitalize | uppercase | lowercase none :� capitalize :� uppercase :� lowercase :� currentStyle textTransform div { text-transform : uppercase; } line-heightCSS1 IE4+ NS4+ line-height : normal | length normal :� | length :� currentStyle lineHeight div {line-height:6px; } div {line-height:10.5; } letter-spacingCSS1 IE4+ NS6+ letter-spacing : normal | length normal :� length :� currentStyle letterSpacing div {letter-spacing:6px; } div {letter-spacing:0.5pt; } word-spacingCSS1 IE6+ NS6+ word-spacing : normal | length normal :� length :� IE4+MACIE6 currentStyle wordSpacing div { word-spacing : 10; } div { word-spacing : 10px; } text-indentCSS1 IE4+ NS4+ text-indent : length | length :� 0 ( br ) currentStyle textIndent DIV { text-indent:2cm } .click1 { text-indent:50% } .click2 { text-indent: } text-overflowIE6+ text-overflow : clip | ellipsis clip :� (...) ellipsis :� (...) (...) ellipsis white-space nowrap () ellipsis overflow hidden overflow scroll auto DHTML currentStyle textOverflow div { overflow: hidden; text-overflow:ellipsis; } vertical-alignCSS1/CSS2 IE4+ NS4+ vertical-align : auto | baseline | sub | super | top | text-top | middle | bottom | text-bottom | length auto :� CSS1 layout-flow baseline :� CSS1 valign sub :� CSS1 super :� CSS1 top :� CSS1 valign text-top :� CSS1 valign middle :� CSS1 valign bottom :� CSS1 valign text-bottom :� CSS1 valign | 00% length :� CSS2 IE currentStyle auto baseline currentStyle verticalAlign td { vertical-align : middle; } text-alignCSS1 IE4+ text-align : left | right | center | justify left :� right :� center :� justify :� (block elements) div null currentStyle textAlign div { text-align : center; } layout-flowIE5.5+ layout-flow : horizontal | vertical-ideographic horizontal :� vertical-ideographic :� text-align vertical-align writing-mode currentStyle layoutFlow div { layout-flow : horizontal; } writing-modeIE5.5+ writing-mode : lr-tb | tb-rl lr-tb :� tb-rl :� --90 ---- text-align vertical-align BUTTON CAPTION INPUT INPUT type=button INPUT type=file INPUT type=password INPUT type=reset INPUT type=submit INPUT type=text ISINDEX OPTION TEXTAREA tb-rl tb-rl writing-mode writing-mode currentStyle writingMode div { writing-mode: tb-rl; } directionCSS2 IE5+ direction : ltr | rtl | inherit ltr :� rtl :� inherit :� dir ltr unicode-bidi embed bidi-override currentStyle direction div { direction: rtl; unicode-bidi: bidi-override; } unicode-bidiCSS2 IE5+ unicode-bidi : normal | bidi-override | embed normal :� bidi-override :� direction embed :� direction direction direction embed bidi-override Unicode -- currentStyle unicodeBidi div { direction: rtl; unicode-bidi: bidi-override; } word-breakIE5+ word-break : normal | break-all | keep-all normal :� break-all :� normal keep-all :� normal break-all currentStyle wordBreak div {word-break : break-all; } line-breakIE5+ line-break : normal | strict normal :� strict :� currentStyle lineBreak div { line-break : strict; } white-spaceCSS1 IE5.5+ NS4+ white-space : normal | pre | nowrap normal :� IE6+ !DOCTYPE standards-compliant mode pre :� !DOCTYPE standards-compliant mode normal pre nowrap :� br noWrap TABHTML normal (DOM)IE currentStyle whiteSpace p { white-space: nowrap; } word-wrapIE5.5+ word-wrap : normal | break-word normal :� break-word :� ( word-break ) height currentStyle wordWrap div { word-wrap: break-word; word-break: break-all; } text-autospaceIE5+ text-autospace : none | ideograph-alpha|ideograph-numeric | ideograph- parenthesis | ideograph-space none :� (Latin-basedGreekCyrillicArabicHebrew ideograph-alpha :� ) ideograph-numeric :� ideograph-parenthesis :� () ideograph-space :� currentStyle textAutospace div {text-autospace: ideograph-alpha; } text-kashida-spaceIE5.5+ text-kashida-space : length | inherit length :� kashida100%kashida0% inherit :� 0% Kashida Kashida text-justify auto distribute kashida currentStyle textKashidaSpace div { text-kashida-space : 50%;text-justify: kashida; } text-justifyIE5+ text-justify : auto | distribute
Recommended publications
  • Cyinpenc.Pdf
    1 The Cyrillic codepages There are several widely used Cyrillic codepages. Currently, we define here the following codepages: • cp 866 is the standard MS-DOS Russian codepage. There are also several codepages in use, which are very similar to cp 866. These are: so-called \Cyrillic Alternative codepage" (or Alternative Variant of cp 866), Modified Alternative Variant, New Alternative Variant, and experimental Tatarian codepage. The differences take place in the range 0xf2{0xfe. All these `Alternative' codepages are also supported. • cp 855 is the standard MS-DOS Cyrillic codepage. • cp 1251 is the standard MS Windows Cyrillic codepage. • pt 154 is a Windows Cyrillic Asian codepage developed in ParaType. It is a variant of Windows Cyrillic codepage. • koi8-r is a standard codepage widely used in UNIX-like systems for Russian language support. It is specified in RFC 1489. The situation with koi8-r is somewhat similar to the one with cp 866: there are also several similar codepages in use, which coincide with koi8-r for all Russian letters, but add some other Cyrillic letters. These codepages include: koi8-u (it is a variant of the koi8-r codepage with some Ukrainian letters added), koi8-ru (it is described in a draft RFC document specifying the widely used character set for mail and news exchange in the Ukrainian internet community as well as for presenting WWW information resources in the Ukrainian language), and ISO-IR-111 ECMA Cyrillic Code Page. All these codepages are supported also. • ISO 8859-5 Cyrillic codepage (also called ISO-IR-144). • Apple Macintosh Cyrillic (Microsoft cp 10007) codepage.
    [Show full text]
  • IDOL Keyview Viewing SDK 12.7 Programming Guide
    KeyView Software Version 12.7 Viewing SDK Programming Guide Document Release Date: October 2020 Software Release Date: October 2020 Viewing SDK Programming Guide Legal notices Copyright notice © Copyright 2016-2020 Micro Focus or one of its affiliates. The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice. Documentation updates The title page of this document contains the following identifying information: l Software Version number, which indicates the software version. l Document Release Date, which changes each time the document is updated. l Software Release Date, which indicates the release date of this version of the software. To check for updated documentation, visit https://www.microfocus.com/support-and-services/documentation/. Support Visit the MySupport portal to access contact information and details about the products, services, and support that Micro Focus offers. This portal also provides customer self-solve capabilities. It gives you a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by using the MySupport portal to: l Search for knowledge documents of interest l Access product documentation l View software vulnerability alerts l Enter into discussions with other software customers l Download software patches l Manage software licenses, downloads, and support contracts l Submit and track service requests l Contact customer support l View information about all services that Support offers Many areas of the portal require you to sign in.
    [Show full text]
  • Relationship to ISO/IEC 10646 C
    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.
    [Show full text]
  • Fonts & Encodings
    Fonts & Encodings Yannis Haralambous To cite this version: Yannis Haralambous. Fonts & Encodings. O’Reilly, 2007, 978-0-596-10242-5. hal-02112942 HAL Id: hal-02112942 https://hal.archives-ouvertes.fr/hal-02112942 Submitted on 27 Apr 2019 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. ,title.25934 Page iii Friday, September 7, 2007 10:44 AM Fonts & Encodings Yannis Haralambous Translated by P. Scott Horne Beijing • Cambridge • Farnham • Köln • Paris • Sebastopol • Taipei • Tokyo ,copyright.24847 Page iv Friday, September 7, 2007 10:32 AM Fonts & Encodings by Yannis Haralambous Copyright © 2007 O’Reilly Media, Inc. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (safari.oreilly.com). For more information, contact our corporate/institutional sales department: (800) 998-9938 or [email protected]. Printing History: September 2007: First Edition. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. Fonts & Encodings, the image of an axis deer, and related trade dress are trademarks of O’Reilly Media, Inc.
    [Show full text]
  • P2178r1
    Misc lexing and string handling improvements Document #: P2178R1 Date: 2020-07-14 Project: Programming Language C++ Audience: EWG, SG-16 Reply-to: Corentin Jabot <[email protected]> Abstract This Omnibus paper proposes a series of small improvements to the lexing of C++ and the forming of string handling, notably to clarify the behavior of Unicode encoded sources files, and to reduce implementation divergence. This paper intends to supersede N3463 [1] and P1854R0 [3] and proposes a resolution to several core issues. While some of these changes are unrelated, the intent of this paper’s authors and SG-16 is to rewrite the description of lexing using more accurate terminology. A wording will, therefore, be provided incorporating all the desired design changes. Updating both the design an the terminology lets us acknowledge and handle the subtilities of text which may not have been fully understood in a pre-Unicode world. The overarching goals are to reduce the divergence in implementations, the complexity of the mental model, and most importantly to make sure that the semantic of text elements is conserved through the different phases of compilation. Revisions R1 • Add a note about trailing whitespaces in raw string literals following a comment from the UK national body • Add a FAQ • Add some notes about BOM, ill-formed code units sequences, string concatenations. Format and goals of this proposal This proposal tries to establish a more or less exhaustive list of issues with lexing in C++. Some of these issues are too small to be worth the overhead cost of an individual paper, some may 1 require further exploration, many are intertwined.
    [Show full text]
  • The Stringenc Package
    The stringenc package Heiko Oberdiek∗ 2019/11/29 v1.12 Abstract This package provides \StringEncodingConvert for converting a string between different encodings. Both LATEX and plain TEX are supported. Contents 1 Documentation2 1.1 User interface..............................2 1.2 Supported encodings..........................3 2 Implementation4 2.1 Reload check and package identification...............4 2.2 Catcodes................................5 2.3 Tools...................................6 2.4 Encoding aliases............................ 17 2.5 Encoding files.............................. 20 2.5.1 UTF-32BE, UTF-32LE.................... 20 2.5.2 UTF-8.............................. 22 2.5.3 UTF-16LE........................... 27 2.5.4 PDFDocEncoding....................... 28 2.5.5 ISO-8859-1........................... 30 2.5.6 CP1252............................. 31 2.5.7 US-ASCII............................ 32 2.5.8 Encoding ascii-print ....................... 33 2.5.9 Clean7Bit............................ 34 2.5.10 Other encodings (8 bit).................... 35 3 Test 80 3.1 Catcode checks for loading....................... 80 3.2 Conversion tests............................ 82 3.2.1 UTF8/16/32 encodings.................... 83 3.2.2 ASCII.............................. 85 3.2.3 PDFDocEncoding....................... 86 3.2.4 ISO-8859-1........................... 86 3.2.5 CP1252............................. 86 3.2.6 KOI8-R............................. 87 3.2.7 DEC-MCS........................... 87 3.3 Removal of byte order marks....................
    [Show full text]
  • The Microtype Package Subliminal Refinements Towards Typographical Perfection
    The microtype package Subliminal refinements towards typographical perfection R Schlicht v2.8c [email protected] 2021/03/14 The microtype package provides aLaTeX interface to the micro-typographic exten- sions that were introduced by pdfTeX and have since also propagated to LuaTeX and X Te eX: most prominently, character protrusion and font expansion, furthermore the adjustment of interword spacing and additional kerning, as well as hyphenatable letterspacing (tracking) and the possibility to disable all or selected ligatures. These features may be applied to customisable sets of fonts, and all micro-typographic aspects of the fonts can be configured in a straight-forward and flexible way. Settings for various fonts are provided. Note that character protrusion requires pdfTeX (version 0.14f or later), LuaTeX, or X Te eX (at least version 0.9997). Font expansion works with pdfTeX (version 1.20 for automatic expansion) or LuaTeX. The package will by default enable protrusion and expansion if they can safely be assumed to work. Disabling ligatures requires pdfTeX( 1.30) or LuaTeX, while the adjustment of interword spacing and of kerning only works≥ with pdfTeX( 1.40). Letterspacing is available with pdfTeX( 1.40) or LuaTeX( 0.62). ≥ ≥ The alternative≥ package letterspace, which also works with plainT eX, provides the user commands for letterspacing only, omitting support for all other extensions (see section7). This package is copyright © 2004–2021 R Schlicht. It may be distributed and/or modified under the conditions of theLaTeX Project Public License, either version 1.3c of this license or (at your option) any later version.
    [Show full text]
  • Misc Lexing and String Handling Improvements
    Misc lexing and string handling improvements Document #: P2178R0 Date: 2020-06-15 Project: Programming Language C++ Audience: EWG, SG-16 Reply-to: Corentin Jabot <[email protected]> Abstract This Omnibus paper proposes a series of small improvements to the lexing of C++ and the forming of string handling, notably to clarify the behavior of Unicode encoded sources files, and to reduce implementation divergence. This paper intends to supersede N3463 [1] and P1854R0 [3] and proposes a resolution to several core issues. While some of these changes are unrelated, the intend of this paper’s authors and SG-16 is to rewrite the description of lexing using more accurate terminology, a wording will, therefore, be provided incorporating all the desired design changes. Updating both the design an the terminology lets us acknowledge and handle the subtilities of text which may not have been fully understood in a pre-Unicode world. The overarching goals are to reduce the divergence in implementations, the complexity of the mental model, and most importantly to make sure that the semantic of text elements is conserved through the different phases of compilation. Proposals All the proposed changes relate to phases 1-6 of translations. In particular, this proposal has no library impact. Proposal 1: Mandating support for UTF-8 encoded source files in phase 1 The set of source file character sets is implementation-defined, which makes writing portable C++ code impossible. We proposed to mandate that C++ compilers must accept UTF-8 as an input format. Both to increase portability and to ensure that Unicode related features (ex P1949R3 [2] can be used widely.
    [Show full text]
  • Dhtmlet® | See Also
    DHTMLET® | SEE ALSO Introduction To CSS2 Dynamic Properties Filters Behaviors HTMLObjectElementHTMLAttributesProperties CSSCascading Style Sheet (Linking to a Style Sheet) .cssHTMLlink <head> <title>title of article</title> <link rel=stylesheet href="http://www.dhtmlet.com/rainer.css" type="text/c ss"> </head> XML <? xml-stylesheet type="text/css" href="http://www.dhtmlet.com/rainer.css ?>> (Embedding a Style Block) HTML<HTML><BODY><STYLE>...</STYLE> <html> <style type="text/css"> <!-- body {font: 10pt "Arial"} h1 {font: 15pt/17pt "Arial"; font-weight: bold; color: maroon} h2 {font: 13pt/15pt "Arial"; font-weight: bold; color: blue} p {font: 10pt/12pt "Arial"; color: black} --> </style> <body> styletype"text/css" (Inline Styles) style <p style="margin-left: 0.5in; margin-right:0.5in"><p> (CSS Syntax) Selector { property: value } Selector -- property : value -- (:)(;) (The ' Inherit ' Value) Inherit · ©2001; rain1977.comer . All rights reserved . Terms of Use . About this handbook (COPYRIGHT) Mainsoft(R)World Wide Web Consortium (W3C) Mainsoft(R)HTML Help rain1977.comerdhtmlet (UPDATE) 200141 www.dhtmlet.com · ©2001; rain1977.comer . All rights reserved . Terms of Use . About rain1977 (Vita) 1996 - 1999 (CAOSC) 1999 - 2000 (www.chineseall.com) 2000 -- (www.rongshu.com) (Intro) (JScripts)(CSS)HTML4.0 www.dhtmlet.comwww.rain1977.com [email protected]@[email protected] 13916616163 139912E3 () 200040 · ©2001; rain1977.comer . All rights reserved . Terms of Use . DHTMLET® | SEE ALSO CSS Properties Reference
    [Show full text]
  • Character Data Representation Architecture (CDRA)
    Character Data Representation Architecture Character Data Representation Architecture (CDRA) is an IBM architecture which defines a set of identifiers, resources and APIs for identifying character data and maintaining data integrity during data conversion processes. The reference publication provides the reader with the framework for the identifiers, descriptions of the supporting resources and APIs, as well as methods for data conversions. CDRA is applicable to country specific data encodings such as the ISO-8859 series as well as large character sets such as Unicode. Edition Notice: Updated in 2018, this document is a revised, on-line version of the original IBM publication. This version of the document contains many typographical and editorial corrections. A section on the Unicode Encoding Structure has been added in Appendix A. Also, Appendix K has been added to document the CDRA identifiers defined in support of Unicode. Likewise, Appendix J, has been updated with information on how to obtain CDRA conversion table resources on-line. Appendix L was added containing the EBCDIC control code definitions. Overview • Chapter 1. Introduction • Chapter 2. Architecture Strategy Architecture Definition • Chapter 3. CDRA Identifiers • Chapter 4. Services • Chapter 5. CDRA Interface Definitions • Chapter 6. Difference Management • Chapter 7. CDRA Resources and Their Management Appendices • Appendix A. Encoding Schemes • Appendix B. Conversion Methods • Appendix C. CCSID Repository • Appendix D. Platform Support of CDRA • Appendix E. Graphic Character Identification Copyright IBM Corp. 1990, 1995, 2018 • Appendix F. Character Sets and Code Pages • Appendix G. Control Character Mappings • Appendix H. CDRA and IBM i (Formerly OS/400) • Appendix I. DFSMS/MVS Considerations • Appendix J.
    [Show full text]
  • The Inputenx Package
    The inputenx package Heiko Oberdiek <[email protected]> 2009/08/13 v1.4 Abstract This package provides input encodings using standard mappings and cov- ers nearly all slots. Thus it serves as more uptodate replacement for package inputenc. Contents 1 Documentation2 1.1 Definition files.............................3 1.2 Unicode.................................4 1.3 Math...................................4 1.4 ToDo...................................4 2 Implementation4 2.1 Identification..............................4 2.2 Encoding names............................4 2.2.1 Record current encoding names................4 2.2.2 Aliases for encoding names..................5 2.3 Package options.............................6 2.3.1 Declare and process options..................6 2.3.2 Load inputenc with encoding options.............6 2.3.3 \InputEncoding ........................6 2.3.4 Option math ..........................6 2.4 Alias encoding file...........................7 2.5 Encoding files..............................8 2.5.1 Encoding ascii.........................8 2.5.2 Encoding atarist........................8 2.5.3 Encoding iso-8859-1...................... 12 2.5.4 Encoding iso-8859-2...................... 15 2.5.5 Encoding iso-8859-3...................... 17 2.5.6 Encoding iso-8859-4...................... 19 2.5.7 Encoding iso-8859-5...................... 21 2.5.8 Encoding iso-8859-8...................... 23 2.5.9 Encoding iso-8859-9...................... 25 2.5.10 Encoding iso-8859-10...................... 28 2.5.11 Encoding iso-8859-13...................... 30 2.5.12 Encoding iso-8859-14...................... 32 2.5.13 Encoding iso-8859-15...................... 34 2.5.14 Encoding iso-8859-16...................... 36 2.5.15 Encoding cp437......................... 38 2.5.16 Encoding cp850......................... 42 2.5.17 Encoding cp852......................... 46 2.5.18 Encoding cp855........................
    [Show full text]
  • The Inputenx Package
    The inputenx package Heiko Oberdiek∗ 2019/11/29 v1.12 Abstract This package provides input encodings using standard mappings and cov- ers nearly all slots. Thus it serves as more uptodate replacement for package inputenc. Contents 1 Documentation3 1.1 Definition files.............................3 1.2 Unicode.................................5 1.3 Verbatim................................5 1.4 Math...................................5 1.5 Setting the input encoding.......................5 1.5.1 Encoding as package option..................5 1.5.2 \InputEncoding ........................5 1.5.3 Hooks..............................6 2 Implementation6 2.1 Identification..............................6 2.2 Encoding names............................6 2.2.1 Record current encoding names................6 2.2.2 Catcode settings for file reading................6 2.2.3 Aliases for encoding names..................7 2.3 Package options.............................8 2.3.1 Declare and process options..................8 2.3.2 Load inputenc with encoding options.............8 2.3.3 \InputEncoding ........................9 2.3.4 Option math .......................... 10 2.4 Alias encoding file........................... 10 2.5 Encoding files.............................. 11 2.5.1 Encoding ascii ......................... 11 2.5.2 Encoding verbatim ....................... 11 2.5.3 Encoding atarist........................ 12 2.5.4 Encoding iso-8859-1...................... 16 2.5.5 Encoding iso-8859-2...................... 19 2.5.6 Encoding iso-8859-3...................... 21 2.5.7 Encoding iso-8859-4...................... 24 2.5.8 Encoding iso-8859-5...................... 26 2.5.9 Encoding iso-8859-8...................... 28 ∗Please report any issues at https://github.com/ho-tex/inputenx/issues 1 2.5.10 Encoding iso-8859-9...................... 30 2.5.11 Encoding iso-8859-10...................... 33 2.5.12 Encoding iso-8859-13.....................
    [Show full text]