DOCSLIB.ORG

The Uplatex2ε Sources

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The Uplatex2ε Sources The upLATEX 2" Sources Ken Nakano & Japanese TEX Development Community & TTK Version u04 (last updated: 2021/03/04) Contents a uplvers.dtx 1 1 upLATEX 2" のバージョンの設定 1 1.1 LATEX 2.09 互換モードの抑制 ..................... 2 1.2 起動時に表示するバナー ....................... 2 b uplfonts.dtx 3 2 概要 3 2.1 docstrip プログラムのためのオプション .............. 3 3 コード 4 4 デフォルト設定ファイル 4 4.1 テキストフォント ........................... 4 4.2 プリロードフォント .......................... 5 4.3 組版パラメータ ............................ 6 5 フォント定義ファイル 7 c ukinsoku.dtx 9 6 禁則 9 6.1 半角文字に対する禁則 ......................... 9 6.2 全角文字に対する禁則 ......................... 10 i 7 文字間のスペース 14 7.1 ある英字と前後の漢字の間の制御 . 14 7.2 ある漢字と前後の英字の間の制御 . 17 d ujclasses.dtx 20 8 オプションスイッチ 20 9 オプションの宣言 21 9.1 用紙オプション ............................ 22 9.2 サイズオプション ........................... 22 9.3 横置きオプション ........................... 23 9.4 トンボオプション ........................... 23 9.5 面付けオプション ........................... 23 9.6 組方向オプション ........................... 24 9.7 両面、片面オプション ......................... 24 9.8 二段組オプション ........................... 24 9.9 表題ページオプション ......................... 24 9.10 右左起こしオプション ......................... 24 9.11 数式のオプション ........................... 24 9.12 参考文献のオプション ......................... 25 9.13 日本語ファミリ宣言の抑制、和欧文両対応の数式文字 . 25 9.14 ドラフトオプション .......................... 26 9.15 オプションの実行 ........................... 26 10 フォント 26 11 レイアウト 30 11.1 用紙サイズの決定 ........................... 30 11.2 段落の形 ................................ 31 11.3 ページレイアウト ........................... 31 11.3.1 縦方向のスペース ....................... 31 11.3.2 本文領域 ............................ 32 11.3.3 マージン ............................ 38 11.4 脚注 .................................. 41 11.5 フロート ................................ 42 11.5.1 フロートパラメータ ...................... 42 ii 11.5.2 フロートオブジェクトの上限値 . 44 12 改ページ（日本語 TEX 開発コミュニティ版のみ） 45 13 ページスタイル 46 13.1 マークについて ............................ 47 13.2 plain ページスタイル ......................... 47 13.3 jpl@in ページスタイル ........................ 47 13.4 headnombre ページスタイル ..................... 48 13.5 footnombre ページスタイル ...................... 48 13.6 headings スタイル ........................... 48 13.7 bothstyle スタイル ........................... 50 13.8 myheading スタイル .......................... 51 14 文書コマンド 51 14.1 表題 .................................. 51 14.2 概要 .................................. 56 14.3 章見出し ................................ 57 14.3.1 マークコマンド ......................... 57 14.3.2 カウンタの定義 ......................... 57 14.3.3 前付け、本文、後付け ..................... 59 14.3.4 ボックスの組み立て ...................... 60 14.3.5 part レベル ........................... 61 14.3.6 chapter レベル ......................... 63 14.3.7 下位レベルの見出し ...................... 65 14.3.8 付録 ............................... 66 14.4 リスト環境 ............................... 66 14.4.1 enumerate 環境 ......................... 69 14.4.2 itemize 環境 .......................... 70 14.4.3 description 環境 ........................ 71 14.4.4 verse 環境 ............................ 71 14.4.5 quotation 環境 ......................... 72 14.4.6 quote 環境 ........................... 72 14.5 フロート ................................ 72 14.5.1 figure 環境 ........................... 73 14.5.2 table 環境 ............................ 73 14.6 キャプション .............................. 74 iii 14.7 コマンドパラメータの設定 ...................... 75 14.7.1 array と tabular 環境 ...................... 75 14.7.2 tabbing 環境 .......................... 75 14.7.3 minipage 環境 ......................... 75 14.7.4 framebox 環境 ......................... 75 14.7.5 equation と eqnarray 環境 ................... 76 15 フォントコマンド 76 16 相互参照 78 16.1 目次 .................................. 78 16.1.1 本文目次 ............................ 80 16.1.2 図目次と表目次 ......................... 82 16.2 参考文献 ................................ 83 16.3 索引 .................................. 84 16.4 脚注 .................................. 84 17 今日の日付 85 18 初期設定 86 変更履歴 88 索 引 93 iv File a uplvers.dtx 1 upLATEX 2" のバージョンの設定 まず、このディストリビューションでの upLATEX 2" の日付とバージョン番号を定義し ます。2018/03/09 以降、upLATEX 2" のフォーマット作成では pLATEX 2" が提供する plcore.ltx の後から uplcore.ltx が読まれなければなりません。また、2020/02/02 以降は \textmc や \em の定義も upldefs.ltx ではなく共通の plcore.ltx に依存 します。そのため、pLATEX のバージョンを確認します。 1 ⟨∗plcorei 2 \ifx\pfmtversion\@undefined 3 \errhelp{Please update your TeX installation; if not available, 4 obtain it^^Jmanually from CTAN 5 (https://ctan.org/pkg/uplatex) or from^^JGitHub 6 (https://github.com/texjporg/uplatex).}% 7 \errmessage{This should not happen!^^JThere should be some 8 inconsistency in your installation;^^Jtry 9 removing old `uplatex.ltx' and install the 10 latest one}\@@end 11 \else 12 \ifnum\expandafter\@parse@version\pfmtversion//00\@nil<20200202 13 \errhelp{Please update your TeX installation; if not available, 14 obtain it^^Jmanually from CTAN 15 (https://ctan.org/pkg/platex) or from^^JGitHub 16 (https://github.com/texjporg/platex).}% 17 \errmessage{This version of upLaTeX2e requires pLaTeX2e 2020/02/02 18 or newer!^^JObtain a newer version of `platex', 19 otherwise upLaTeX2e setup will^^Jnever succeed}\@@end 20 \fi 21 \fi 22 h=plcorei \pfmtname upLATEX 2" のフォーマットファイル名とバージョンです。フォーマット名は \pfmtversion pLATEX 2" のもの (pLaTeX2e) をそのまま引き継ぎ、バージョンは pLATEX 2" の \ppatch@level ものの末尾に \u04" のようにサフィックスを付けます。 23 ⟨∗plcorei 24 %\def\pfmtname{pLaTeX2e} 25 \def\uppatch@level{u04} 26 \edef\pfmtversion{\pfmtversion\uppatch@level} 27 h=plcorei File a: uplvers.dtx Date: 2020/02/01 Version v1.1r-u03 1 1.1 LATEX 2.09 互換モードの抑制 \documentstyle pLATEX は、\documentclass の代わりに \documentstyle が使われると LATEX 2.09 互換モードに入ります。しかし、upLATEX は新しいマクロパッケージですので、 LATEX 2.09 互換モードをサポートしません。このため、plcore.dtx の定義を上 書きして明確なエラーを出します。 28 ⟨∗plfinali 29 \def\documentstyle{% 30 \@latex@error{upLaTeX does NOT support LaTeX 2.09 compatibility 31 mode.\MessageBreak Use \noexpand\documentclass instead}{% 32 \noexpand\documentstyle is an old convention of LaTeX 2.09, 33 which has been\MessageBreak obsolete since 1995. upLaTeX is 34 first released in 2007, so we do\MessageBreak not provide any 35 emulation of the LaTeX 2.09 author environment.\MessageBreak 36 New documents should use Standard LaTeX conventions, and 37 start\MessageBreak with the \noexpand\documentclass command.}% 38 \documentclass} 39 h=plfinali 1.2 起動時に表示するバナー \everyjob upLATEX 2" が起動されたときに表示される文字列は、pLATEX 2" の中ですでに設定 されています。 File a: uplvers.dtx Date: 2020/02/01 Version v1.1r-u03 2 File b uplfonts.dtx 2 概要 ここでは、和文書体を NFSS2 のインターフェイスで選択するためのコマンドやマクロ について説明をしています。また、フォント定義ファイルや初期設定ファイルなどの 説明もしています。新しいフォント選択コマンドの使い方については、fntguide.tex や usrguide.tex を参照してください。 第 2 節 この節です。このファイルの概要と docstrip プログラムのためのオプショ ンを示しています。 第 3 節 実際のコードの部分です。 第 4 節 プリロードフォントやエラーフォントなどの初期設定について説明をして います。 第 5 節 フォント定義ファイルについて説明をしています。 2.1 docstrip プログラムのためのオプション docstrip プログラムのためのオプションを次に示します。 オプション 意味 plcore uplcore.ltx の断片を生成するオプションでしたが、削除。 trace uptrace.sty を生成します。 JY2mc 横組用、明朝体のフォント定義ファイルを生成します。 JY2gt 横組用、ゴシック体のフォント定義ファイルを生成します。 JT2mc 縦組用、明朝体のフォント定義ファイルを生成します。 JT2gt 縦組用、ゴシック体のフォント定義ファイルを生成します。 pldefs upldefs.ltx を生成します。次の４つのオプションを付加 することで、プリロードするフォントを選択することがで きます。デフォルトは 10pt です。 xpt 10pt プリロード xipt 11pt プリロード xiipt 12pt プリロード ori plfonts.tex に似たプリロード File b: uplfonts.dtx Date: 2020/02/01 Version v1.6v-u02 3 3 コード NFSS2 の拡張は、pLATEX において plfonts.dtx から生成される plcore.ltx をそ のまま利用するので、upLATEX では定義しません。後方互換性のため、uptrace.sty を提供しますが、これも単に ptrace.sty を読み込むだけとします。 1 ⟨∗tracei 2 \NeedsTeXFormat{pLaTeX2e} 3 \ProvidesPackage{uptrace} 4 [2019/09/22 v1.6t-u02 Standard upLaTeX package (font tracing)] 5 \RequirePackageWithOptions{ptrace} 6 h=tracei デフォルト設定ファイル upldefs.ltx は、もともと uplcore.ltx の途中で読み 込んでいましたが、2018 年以降の新しいコミュニティ版 upLATEX では uplatex.ltx から読み込むことにしました。実際の中身については、第 4 節を参照してください。 4 デフォルト設定ファイル ここでは、フォーマットファイルに読み込まれるデフォルト値を設定しています。こ の節での内容は upldefs.ltx に出力されます。このファイルの内容を uplcore.ltx に含めてもよいのですが、デフォルトの設定を参照しやすいように、別ファイルに してあります。 プリロードサイズは、docstrip プログラムのオプションで変更することができ ます。これ以外の設定を変更したい場合は、upldefs.ltx を直接、修正するのでは なく、このファイルを upldefs.cfg という名前でコピーをして、そのファイルに対 して修正を加えるようにしてください。 7 ⟨∗pldefsi 8 \ProvidesFile{upldefs.ltx} 9 [2020/02/01 v1.6v-u02 upLaTeX Kernel (Default settings)] 10 h=pldefsi 4.1 テキストフォント テキストフォントのための属性やエラー書体などの宣言です。pLATEX のデフォル トの横組エンコードは JY1、縦組エンコードは JT1 ですが、upLATEX では横組エン コードは JY2、縦組エンコードは JT2 とします。 縦横エンコード共通： 11 ⟨∗pldefsi 12 \DeclareKanjiEncodingDefaults{}{} 13 \DeclareErrorKanjiFont{JY2}{mc}{m}{n}{10} File b: uplfonts.dtx Date: 2020/02/01 Version v1.6v-u02 4 14 \kanjifamily{mc} 15 \kanjiseries{m} 16 \kanjishape{n} 17 \fontsize{10}{10} 横組エンコード： 18 \DeclareYokoKanjiEncoding{JY2}{}{} 19 \DeclareKanjiSubstitution{JY2}{mc}{m}{n} 縦組エンコード： 20 \DeclareTateKanjiEncoding{JT2}{}{} 21 \DeclareKanjiSubstitution{JT2}{mc}{m}{n} 縦横のエンコーディングのセット化： 22 \KanjiEncodingPair{JY2}{JT2} フォント属性のデフォルト値：LATEX 2" 2019-10-01 までは \shapedefault は \updefault でしたが、LATEX 2" 2020-02-02 で \updefault が \n" から \up" へ と修正されたことに伴い、\shapedefault は明示的に \n" に設定されました。 23 \newcommand\mcdefault{mc} 24 \newcommand\gtdefault{gt} 25 \newcommand\kanjiencodingdefault{JY2} 26 \newcommand\kanjifamilydefault{\mcdefault} 27 \newcommand\kanjiseriesdefault{\mddefault} 28 \newcommand\kanjishapedefault{n}% formerly \updefault 和文エンコードの指定： 29 \kanjiencoding{JY2} フォント定義：これらの具体的な内容は第 5 節を参照してください。 30 \input{jy2mc.fd} 31 \input{jy2gt.fd} 32 \input{jt2mc.fd} 33 \input{jt2gt.fd} フォントを有効にします。 34 \fontencoding{JT2}\selectfont 35 \fontencoding{JY2}\selectfont 4.2 プリロードフォント あらかじめフォーマットファイルにロードされるフォントの宣言です。docstrip プログラムのオプションでロードされるフォントのサイズを変更することができま す。uplfmt.ins では xpt を指定しています。 36 ⟨∗xpti 37 \DeclarePreloadSizes{JY2}{mc}{m}{n}{5,7,10,12} 38 \DeclarePreloadSizes{JY2}{gt}{m}{n}{5,7,10,12} 39 \DeclarePreloadSizes{JT2}{mc}{m}{n}{5,7,10,12}
Load more

Recommended publications
  • 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.
    [Show full text]
  • Specification Method for Cultural Conventions
    Reference number of working document: ISO/IEC JTC1/SC22/WG20 N690 Date: 1999-06-28 Reference number of document: ISO/IEC PDTR 14652 Committee identification: ISO/IEC JTC1/SC22 Secretariat: ANSI Information technology Ð Specification method for cultural conventions Technologies de l’information — Méthode de modélisation des conventions culturelles 1 Document type: International standard Document subtype: if applicable Document stage: (40) Enquiry Document language: E H:\IPS\SAMARIN\DISKETTE\BASICEN.DOT ISO Basic template Version 3.0 1997-02-03 ISO/IEC PDTR 14652:1999(E) © ISO/IEC 2 Contents Page 3 4 1 SCOPE 1 5 2 NORMATIVE REFERENCES 1 6 3 TERMS, DEFINITIONS AND NOTATIONS 2 7 4 FDCC-set 6 8 4.1 FDCC-set definition 6 9 4.2 LC_IDENTIFICATION 10 10 4.3 LC_CTYPE 11 11 4.4 LC_COLLATE 27 12 4.5 LC_MONETARY 42 13 4.6 LC_NUMERIC 46 14 4.7 LC_TIME 47 15 4.8 LC_MESSAGES 53 16 4.9 LC_PAPER 53 17 4.10 LC_NAME 55 18 4.11 LC_ADDRESS 57 19 4.12 LC_TELEPHONE 57 20 5 CHARMAP 58 21 6 REPERTOIREMAP 62 22 7 CONFORMANCE 89 23 Annex A (informative) DIFFERENCES FROM POSIX 90 24 Annex B (informative) RATIONALE 92 25 Annex C (informative) BNF GRAMMAR 106 26 Annex D (informative) INDEX 111 27 BIBLIOGRAPHY 114 ii © ISO/IEC ISO/IEC PDTR 14652:1999(E) 28 Foreword 29 30 ISO (the International Organization for Standardization) and IEC (the International 31 Electrotechnical Commission) form the specialized system for worldwide standardization. 32 National bodies that are members of ISO or IEC participate in the development of 33 International Standards through technical committees established by the respective 34 organization to deal with particular fields of technical activity.
    [Show full text]
  • CSV Import and Export
    Importing Tabular Data into Protogrid Protogrid supports the import of CSV files into TableViews. In order to make your data compatible, a few preliminary steps as outlined below are necessary before the import. In this document we assume that you work with Microsoft Excel, however any spreadsheet software or even text editor with UTF-8 support is suitable for this task. Preparing Your Spreadsheet 1. The first row of your spreadsheet should contain the field (column) names according to your current language setting in Protogrid. You may leave out non-mandatory fields, however the field names need to match exactly what you have in your spreadsheet. Any order is acceptable, i.e. it does not need to follow what you see in your Protogrid TableView. 2. Make sure that for all the mandatory fields specified by the corresponding Data Proto, you don’t have any empty cells in your spreadsheet column. 3. Make sure that your cells don’t contain any tabulators. They may however contain commas or semicolons. 4. If you have relational columns (with foreign keys) in your spreadsheet, make sure that: a. the column entries correspond to Shortnames (a short textual representation) of existing Cards for the related Proto. Please note that Protogrid computes a default Shortname for any Card, as displayed in the corresponding TableView column. You can change Shortname of a Card by using a ScriptLibrary (please have a look at the default code that is generated when creating a new ScriptLibrary). b. in case of m-to-n relations, separate the column entries using the tilde (‘wave dash’) character (~).
    [Show full text]
  • Chapter 6, Writing Systems and Punctuation
    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]
  • IBM Cognos Powerplay Version 11.0: Administration Guide Introduction
    IBM Cognos PowerPlay Version 11.0 Administration Guide IBM © Product Information This document applies to IBM Cognos Analytics version 11.0.0 and may also apply to subsequent releases. Copyright Licensed Materials - Property of IBM © Copyright IBM Corp. 2005, 2018. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. IBM, the IBM logo and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml. The following terms are trademarks or registered trademarks of other companies: v Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. v Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. v Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. v Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. v UNIX is a registered trademark of The Open Group in the United States and other countries. v Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
    [Show full text]
  • Unicode Line Breaking Algorithm Technical Reports
    4/26/2018 UAX #14: Unicode Line Breaking Algorithm Technical Reports Proposed Update Unicode® Standard Annex #14 UNICODE LINE BREAKING ALGORITHM Version Unicode 11.0.0 (draft 1) Editors Andy Heninger ([email protected]) Date 2018-04-10 This Version http://www.unicode.org/reports/tr14/tr14-40.html Previous http://www.unicode.org/reports/tr14/tr14-39.html Version Latest http://www.unicode.org/reports/tr14/ Version Latest http://www.unicode.org/reports/tr14/proposed.html Proposed Update Revision 40 Summary This annex presents the Unicode line breaking algorithm along with detailed descriptions of each of the character classes established by the Unicode line breaking property. The line breaking algorithm produces a set of "break opportunities", or positions that would be suitable for wrapping lines when preparing text for display. Status This is a draft document which may be updated, replaced, or superseded by other documents at any time. Publication does not imply endorsement by the Unicode Consortium. This is not a stable document; it is inappropriate to cite this document as other than a work in progress. A Unicode Standard Annex (UAX) forms an integral part of the Unicode Standard, but is published online as a separate document. The Unicode Standard may require conformance to normative content in a Unicode Standard Annex, if so specified in the Conformance chapter of that version of the Unicode Standard. The version number of a UAX document corresponds to the version of the Unicode Standard of which it forms a part. https://www.unicode.org/reports/tr14/tr14-40.html 1/59 4/26/2018 UAX #14: Unicode Line Breaking Algorithm Please submit corrigenda and other comments with the online reporting form [Feedback].
    [Show full text]
  • Iso/Iec 30112 Wd12 Standard
    INTERNATIONAL ISO/IEC 30112 WD12 STANDARD ISO/IEC 30112 WD12 2018-02-12 Information technology — Specification methods for cultural conventions Technologies de l'information — Méthodes de modélisation des conventions culturelles This page left for ISO/IEC copyright notices. ISO/IEC 30112 WD12 Contents Page CONTENTS iii FOREWORD iv INTRODUCTION v 1 SCOPE 1 2 NORMATIVE REFERENCES 1 3 TERMS, DEFINITIONS AND NOTATIONS 1 4 FDCC-set 7 4.1 FDCC-set description 8 4.2 LC_IDENTIFICATION 13 4.3 LC_CTYPE 15 4.4 LC_COLLATE 48 4.5 LC_MONETARY 62 4.6 LC_NUMERIC 67 4.7 LC_TIME 68 4.8 LC_MESSAGES 77 4.9 LC_XLITERATE 78 4.10 LC_NAME 80 4.11 LC_ADDRESS 82 4.12 LC_TELEPHONE 85 4.13 LC_PAPER 86 4.14 LC_MEASUREMENT 86 4.15 LC_KEYBOARD 87 5 CHARMAP 87 6 REPERTOIREMAP 93 7 FUNCTIONALITY 127 8 MESSAGE FORMAT 127 Annex A (informative) DIFFERENCES FROM POSIX 127 Annex B (informative) RATIONALE 129 Annex C (informative) BNF GRAMMAR 145 Annex D (informative) RELATION TO TAXONOMY 151 Annex E (informative) IMPLEMENTATION IN GLIBC 154 Annex F (informative) INDEX 155 BIBLIOGRAPHY 158 2 © ISO/IEC 2018 – All rights reserved ISO/IEC 30112 WD12 Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work.
    [Show full text]
  • Developer Camp
    【1E】 Delphi / C++ テクニカルセッション 「Delphiでの文字コードのハンドリングについて」 有限会社 エイブル 富永 英明 1 はじめに まずは文字コードの種類を知る • 日本で使われる有名所の文字コード – Shift_JIS – ISO-2022-JP – EUC-JP – UTF-8 (Unicode) – UTF-16 (Unicode) • 文字コードがどうなっているのか知らない事には始まらない。 • …でも、あんまり詳しくやってると文字コードだけで終わっちゃいますの で、“駆け足で” やります。 3 文字集合 JIS X 0208 JIS X 0201 JIS X 0212 (ANSI 漢字集合) (ANK 半角カナ) (補助漢字) Unicode JIS X 0213 (ANSI 漢字集合) 4 文字エンコーディング JIS X 0208 JIS X 0213 EUC-JP SHIFT_JIS ISO-2022-JP Unicode UTF-8 UTF-16 UTF-32 UTF-7 5 ANSI – Shift_JIS • Shift_JIS – Windows では CP932 – 1 エレメント (文字構成単位) は 1 バイト – 漢字は 2 バイト (2 エレメント で構成される) – 亜種が多い。所謂、”機種依存文字” が多い。 名称 備 考 Shift_JIS JIS X 0208 ベース CP932 JIS X 0208 ベース Shift_JISX0213 JIS X 0213:2000 ベース Shift_JIS-2004 JIS X 0213:2004 ベース 他多数。 – "補助漢字 (JIS X 0212)" は使えない。 – Shift_JISX0213 と Shift_JIS-2004 は第3/4水準漢字が使える。 – 0x5C (パスデリミタ) が 2 バイト文字に含まれる場合がある。 – Delphi 1 ～ Delphi 2007 でのデフォルト文字コード (於日本) 6 ANSI – Shift_JIS • 機種依存文字 – 例えば、Mac OS X。 ANSI Windows Mac 0xFD (未使用) © 0xFE (未使用) ™ 0xFD と 0xFE を Unicode に変換してみると… ANSI Windows Mac (私用領域) 0xFD © U+F8F1 U+00A9 (私用領域) 0xFE ™ U+F8F2 U+2122 7 ANSI – Shift_JIS • パスデリミタの問題 – 2バイト文字が考慮されていないと… C:¥集計表１.txt “表” は 0x95, 0x5C で、2バイト目に 0x5C (パスデリミタ) を含んでいる。 海外製のアプリケーションで問題になる事が多い。 C:¥饅頭怖い.txt 等も同様。 – コンソールアプリケーションの場合には、0x7C (パイプ) にも注意が必要。 C:¥竹の弓.txt 現在では問題になる事はあまりないとは思うが念のため。 8 ANSI – Shift_JIS • パスデリミタの問題 – パスデリミタ ( ¥ = 0x5C) を含む漢字は… ― ソ Ы Ⅸ 噂 浬 欺 圭 構 蚕 十 申 曾 箪 貼 能 表 暴 予 禄 兔 喀 媾 彌 拿 杤 歃 濬 畚 秉 綵 臀 藹 觸 軆 鐔 饅 鷭 偆 砡 – パイプ ( | = 0x7C) を含む漢字は… － ポ л 榎 掛 弓 芸 鋼 旨 楯 酢 掃 竹 倒 培 怖 翻 慾 處 嘶 斈 忿 掟 桍 毫 烟 痞 窩 縹 艚 蛞 諫 轎 閖 驂 黥 埈 蒴 9 ANSI – ISO-2022-JP
    [Show full text]
  • L2/01-252-Amd
    ISO/IEC JTC1/SC2 N ISO/IEC JTC1/SC2/WG2 N Universal Multiple Octet Coded Character Set International Organization for Standardization Organisation internationale de normalisation Международная организация по стандартизации Doc Type: Document for Ballot Title: FPDAM text for Amendment 1 to ISO/IEC 10646-1:2000 Source: Project editor Michel Suignard, and contributing editors Michael Everson and Asmus Freytag Status: Working Group Document Action: For JTC1/SC2 ballot Date: 2001-06-07 Note to reviewers: In the character code tables, both new and existing characters are printed. The new characters are shown in a light yellow background, which, on some printers, may show as light gray background. The existing characters that have been corrected since the last edition are also shown in the same light yellow background. This highlight is solely intended as an aid to the reviewer, and is not formally part of the standard. The fonts in the code charts reflect the best fonts available to the editors as of this date. (This page left intentionally blank) Final Proposed Draft Amendment (FPDAM) ISO/IEC 10646-1:2000/Amd. 1:2001 (E) Information technology — Universal Multiple-Octet Coded Character Set (UCS) — Part 1: Architecture and Basic Multilingual Plane AMENDMENT 1: Mathematical symbols and other characters Item 1. Mathematical and other Table 85 - Row 2A: Supplemental Mathematical characters Operators Table 86 - Row 2A: Supplemental Mathematical 1. Modifications to existing tables Operators Insert the following additional character glyphs and Table 98 - Row 31: Katakana Phonetic names at the indicated positions in the tables given Extensions below in Item 15, the character names replacing the Table 145 - Row FA: CJK Compatibility existing entries which read “(This position shall not Ideographs be used)”.
    [Show full text]
  • Oracle Database Globalization Support Guide, 10G Release 2 (10.2) B14225-02
    Oracle® Database Globalization Support Guide 10g Release 2 (10.2) B14225-02 December 2005 Oracle Database Globalization Support Guide, 10g Release 2 (10.2) B14225-02 Copyright © 1996, 2005, Oracle. All rights reserved. Primary Author: Cathy Shea Contributing Authors: Paul Lane, Cathy Baird Contributors: Dan Chiba, Winson Chu, Claire Ho, Gary Hua, Simon Law, Geoff Lee, Peter Linsley, Qianrong Ma, Keni Matsuda, Meghna Mehta, Valarie Moore, Shige Takeda, Linus Tanaka, Makoto Tozawa, Barry Trute, Ying Wu, Peter Wallack, Chao Wang, Huaqing Wang, Simon Wong, Michael Yau, Jianping Yang, Qin Yu, Tim Yu, Weiran Zhang, Yan Zhu The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S.
    [Show full text]
  • 6 Java Overview of Oracle8i Java Support
    Oracle8i National Language Support Guide Release 2 (8.1.6) December 1999 Part No. A76966-01 National Language Support Guide, Release 2 (8.1.6) Part No. A76966-01 Copyright © 1996, 1999, Oracle Corporation. All rights reserved. Primary Author: Paul Lane Contributors: Winson Chu, Jason Durbin, Jessica Fan, Yu Gong, Josef Hasenberger, Claire Ho, Peter Linsley, Tom Portfolio, Den Raphaely, Linus Tanaka, Makoto Tozawa, Gail Yamanaka, Michael Yau, Hiro Yoshioka, Sergiusz Wolicki, Simon Wong Graphic Designer: Valarie Moore The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee’s responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and Oracle disclaims liability for any damages caused by such use of the Programs. The Programs (which include both the software and documentation) contain proprietary information of Oracle Corporation; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this document is error free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Oracle Corporation.
    [Show full text]
  • The Power of Globalization Technology
    Oracle9i Database: The Power of Globalization Technology An Oracle White Paper [February] [2002] The Power of Globalization Page 1 GLOBALIZATION SUPPORT - EXECUTIVE OVERVIEW........... 4 THE POWER OF GLOBALIZATION TECHNOLOGY/ INTRODUCTION.......................................................................................... 5 GLOBALIZATION SUPPORT IS NATIONAL LANGUAGE SUPPORT AND MORE ................................................................................ 6 Built in Universal support....................................................................... 6 WHAT IS GLOBALIZATION?................................................................... 6 So who needs Globalization?................................................................. 7 WHY GLOBALIZATION?........................................................................... 7 WHAT’S NEW IN ORACLE9i GLOBALIZATION SUPPORT? ....... 7 Extended Unicode Enablement................................................................. 7 Unicode Encoding................................................................................... 7 UTF-8 Encoding...................................................................................... 7 UTF-16 Encoding.................................................................................... 8 Unicode Databases .................................................................................. 8 Did you know? ......................................................................................... 9 New Unicode Datatypes........................................................................
    [Show full text]