DOCSLIB.ORG

United States RBDS Standard Specification of the Radio Broadcast Data System (RBDS) April, 2005

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

NRSC STANDARD NATIONAL RADIO SYSTEMS COMMITTEE NRSC-4-A United States RBDS Standard Specification of the radio broadcast data system (RBDS) April, 2005 Part II - Annexes NAB: 1771 N Street, N.W. CEA: 1919 South Eads Street Washington, DC 20036 Arlington, VA 22202 Tel: (202) 429-5356 Fax: (202) 775-4981 Tel: (703) 907-7660 Fax: (703) 907-8113 Co-sponsored by the Consumer Electronics Association and the National Association of Broadcasters http://www.nrscstandards.org NOTICE NRSC Standards, Bulletins and other technical publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for his particular need. Existence of such Standards, Bulletins and other technical publications shall not in any respect preclude any member or nonmember of the Consumer Electronics Association (CEA) or the National Association of Broadcasters (NAB) from manufacturing or selling products not conforming to such Standards, Bulletins or other technical publications, nor shall the existence of such Standards, Bulletins and other technical publications preclude their voluntary use by those other than CEA or NAB members, whether the standard is to be used either domestically or internationally. Standards, Bulletins and other technical publications are adopted by the NRSC in accordance with the NRSC patent policy. By such action, CEA and NAB do not assume any liability to any patent owner, nor do they assume any obligation whatever to parties adopting the Standard, Bulletin or other technical publication. Note: The user's attention is called to the possibility that compliance with this standard may require use of an invention covered by patent rights. By publication of this standard, no position is taken with respect to the validity of this claim or of any patent rights in connection therewith. The patent holder has, however, filed a statement of willingness to grant a license under these rights on reasonable and nondiscriminatory terms and conditions to applicants desiring to obtain such a license. Details may be obtained from the publisher. This NRSC Standard is considered to have International Standardization implication, but the International Electrotechnical Commission activity has not progressed to the point where a valid comparison between the NRSC Standard and the IEC document can be made. This Standard does not purport to address all safety problems associated with its use or all applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. Published by ©CONSUMER ELECTRONICS ASSOCIATION 2005 Technology & Standards Department 2500 Wilson Boulevard Arlington, VA 22201 ©NATIONAL ASSOCIATION OF BROADCASTERS 2005 Science and Technology Department 1771 N Street, NW Washington, DC 20036 All rights reserved Printed in U.S.A. Page i PLEASE! DON’T VIOLATE THE LAW! This document is copyrighted by CEA and NAB and may not be reproduced without permission. This document is distributed free of charge via the NRSC website at: http://www.nrscstandards.org Page ii Page 5 U.S. RBDS Standard ANNEXES A - Offset words to be used for group and block synchronization (normative) ........................................................... 72 B - Theory and implementation of the modified shortened cyclic code (informative)................................................. 73 C - Implementation of group and block synchronization using the modified shortened cyclic code (informative) ............................................................................................................................... 79 D - Program identification codes and Extended country codes (normative) ................................................................ 82 E - Character definition for Program Service name, Program Type Name, Radiotext and alphanumeric Radio paging (normative)........................................................................................................ 93 F - Program Type codes (normative) ........................................................................................................................... 97 G - Conversion between time and date conventions (informative) ............................................................................ 105 H - Specification of the ARI system (informative) ................................................................................................... 107 J - Language identification (normative).................................................................................................................... 108 K - RDS logo (informative) ...................................................................................................................................... 110 L - Open data registration (informative) ................................................................................................................... 111 M - Coding of Radio Paging (normative) .................................................................................................................. 118 N - Country codes and Extended country codes for countries outside the European Broadcasting Area (normative)................................................................................................... 154 P - Coding of MMBS Radio Paging, Data and In-House Application (informative)................................................. 159 Q - Emergency Alert System Open Data Application (informative).......................................................................... 180 R - In-Receiver Database System (I-RDS) File Structure (informative).................................................................... 186 S - List of Abbreviations (normative)......................................................................................................................... 205 T - Bibliography (informative)................................................................................................................................... 206 U - Open Data Application for Program Associated Data (normative)...................................................................... 207 Page 72 U.S. RBDS Standard ANNEX A (normative) Offset words to be used for group and block synchronization The offset words are chosen in such a way that the content in the offset register will not be interpreted as a burst of errors equal to or shorter than five bits when rotated in the polynomial shift register (see annex B). Only eight bits (i.e. d9 to d2) are used for identifying the offset words. The remaining two bits (i.e. d1 and d0 ) are set to logical level zero. The six offset words (A, B, C, C', D, E) of the table below are used for all applications. For MMBS applications an additional offset word E is used to maintain synchronization. Table A.1 Binary value Offset word d9 d8 d7 d6 d5 d4 d3 d2 d1 d0 A 0011111100 B 0110011000 C 0101101000 C' 1101010000 D 0110110100 E 1) 0000000000 The offset words are added (modulo-two) to the checkword c9 - c0 to generate the modified check-bits: c'9 - c'0 (see 2.3, Error protection). 1) Attention is drawn to the fact that, in the USA (see [15] of annex Q), offset word E (binary value = 0) is used in multiples of four blocks, when RDS and MMBS are simultaneously implemented. Offset word E must not be used in RDS implementations corresponding to this specification. Page 73 U.S. RBDS Standard ANNEX B (informative) Theory and implementation of the modified shortened cyclic code The data format described in this document uses a shortened cyclic block code, which is given the capability of detecting block-synchronization-slip by the addition (modulo-two) of chosen binary sequences (offset words, see annex A) to the check bits of each codeword [4, 6, 7]. B.1 Encoding procedure B.1.1 Theory A definitive description of the encoding of the information is given in 3.2. The code used is an optimum burst-error-correcting shortened cyclic code [5] and has the generator polynomial: g(x) = x10 + x8 + x7 + x5 + x4 + x3 + 1 Each block consists of 16 information bits and 10 check bits. Thus the block length is 26 bits. The 10-bit checkword of the basic shortened cyclic code may be formed in the usual way, i.e. it is the remainder after multiplication by xn-k (where n-k is the number of check bits, 10 here), and then division (modulo- two) by the generator polynomial g(x), of the message vector. 15 14 Thus if the polynomial m(x) = m15 x + m14 x + ... + m1 x + m0 (where the coefficients mn are 0 or 1), represents the 16-bit message vector, the basic code vector v(x) is given by: The transmitted code vector is then formed by the addition (modulo-two) of the 10-bit offset word, d(x) (see annex A) to the basic code vector v(x). Thus the transmitted code vector, c(x), is given by: 25 10 The code vector is transmitted m.s.b. first, i.e. information bits c25x to c10x , followed by modified 9 0 check bits c9'x to c0'x . Page 74 U.S. RBDS Standard The encoding process may alternatively be considered in terms of its generator matrix G which is derived from the generator polynomial. The 16 information bits are expressed as a 16 x 1 column matrix and multiplied by the generator matrix to give the information bits and check bits. The complete transmitted code
Recommended publications
  • Sample Induction Ceremony for Honors Membership in Lambda Pi Eta

    Sample Induction Ceremony for Honors Membership in Lambda Pi Eta

    Sample Induction Ceremony for Honors Membership in Lambda Pi Eta The following is a sample script for a Lambda Pi Eta induction ceremony. Please feel free to use it as a guide and adapt it to meet the individual needs of your chapter. Room Set-up: Chairs are arranged theater style with a center aisle. A table is in the front of the room with three candles. To the right is a podium for speakers and to the rear of the room is a table for refreshments. Greeters meet people at the door with a program and any other handouts. Faculty Advisor: I would like to begin by welcoming everyone to the Lambda Pi Eta (your chapter) Induction ceremony. First, it is my pleasure to introduce to you the chapter officers and our special guests (make a list of chapter officers and any special guests). President: The name Lambda Pi Eta is represented by the Greek letters L (lambda), P (pi), and H (eta) symbolizing what Aristotle described in his book Rhetoric as the three modes of persuasion: Logos meaning logic, Pathos relating to emotion, and Ethos defined as character credibility and ethics. The candle lighting ceremony will describe each of these Greek letters. Lambda Pi Eta was initiated by the students of the Department of Communication at the University of Arkansas and was then endorsed by the faculty and founder, Dr. Stephen A. Smith in 1985. The Speech Communication Association established Lambda Pi Eta as an affiliate organization and as the official national communication honor society for undergraduates in 1994.
  • The Use of Gamma in Place of Digamma in Ancient Greek

    The Use of Gamma in Place of Digamma in Ancient Greek

    Mnemosyne (2020) 1-22 brill.com/mnem The Use of Gamma in Place of Digamma in Ancient Greek Francesco Camagni University of Manchester, UK [email protected] Received August 2019 | Accepted March 2020 Abstract Originally, Ancient Greek employed the letter digamma ( ϝ) to represent the /w/ sound. Over time, this sound disappeared, alongside the digamma that denoted it. However, to transcribe those archaic, dialectal, or foreign words that still retained this sound, lexicographers employed other letters, whose sound was close enough to /w/. Among these, there is the letter gamma (γ), attested mostly but not only in the Lexicon of Hesychius. Given what we know about the sound of gamma, it is difficult to explain this use. The most straightforward hypothesis suggests that the scribes who copied these words misread the capital digamma (Ϝ) as gamma (Γ). Presenting new and old evidence of gamma used to denote digamma in Ancient Greek literary and documen- tary papyri, lexicography, and medieval manuscripts, this paper refutes this hypoth- esis, and demonstrates that a peculiar evolution in the pronunciation of gamma in Post-Classical Greek triggered a systematic use of this letter to denote the sound once represented by the digamma. Keywords Ancient Greek language – gamma – digamma – Greek phonetics – Hesychius – lexicography © Francesco Camagni, 2020 | doi:10.1163/1568525X-bja10018 This is an open access article distributed under the terms of the CC BY 4.0Downloaded license. from Brill.com09/30/2021 01:54:17PM via free access 2 Camagni 1 Introduction It is well known that many ancient Greek dialects preserved the /w/ sound into the historical period, contrary to Attic-Ionic and Koine Greek.
  • DRAFT Arabtex a System for Typesetting Arabic User Manual Version 4.00

    DRAFT Arabtex a System for Typesetting Arabic User Manual Version 4.00

    DRAFT ArabTEX a System for Typesetting Arabic User Manual Version 4.00 12 Klaus Lagally May 25, 1999 1Report Nr. 1998/09, Universit¨at Stuttgart, Fakult¨at Informatik, Breitwiesenstraße 20–22, 70565 Stuttgart, Germany 2This Report supersedes Reports Nr. 1992/06 and 1993/11 Overview ArabTEX is a package extending the capabilities of TEX/LATEX to generate the Perso-Arabic writing from an ASCII transliteration for texts in several languages using the Arabic script. It consists of a TEX macro package and an Arabic font in several sizes, presently only available in the Naskhi style. ArabTEX will run with Plain TEXandalsowithLATEX2e. It is compatible with Babel, CJK, the EDMAC package, and PicTEX (with some restrictions); other additions to TEX have not been tried. ArabTEX is primarily intended for generating the Arabic writing, but the stan- dard scientific transliteration can also be easily produced. For languages other than Arabic that are customarily written in extensions of the Perso-Arabic script some limited support is available. ArabTEX defines its own input notation which is both machine, and human, readable, and suited for electronic transmission and E-Mail communication. However, texts in many of the Arabic standard encodings can also be processed. Starting with Version 3.02, ArabTEX also provides support for fully vowelized Hebrew, both in its private ASCII input notation and in several other popular encodings. ArabTEX is copyrighted, but free use for scientific, experimental and other strictly private, noncommercial purposes is granted. Offprints of scientific publi- cations using ArabTEX are welcome. Using ArabTEX otherwise requires a license agreement. There is no warranty of any kind, either expressed or implied.
  • D Igital Text

    D Igital Text

    Digital text The joys of character sets Contents Storing text ¡ General problems ¡ Legacy character encodings ¡ Unicode ¡ Markup languages Using text ¡ Processing and display ¡ Programming languages A little bit about writing systems Overview Latin Cyrillic Devanagari − − − − − − Tibetan \ / / Gujarati | \ / − Armenian / Bengali SOGDIAN − Mongolian \ / / Gurumukhi SCRIPT Greek − Georgian / Oriya Chinese | / / | / Telugu / PHOENICIAN BRAHMI − − Kannada SINITIC − Japanese SCRIPT \ SCRIPT Malayalam SCRIPT \ / | \ \ Tamil \ Hebrew | Arabic \ Korean | \ \ − − Sinhala | \ \ | \ \ _ _ Burmese | \ \ Khmer | \ \ Ethiopic Thaana \ _ _ Thai Lao The easy ones Latin is the alphabet and writing system used in the West and some other places Greek and Cyrillic (Russian) are very similar, they just use different characters Armenian and Georgian are also relatively similar More difficult Hebrew is written from right−to−left, but numbers go left−to−right... Arabic has the same rules, but also requires variant selection depending on context and ligature forming The far east Chinese uses two ’alphabets’: hanzi ideographs and zhuyin syllables Japanese mixes four alphabets: kanji ideographs, katakana and hiragana syllables and romaji (latin) letters and numbers Korean uses hangul ideographs, combined from jamo components Vietnamese uses latin letters... The Indic languages Based on syllabic alphabets Require complex ligature forming Letters are not written in logical order, but require a strange ’circular’ ordering In addition, a single line consists of separate
  • The Arabi System — TEX Writes in Arabic and Farsi

    The Arabi System — TEX Writes in Arabic and Farsi

    The Arabi system | ] ¨r` [ A\ TEX writes in Arabic and Farsi Youssef Jabri Ecole´ Nationale des Sciences Appliqu´ees, Oujda, Morocco yjabri (at) ensa dot univ-oujda dot ac dot ma Abstract In this paper, we will present a newly arrived package on CTAN that provides Arabic script support for TEX without the need for an external pre-processor. The Arabi package adds one of the last major multilingual typesetting capabilities to Babel by adding support for the Arabic ¨r and Farsi ¨FCA languages. Other languages using the Arabic script should also be more or less easily imple- mentable. Arabi comes with many good quality free fonts, Arabic and Farsi, and may also use commercial fonts. It supports many 8-bit input encodings (namely, CP-1256, ISO-8859-6 and Unicode UTF-8) and can typeset classical Arabic poetry. The package is distributed under the LATEX Project Public License (LPPL), and has the LPPL maintenance status \author-maintained". It can be used freely (including commercially) to produce beautiful texts that mix Arabic, Farsi and Latin (or other) characters. Pl Y ¾Abn Tn ®¤ Tr` ¤r Am`tF TAk t§ A\ ¨r` TEC .¤r fOt TEX > < A\ Am`tFA d¤ dnts ¨ n A\ (¨FCA ¤ ¨r)tl Am`tF TAk S ¨r` TEC , T¤rm rb Cdq tmt§¤ ¯m ¢k zymt§ A\n @h , T§db @n¤ Y At§ ¯ ¢ Y TAR . AARn £EA A \` Am`tF® A ¢± ¾AO ¾AA ¨r` dq§ . Tmlk ¨ ¤r AkJ d§dt ¨CA A` © ¨ ¨t ªW d Am`tF ¢nkm§ Am Am`tF¯ ­r ªW Tmm ¯¤ ¨A ¨r` , A\n TbsnA A w¡ Am .
  • The Bylaws of Phi Theta Kappa, Beta Pi Rho Chapter

    The Bylaws of Phi Theta Kappa, Beta Pi Rho Chapter

    The Bylaws of Phi Theta Kappa, Beta Pi Rho Chapter CHAPTER 1. Name of Chapter ​ The name of this chapter in Phi Theta Kappa shall be distinguished as Beta Pi Rho. CHAPTER 2. Purpose ​ The purpose of the Beta Pi Rho Chapter in Phi Theta Kappa at Portland Community College, Southeast Campus, shall be the promotion of scholarship, the development of leadership and service, and the cultivation of fellowship among exemplary students of this college. CHAPTER 3. Membership ​ Section 1. Types of membership in the Chapter shall consist of member, provisional member, alumni member, ​ and honorary member as defined in Article IV, Section I, of the Phi Theta Kappa Constitution and ​ Bylaws.* ​ A. Member. In addition to meeting membership eligibility requirement as stated in Article IV and Chapter 1 of ​ the Phi Theta Kappa Constitution and Bylaws,* each candidate for membership must have completed 12 ​ ​ credit hours of associate degree course work, with a Grade Point Average of 3.5 on a 4.0 scale, and adhere to the school conduct code and possess recognized qualities of citizenship. Grades for courses completed at other institutions can be considered when determining membership eligibility. A cumulative Grade Point Average of 3.0 must be maintained to remain in good standing. Failure to maintain the required cumulative Grade Point Average will result in the member being removed from good standing as stated in the Phi ​ Theta Kappa Constitution and Bylaws, * Chapter 1, Section 3. Failure to meet good standing requirements ​ as stated in the Phi Theta Kappa Constitution and Bylaws* will cause membership and all of membership ​ ​ privileges to be revoked.
  • ΠΣΑ Pi Sigma Alpha

    ΠΣΑ Pi Sigma Alpha

    Pi Sigma Alpha ΠΣΑ The National Political Science Honor Society Pi Sigma Alpha, Psi Omega Chapter University of California, San Diego 9500 Gilman Drive 0077 Mail Box D-30 La Jolla, CA 92093-0077 An Invitation to Join Pi Sigma Alpha Thank you for your interest in the University of California, San Diego’s chapter of Pi Sigma Alpha, the national Political Science Honor Society. The chapter recognizes majors in political science who have demonstrated superior scholarship. The chapter seeks to provide its members with access to professionals in the field of political science and to the faculty at UCSD as well as opportunities to interact with fellow honors students in the major. The chapter particularly solicits membership from individuals who will be active and play a leading role in the chapter’s programs. Due to the reputation of Pi Sigma Alpha as a respected honor society within the field of Political Science, the members of the Psi Omega Chapter have established a high standard of academic achievement within the Political Science major as a prerequisite for membership. Specifically, to be eligible for membership in UCSD’s Psi Omega Chapter of Pi Sigma Alpha, a student must have: •Completed at least seven (7) political science courses, including at least three (3) upper division courses (transfer students must have completed at least two (2) of the three upper division courses at the University of California, San Diego); •Maintained no less than a 3.60 GPA in all political science courses taken at UCSD; and •Declared political science as a major of study or declared a concentration in political science within an interdisciplinary major such as international studies at the University of California, San Diego.
  • The Ritual Of

    The Ritual Of

    The Ritual of The International Honor Society for Professions in Technology Promoting Excellence in Preparation and Excellence In Practice CONTENTS Foreword iv Preliminaries v Arrangement of the Initiation vii Glossary viii THE RITUAL The Honorable BASILEUS Presides 1 PHYLAX Guards Portal 1 HEGEMON Presents Apprentices 3 HISTORIOGRAPHOS Reviews Record 5 TEXNIKH, the Ideal of Skill 7 PRAGMATEIA, the Professional Ideal 8 EXETASIS, the Technologist’s Ideal 10 HISTORIOGRAPHOS, Symbolism of Triangle 13 BASILEUS Administers Obligation 14 TRUSTEE Reports on the Honorary 15 BASILEUS Adjourns the Meeting 19 iii Copyright 1934,1943,1963,1976,1983, 1995, 2004 by EPSILON PI TAU This ritual is the property of EPSILON PI TAU, Incorporated. Its availability on the Epsilon Pi Tau website in no way implies permission for it use, in part or its entirety, in situations not authorized by the Board of Directors. Edition of 2004 (Microsoft Works Font: Palatino Size 14pt) This revision is built on the excellent 1995 edition that was produced by a FOCUS GROUP at Bowling Green State University: Dr. G. R. Horton (chair), Norina Columbaro, Dan Engstrom, Dr. Larry Hatch, and Dr. Jerry Streichler. Their work is honored in this volume that also has modifications that respond to the rapid changes in technology and society and in the academic programs, organizations and professions that Epsilon Pi Tau serves. The Board of Directors listed below, along with former Directors Kenneth Delucca, Donald Lux and Lester Russell constituted a revision committee of the whole. Final changes and improvements were made based on feedback from a number of chapters that tested the draft material in their initiation ceremonies International Office Board of Directors Technology Building Dr.
  • Proto-Elamite

    Proto-Elamite

    L2/20­192 2020­09­21 Preliminary proposal to encode Proto­Elamite in Unicode Anshuman Pandey [email protected] pandey.github.io/unicode September 21, 2020 Contents 1 Introduction 2 2 Overview of the Sign Repertoire 3 2.1 Sign names . 4 2.2 Numeric signs . 4 2.3 Numeric signs with extended representations . 5 2.4 Complex capacity signs . 6 2.5 Complex graphemes . 7 2.6 Signs in compounds without independent attestation . 10 2.7 Alternate or variant forms . 11 2.8 Scribal designs . 11 3 Proposed Encoding Model 12 4 Proposed Characters 13 4.1 Numeric signs . 13 4.2 General ideographic signs . 17 5 Characters Not Suitable for Encoding 110 6 References 110 7 Acknowledgments 111 1 Preliminary proposal to encode Proto­Elamite in Unicode Anshuman Pandey 1 Introduction The term ‘Proto­Elamite’ refers to a writing system that was used at the beginning of the 3rd millenium BCE in the region to the east and southeast of Mesopotamia, known as Elam, which corresponds to the eastern portion of present­day Iran. The name was assigned by the French epigraphist Jean­Vincent Scheil in the early 20th century, who believed it to be the predecessor of a ‘proper’ Elamite script, which would have been used for recording the Elamite language, simply on account of the location of the tablets at Susa, which was the capital city of Elam. While no ‘proper’ descendent of the script has been identified, scholars continue to use the name ‘Proto­Elamite’ as a matter of convention (Dahl 2012: 2). Proto­Elamite is believed to have been developed from an accounting system used in Mesopotamia, in a manner similar to the development of ‘Proto­Cuneiform’.
  • The TIFAX XM 11 Teletext Decoder

    The TIFAX XM 11 Teletext Decoder

    B183 The TIFAX XM 11 Teletext Decoder 100 too CEEFAX Tue 31 may 100 ORACLE 100 WedOlJun ITV 19.14i11 c ELF FiZ1 M21111 &Di I ITN MAIN INDEX 200 TELEVISION NEWS HEADLINES 101 FULL INDEX HEADLINES. Nous 201 TV INDEX. 120 NEWS IN DETAIL 102-114 Sport 202 171' LONDON 777 HEWSFLASH 150 C - P 197 Business 203 ITV REGIONS 150 WEATHER 115 R - Z The Pound 248 BBC TY 333 FT Index 249 FINANCE HEADLINES .120 For the CEEFAX FT INDEX 125 "Latest Pages^ WEATHER MAP..... 600 CONSUMER PAGES 500 serv.ce, leave LONDON. 701 PRICES 501 SPORT HEADLINES ... 130 your set on 190 REGIONS 1508 BIRTHDAYS 506 YOUR STARS 507 TRAVEL NEWS..... 116-119 TRAVEL INDEX....400 .0414 LONDON... 704 SPECIAL SECTION INDEX LONDON 700 CONSUMER NEWS .. REGIONS ISO 141 ON THE BATH AHD WHATS ON ...... PRICES GUIDE 142 .300 TECHNICAL 450 WEST SHOW 700 RECIPE 143 PACES 171-1/5 COMPLETE INDEX 19B FOR CHILDREN 144 'ARMING 147 BBC Ceefax Index IBA Oracle Index CEEFAX 116 Tue 31 May 20 35r53 ORACLE 51i Wed01Jun 1Tv 19 A _ 511 fir2t 5FOPIEIC ODIFFTIBREAkinEPSEI 1LP PDS BREAK THE HIDDEN CODE 1st JUNE MI Road works have closed the south- bound side exit link at Junction 14, PEG colours A II it II 5 II Newport Pagnell, and one or store lanes T i''Ir4IIID;)46Cg22Eis any four Code Pegs in the area. Those wishing to head for 'maybe more than one of each colour) Newport Pagnell should leave the motor --e KEY PEGS -chow the Code Breaker's -way at Junction 15, via the 2508, 05 ,,ess, after each turn and 4422 ,-/light colour SCODE PEGS* KEY PEGS* A:1 Gas board son have the road up at Int positinf Stansted, Essex 115111111 x X H m =Right colour 21 H • x ..crseguards Parade, London: a Beating wrong position 3M IM ■ H • the Retreat ceresony uill ..an 411 Isiown congestion in the Whitehall area ,,on X eVronq colour.
  • Saa5x9x Family Economy Teletext and TV Microcontrollers

    Saa5x9x Family Economy Teletext and TV Microcontrollers

    INTEGRATED CIRCUITS DATA SHEET SAA5x9x family Economy teletext and TV microcontrollers Preliminary specification 1998 Dec 14 Supersedes data of 1997 Jul 07 File under Integrated Circuits, IC02 Philips Semiconductors Preliminary specification Economy teletext and TV microcontrollers SAA5x9x family CONTENTS 9.3 East/West selection 9.4 National option characters 1 FEATURES 9.5 The twist attribute 1.1 General 9.6 Language group identification 1.2 Microcontroller 9.7 525-line operation 1.3 Teletext acquisition 9.8 On-Screen Display characters 1.4 Teletext Display 9.9 Control characters 1.5 Additional features of SAA529xA devices 9.10 Quadruple width display (SAA549x) 1.6 Additional features of SAA549x devices 9.11 Page attributes 9.12 Display modes 2 GENERAL DESCRIPTION 9.13 On-Screen Display boxes 2.1 Device masking history 9.14 Screen colour 3 ORDERING INFORMATION 9.15 Redefinable colours (SAA549x) 4 QUICK REFERENCE DATA 9.16 Cursor 9.17 Other display features 5 BLOCK DIAGRAM 9.18 Display timing 6 PINNING INFORMATION 9.19 Horizontal timing 6.1 Pinning 9.20 Vertical timing 6.2 Pin description 9.21 Display position 9.22 Clock generator 7 FUNCTIONAL DESCRIPTION 9.23 Reset signal 7.1 Microcontroller 10 CHARACTER SETS 7.2 80C51 features not supported 7.3 Additional features 10.1 Pan-European 7.4 Microcontroller interfacing 10.2 Cyrillic 10.3 Greek/Turkish 8 TELETEXT DECODER 10.4 Arabic/English/French 8.1 Data slicer 10.5 Thai 8.2 Acquisition timing 10.6 Arabic/Hebrew 8.3 Teletext acquisition 10.7 Iranian 8.4 Rolling headers and time 11 LIMITING
  • Technical Advisory Group on Machine Readable Travel Documents (Tag/Mrtd) Twentieth Meeting

    Technical Advisory Group on Machine Readable Travel Documents (Tag/Mrtd) Twentieth Meeting

    TAG/MRTD/20-WP/17 6/09/11 English Only International Civil Aviation Organization WORKING PAPER TECHNICAL ADVISORY GROUP ON MACHINE READABLE TRAVEL DOCUMENTS (TAG/MRTD) TWENTIETH MEETING Montréal, 7 to 9 September 2011 Agenda Item 2: Activities of the NTWG Agenda Item 2.9: Transliteration Rules (Arabic) TRANSLITERATION RULES (ARABIC) (Presented by the NTWG) 1. INTRODUCTION 1.1 The purpose of the working paper is to inform the TAG of the progress made on the recommended transliteration of Arabic national characters for Doc Doc 9303, Machine Readable Travel Documents , Part 1 — Machine Readable Passports , Volume1, Section IV, Appendix 9. These recommended transliterations apply to the MRZ only. 2. BACKGROUND 2.1 Transliteration of Arabic characters applies mainly to the name of the holder of the MRTD, and is critical for determining the true identity of the holder. At present, Arabic names are transcribed (phonetically) to Latin characters on an ad-hoc basis and this compromises identity management. 2.2 The only true and reliable source of identification is the original form of the name in Arabic characters. Thus, any transliteration scheme must preserve the original form of the name. 2.3 It would be advantageous to countries using the Arabic script if encoding the name in the MRZ led to machine reading producing the original form of the name in Arabic. This would allow these countries to gain the benefit of machine reading without having to deal with an intermediate form of the name as an inaccurate Latin transcription. 2.4 There is no known existing transliteration scheme for Arabic script that is suitable for the MRZ.