ISO/IEC JTC1/SC2/WG2 N4225 2012-02-04



Similar documents
L2/ Abstract Introduction

Whisky Emoji Submission

ISO/IEC JTC1 SC2/WG2 N4399

JURASSIC EMOJI. This proposal details a set of Jurassic emoji to fix this situation once and for all.

The Unicode Standard Version 8.0 Core Specification

1. Arguments against the term Hungarian Runic


ISO/IEC JTC1/SC2/WG2 N 2342

EURESCOM - P923 (Babelweb) PIR.3.1

Unicode in Mobile Phones

BOARD OF DIRECTORS OF OTP BANK LTD.

1. Basic encoding principles

Toolbox 1! Susan Gehr!! Cell/text (707) !

Frequently Asked Questions on character sets and languages in MT and MX free format fields

Preservation Handbook

Easy Bangla Typing for MS-Word!

LESSON 3: EXHIBITING A CIVIL WAR SOLDIER

INSTALL AND ACTIVATE DRAGON

ª as < º äs < Ω aš << æ aš y < ø eš << eš y < at << at y < ät << ƒ ät y < ot < Δ baš

Numeration systems. Resources and methods for learning about these subjects (list a few here, in preparation for your research):

CivicScience Insight Report

Reliability on ARMA Examinations: How we do it at Miklós Zrínyi National Defence University

Designing Global Applications: Requirements and Challenges

WORKING DRAFT. ISO/IEC International Standard International Standard ISO/IEC st Edition + Amd1

Bitrix Site Manager 4.0. Quick Start Guide to Newsletters and Subscriptions

When older typesetting methods gave

Search Interface to a Mayan Glyph Database based on Visual Characteristics *

Preservation Handbook

Internationalizing JavaScript Applications Norbert Lindenberg. Norbert Lindenberg All rights reserved.

Tests for Divisibility, Theorems for Divisibility, the Prime Factor Test

Creating a Poster Presentation using PowerPoint

Introduction to Unicode. By: Atif Gulzar Center for Research in Urdu Language Processing

Using Unified Communications Chat from Sametime Connect Client

The Unicode Standard Version 8.0 Core Specification

BAR CODE 39 ELFRING FONTS INC.

M3039 MPEG 97/ January 1998

The use of binary codes to represent characters

WebEx Meeting Center User Guide

7-Bit coded Character Set

The Hungarian National Branch has 18 members (11 institutional, 4 individual and 3

Internationalized Domain Names -

Tibetan For Windows - Software Development and Future Speculations. Marvin Moser, Tibetan for Windows & Lucent Technologies, USA

Chapter 4: Computer Codes

.ASIA CJK (Chinese Japanese Korean) IDN Policies

Google Apps to Office 365 for business

RGB Workflow Key Communication Points. Journals today are published in two primary forms: the traditional printed journal and the

National Language (Tamil) Support in Oracle An Oracle White paper / November 2004

About the HealthStream Learning Center

How To Write A Domain Name In Unix (Unicode) On A Pc Or Mac (Windows) On An Ipo (Windows 7) On Pc Or Ipo 8.5 (Windows 8) On Your Pc Or Pc (Windows

The QuickStudy Guide for Sage ACT! 2013

BAR CODE 2 OF 5 INTERLEAVED

Points to Note. Chinese and English characters shall be coded in ISO/IEC 10646:2011, and the set of Chinese

Quick Start Guide. Microsoft Outlook 2013 looks different from previous versions, so we created this guide to help you minimize the learning curve.

Version : 1.0: General Certificate of Secondary Education November Foundation Unit 2. Final. Mark Scheme

Each figure of a manuscript should be submitted as a single file.

Create!form Barcodes. User Guide

Guidelines for Writing System Support

Northeast African Studies BOOK REVIEW GUIDELINES

Encoding script-specific writing rules based on the Unicode character set

Rendering/Layout Engine for Complex script. Pema Geyleg

Read Naturally, Inc. Version: 05 February Saint Paul, Minnesota

SAPScript. A Standard Text is a like our normal documents. In Standard Text, you can create standard documents like letters, articles etc

MISSISSIPPI STATE UNIVERSITY Office of Planning Design and Construction Administration

Crystal Reports Server Quick Installation Guide

Embedded Special Characters Kiran Karidi, Mahipal Vanam, and Sridhar Dodlapati

ISO/TMB/JTCG N 359. N0359 JTCG FAQ to support Annex SL. Document type: Other committee document. Date of document:

EUROPEAN CITIZENS DIGITAL HEALTH LITERACY

Forest Stewardship Council

LECTURE -08 INTRODUCTION TO PRIMAVERA PROJECT PLANNER (P6)

Installation Quick Start SUSE Linux Enterprise Server 11 SP1

IBM Unica emessage Version 8 Release 6 February 13, User's Guide

Using the T&D Thermo App with TR-7wf Data Loggers

Customer admin guide. UC Management Centre

Annual Report

XML Character Encoding and Decoding

HKSCS-2004 Support for Windows Platform

On-entry Assessment Program. Accessing and interpreting online reports Handbook

designed and prepared for california safe routes to school by circle design circledesign.net Graphic Standards

Template and Daily Schedules

ABOUT THIS DOCUMENT ABOUT CHARTS/COMMON TERMINOLOGY

Figure Error! No text of specified style in document..1: Project Organization

WEBMAIL User s Manual

ELFRING FONTS UPC BAR CODES

Manage. Help Documentation. This document was auto-created from web content and is subject to change at any time. Copyright (c) 2016 SmarterTools Inc.

Guidance for ISO liaison organizations Engaging stakeholders and building consensus

What is Memento. Content

PROJECT AND CONSTRUCTION MANAGEMENT SERVICES FOR KUWAIT PORT AUTHORITY FOR PROJECTS AT SHUAIBA PORT

Transcription:

ISO/IEC JTC1/SC2/WG2 N4225 2012-02-04 Doc Type: Working Group Document Title: Proposal for encoding pre-combined and extended Rovas numerals into the Rovas block in the SMP of the UCS Source: Tamás Rumi (Rovas Foundation) Status: Individual Contribution Action: For consideration by UTC and ISO/IEC JTC1/SC2/WG2 Introduction This document contains some information about the usage of the Rovas numerals and proposes Rovas numeral symbols, which have not been included into the N4083. The document contains the proposal summary form. Please send any response to this proposal to Tamás Rumi (email: napjelkepek@gmail.com), curator of the Rovas Foundation. The pre-combined Rovas numerals I support the N4183 in order to give individual code point to each group of numeral signs, which could help the easy transcription between Arabic and Rovas numbers. However, I propose to extend the proposed Rovas numeral range to all pre-combined characters for numbers up to 12. The reason for encoding of pre-combined numerals is for the 12-month use. The use of the Szekely-Hungarian Rovas script in a calendar is an inherent part of the Rovas traditions (Sándor 1991; Hosszú 2011:198 210), the Rovas Calendar (Rovásnaptár) 2012 also continues this tradition. y ROVAS NUMERAL ONE (proposed in N4083) 2 ROVAS NUMERAL TWO (proposed in N4083) 3 ROVAS NUMERAL THREE (proposed in N4083) 4 ROVAS NUMERAL FOUR (proposed in N4083) Y ROVAS NUMERAL FIVE (proposed in N4083) 6 ROVAS NUMERAL SIX NEW 7 ROVAS NUMERAL SEVEN NEW 8 ROVAS NUMERAL EIGHT NEW 9 ROVAS NUMERAL NINE NEW X ROVAS NUMERAL TEN (proposed in N4083) 1 ROVAS NUMERAL ELEVEN NEW 5 ROVAS NUMERAL TWELWE NEW Table 1: The range 1 12 of the Rovas numerals

It is noteworthy that encoding the Rovas pre-combined numerals up to 12 is strictly follows the traditions of the Unicode, see the code range of the Roman numerals U+2160 to U+2171. Extended Rovas numerals Based on the extensive present-day use of the Szekely-Hungarian Rovas script, the Rovas numerals higher than M 1000 are necessary in the Rovas orthography. for the modern use there should be code points for these numbers. In the last decades several research was carried out for improving the traditional repertoire of the Rovas numerals. The most comprehensive solution is presented in Figure 1 (Rumi 2010). Figure 1: The comprehensive system of the Rovas numerals There are some traditions of the Rovas numerals that have to be considered: 2

The glyphs of the 5000 and 500.000 should be graphically half of the glyphs 1000 and 1.000.000, respective. See correlations between Y 5 vs. X 10, V 50 vs. B 100, ² 500 vs. M 1000. According to Historians the Hungarians have used a term for denoting 10.000 soldiers, that was the tömény / tumen. Based on the previous research results, the following Rovas numerals are proposed, see Table 2. < ROVAS NUMERAL FIVE THOUSAND > ROVAS NUMERAL TEN THOUSAND # ROVAS NUMERAL FIFTY THOUSAND & ROVAS NUMERAL ONE HUNDRED THOUSAND $ ROVAS NUMERAL FIVE HUNDRED THOUSAND % ROVAS NUMERAL ONE MILLION ( ROVAS NUMERAL FIVE MILLION ) ROVAS NUMERAL TEN MILLION Table 2: Proposed new characters for Rovas numerals Some examples for use of the Rovas numerals As one of the authors I have investigated the Patakfalvi family s Bible, which have an important long-text Rovas relic in many aspect (see Figure 2). In this relic the number 2 is denoted with 2 TWO. Figure 2: Rovas text in the Patakfalvi Bible 3

See the traditional way of representing Rovas numerals: yyyxv = 67 = 50+10+(5+2) yyyyxxxxbyyyy = 448 = 4*100+40+(5+3) yyyyyxxxvbyyymyy = 2789 = 2*1000+(5+2)*100+(50+30)+(5+4) XXXByyyyMyYXXByyy = 326.430 = (3*100+(20+(5+1)))*1000+4*100+30 MyyXXBMMyyy = 3.122.000 = 3*1000*1000+(100+20+2)*1000 Figure 3 presents a Szekely-gate (traditional Szekely wood carving) with Rovas inscriptions, including the yyyymm = 2004 = 1000+1000+4 Figure 3: Rovas numerals from Nagyatád (West Hungary) (2004), Photo: János Balogh 4

PT PT Form for PT for References Tamás Rumi, András Tisza et al. (2009, web page): A Patakfalvi Bibliában található rovásírás megfejtése, Retrieved in 2009 from http://unitarius.eu/patakfalvi-biblia/index.htm Tamás Rumi, László Sípos, Tamás Somfai (2009): Gárdonyi Géza: Egri csillagok. Transcribed into Szekely-Hungarian Rovas by Tamás Rumi, László Sípos, & Tamás Somfai. Edited by Tamás Rumi. Published in 2009 by Imagent WOU Hungary, ISBN: 978-963-06-7107-1. Tamás Rumi (2010): Körök a Szent Koronán - égi mértékrendszerek az ősi műveltségekben. Budapest: Imagent, ISBN 978-963-87967-7-6. Tamás Rumi, László Sípos (2010): Rovás alapismeretek. Budapest: Imagent and WOU Hungary, ISBN: 978-963-88437-1-5 Tamás Rumi, László Sípos, Tamás Somfai (2010): Illyés Gyula: Hét meg hét magyar népmese, transcribed to Szekely-Hungarian Rovas by Tamás Rumi, László Sípos, & Tamás Somfai. Published by Imagent and WOU Hungary, ISBN: 978-963-88437-0-8 Tamás Rumi, László Sípos (2011): Rovásnaptár 2012 és Rovás ABC oktatótábla. Szolnok: Rovás Foundation Gábor Hosszú, Tamás Rumi, László Sípos (2008): Az élő rovás. Nemzeti írásunk a szabványosítás útján. In Proc. of Living Rovas Symposium, Gödöllő, October 4, 2008. Budapest: Imagent and WOU Hungary. ISBN: 978-963-87967-1-4. Gábor Hosszú (2011): Heritage of Scribes. The Relation of Rovas Scripts to Eurasian Writing Systems. First edition. Budapest: Rovas Foundation, ISBN 978-963-88437-4-6, available from Google Books at http://books.google.hu/books?id=tyk8azcqc34c&pg=pa1 Klára Sándor (1991): A Marsigli-féle székely rovásnaptár és más 15. századi kalendáriumok. In Békési et al. (ed.), Régi és új peregrináció. Magyarok küföldön, külföldiek Magyarországon. Budapest-Szeged: Nemzetközi Magyar Filológiai Társaság-Scriptum Kft., 322-331. Proposal Summary form ISO/IEC JTC 1/SC 2/WG 2 PROPOSAL SUMMARY FORM TO ACCOMPANY SUBMISSIONS 1 FOR ADDITIONS TO THE REPERTOIRE OF ISO/IEC 10646TP Please fill all the sections A, B and C below. Please read Principles and Procedures Document (P & P) from HTUhttp://www.dkuug.dk/JTC1/SC2/WG2/docs/principles.html UTH guidelines and details before filling this form. Please ensure you are using the latest Form from HTUhttp://www.dkuug.dk/JTC1/SC2/WG2/docs/summaryform.htmlUTH. See also HTUhttp://www.dkuug.dk/JTC1/SC2/WG2/docs/roadmaps.html UTH latest Roadmaps. A. Administrative 1. Title: Proposal for encoding pre-combined and extended Rovas numerals into the Rovas block in the SMP of the UCS 2. Requester's name: Tamás Rumi 3. Requester type (Member body/liaison/individual contribution): Individual contribution 4. Submission date: February 4, 2012 1 number: N3152-F (Original 1994-10-14; Revised 1995-01, 1995-04, 1996-04, 1996-08, 1999-03, 2001-05, 2001-09, 2003-11, 2005-01, 2005-09, 2005-10, 2007-03, 2008-05) 5

5. Requester's reference (if applicable): napjelkepek@gmail.com 6. Choose one of the following: This is a complete proposal: (or) More information will be provided later: B. Technical General 1. Choose one of the following: a. This proposal is for a new script (set of characters): Proposed name of script: b. The proposal is for addition of character(s) to an existing block: Name of the existing block: Rovas 2. Number of characters in proposal: 14 3. Proposed category (select one from below - see section 2.2 of P&P document): A-Contemporary X B.1-Specialized (small collection) B.2-Specialized (large collection) C-Major extinct D-Attested extinct E-Minor extinct F-Archaic Hieroglyphic or Ideographic G-Obscure or questionable usage symbols 4. Is a repertoire including character names provided? a. If YES, are the names in accordance with the character naming guidelines in Annex L of P&P document? b. Are the character shapes attached in a legible form suitable for review? 5. Who will provide the appropriate computerized font (ordered preference: True Type, or PostScript format) for publishing the standard? Tamás Rumi If available now, identify source(s) for the font (include address, e-mail, ftp-site, etc.) and indicate the tools used: 6. References: Tamás Rumi, Font Creator a. Are references (to other character sets, dictionaries, descriptive texts etc.) provided? b. Are published examples of use (such as samples from newspapers, magazines, or other sources) of proposed characters attached? 7. Special encoding issues: Does the proposal address other aspects of character data processing (if applicable) such as input, presentation, sorting, searching, indexing, transliteration etc. (if yes please enclose information)? 8. Additional Information: Submitters are invited to provide any additional information about Properties of the proposed Character(s) or Script that will assist in correct understanding of and correct linguistic processing of the proposed character(s) or script. Examples of such properties are: Casing information, Numeric information, Currency information, Display behaviour information such as line breaks, widths etc., Combining behaviour, Spacing behaviour, Directional behaviour, Default Collation behaviour, relevance in Mark Up contexts, Compatibility equivalence and other Unicode normalization related information. See the Unicode standard at THUhttp://www.unicode.orgUTH for such information on other scripts. Also see HTUhttp://www.unicode.org/Public/UNIDATA/UCD.htmlUTH and associated Unicode Technical Reports for information needed for consideration by the Unicode Technical Committee for inclusion in the Unicode Standard. See below. C. Technical - Justification 1. Has this proposal for addition of character(s) been submitted before? If YES explain 2. Has contact been made to members of the user community (for example: National Body, 6

user groups of the script or characters, other experts, etc.)? If YES, with whom? If YES, available relevant documents: Rovas Foundation László Sípos, Tamás Somfai, Dr. Gábor Hosszú 3. Information on the user community for the proposed characters (for example: size, demographics, information technology use, or publishing use) is included? Reference: Rovas Info (rovas.info) 4. The context of use for the proposed characters (type of use; common or rare) Common with increasing popularity Reference: Rovas Info (rovas.info) 5. Are the proposed characters in current use by the user community? If YES, where? Reference: In Hungary and other places, where Hungarians live. 6. After giving due considerations to the principles in the P&P document must the proposed characters be entirely in the BMP? If YES, is a rationale provided? 7. Should the proposed characters be kept together in a contiguous range (rather than being scattered)? 8. Can any of the proposed characters be considered a presentation form of an existing character or character sequence? If YES, is a rationale for its inclusion provided? 9. Can any of the proposed characters be encoded using a composed character sequence of either existing characters or other proposed characters? If YES, is a rationale for its inclusion provided? 10. Can any of the proposed character(s) be considered to be similar (in appearance or function) to an existing character? If YES, is a rationale for its inclusion provided? 11. Does the proposal include use of combining characters and/or use of composite sequences? If YES, is a rationale for such use provided? Is a list of composite sequences and their corresponding glyph images (graphic symbols) provided? 12. Does the proposal contain characters with any special properties such as control function or similar semantics? If YES, describe in detail (include attachment if necessary) 13. Does the proposal contain any Ideographic compatibility character(s)? If YES, is the equivalent corresponding unified ideographic character(s) identified? 7