Features of the "Kliment Std" Font V. 4.5, 2014 Kliment Std the Companion to Our Free «Romancyrillic Std» Font – Especially for Slavic Medievalists
Total Page:16
File Type:pdf, Size:1020Kb

Load more
Recommended publications
-
+1. Introduction 2. Cyrillic Letter Rumanian Yn
MAIN.HTM 10/13/2006 06:42 PM +1. INTRODUCTION These are comments to "Additional Cyrillic Characters In Unicode: A Preliminary Proposal". I'm examining each section of that document, as well as adding some extra notes (marked "+" in titles). Below I use standard Russian Cyrillic characters; please be sure that you have appropriate fonts installed. If everything is OK, the following two lines must look similarly (encoding CP-1251): (sample Cyrillic letters) АабВЕеЗКкМНОопРрСсТуХхЧЬ (Latin letters and digits) Aa6BEe3KkMHOonPpCcTyXx4b 2. CYRILLIC LETTER RUMANIAN YN In the late Cyrillic semi-uncial Rumanian/Moldavian editions, the shape of YN was very similar to inverted PSI, see the following sample from the Ноул Тестамент (New Testament) of 1818, Neamt/Нямец, folio 542 v.: file:///Users/everson/Documents/Eudora%20Folder/Attachments%20Folder/Addons/MAIN.HTM Page 1 of 28 MAIN.HTM 10/13/2006 06:42 PM Here you can see YN and PSI in both upper- and lowercase forms. Note that the upper part of YN is not a sharp arrowhead, but something horizontally cut even with kind of serif (in the uppercase form). Thus, the shape of the letter in modern-style fonts (like Times or Arial) may look somewhat similar to Cyrillic "Л"/"л" with the central vertical stem looking like in lowercase "ф" drawn from the middle of upper horizontal line downwards, with regular serif at the bottom (horizontal, not slanted): Compare also with the proposed shape of PSI (Section 36). 3. CYRILLIC LETTER IOTIFIED A file:///Users/everson/Documents/Eudora%20Folder/Attachments%20Folder/Addons/MAIN.HTM Page 2 of 28 MAIN.HTM 10/13/2006 06:42 PM I support the idea that "IA" must be separated from "Я". -
Old Cyrillic in Unicode*
Old Cyrillic in Unicode* Ivan A Derzhanski Institute for Mathematics and Computer Science, Bulgarian Academy of Sciences [email protected] The current version of the Unicode Standard acknowledges the existence of a pre- modern version of the Cyrillic script, but its support thereof is limited to assigning code points to several obsolete letters. Meanwhile mediæval Cyrillic manuscripts and some early printed books feature a plethora of letter shapes, ligatures, diacritic and punctuation marks that want proper representation. (In addition, contemporary editions of mediæval texts employ a variety of annotation signs.) As generally with scripts that predate printing, an obvious problem is the abundance of functional, chronological, regional and decorative variant shapes, the precise details of whose distribution are often unknown. The present contents of the block will need to be interpreted with Old Cyrillic in mind, and decisions to be made as to which remaining characters should be implemented via Unicode’s mechanism of variation selection, as ligatures in the typeface, or as code points in the Private space or the standard Cyrillic block. I discuss the initial stage of this work. The Unicode Standard (Unicode 4.0.1) makes a controversial statement: The historical form of the Cyrillic alphabet is treated as a font style variation of modern Cyrillic because the historical forms are relatively close to the modern appearance, and because some of them are still in modern use in languages other than Russian (for example, U+0406 “I” CYRILLIC CAPITAL LETTER I is used in modern Ukrainian and Byelorussian). Some of the letters in this range were used in modern typefaces in Russian and Bulgarian. -
2019 Key Stage 2 English Grammar, Punctuation and Spelling
2019 national curriculum tests Key stage 2 English grammar, punctuation and spelling Paper 1: questions First name Middle name Last name Date of birth Day Month Year School name DfE number H00030A0132 [BLANK PAGE] Please do not write on this page. Page 2 of 32 H00030A0232 Instructions Questions and answers There are different types of question for you to answer in different ways. The space for your answer shows you what type of answer is needed. Write your answer in the space provided. Do not write over any barcodes. Multiple-choice answers For some questions, you do not need to do any writing. Read the instructions carefully so that you know how to answer each question. Short answers Some questions are followed by a line or a box. This shows that you need to write a word, a few words or a sentence. Marks The number under each line at the side of the page tells you the number of marks available for each question. You should work through the booklet until you are asked to stop. Work as quickly and as carefully as you can. If you finish before the end, go back and check your work. You have 45 minutes to answer the questions in this booklet. H00030A0332 Page 3 of 32 G004559 – 4 October 2018 10:40 AM – Version 5 1 Tick the sentence that must end with a question mark. Tick one. The teacher asked them what they were doing I wonder what time the next train arrives Did she play tennis on your team last year He asked if he could use my pen 1 mark G002877 – 4 October 2018 10:36 AM – Version 1 2 Draw a line to match each word to the correct suffix. -
5892 Cisco Category: Standards Track August 2010 ISSN: 2070-1721
Internet Engineering Task Force (IETF) P. Faltstrom, Ed. Request for Comments: 5892 Cisco Category: Standards Track August 2010 ISSN: 2070-1721 The Unicode Code Points and Internationalized Domain Names for Applications (IDNA) Abstract This document specifies rules for deciding whether a code point, considered in isolation or in context, is a candidate for inclusion in an Internationalized Domain Name (IDN). It is part of the specification of Internationalizing Domain Names in Applications 2008 (IDNA2008). Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc5892. Copyright Notice Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. -
Avar Romanization Handwriting
Checked for validity and accuracy – June 2019 ROMANIZATION OF AVAR BGN/PCGN 2011 System The BGN/PCGN system for Avar is designed for use in romanizing names written in the Avar Cyrillic alphabet. Avar is a consonant-rich north-eastern Caucasian language, spoken principally in Russia’s republic of Dagestan. It has been written in a modified Cyrillic script since 1938 and, as other Caucasian languages, features glottalised consonants, and though these are not marked with a uniform marker in Avar Cyrillic, an apostrophe denotes the glottalised form of consonants in this romanization table. Avar italics/ Avar Romanization handwriting 1. A а А а a 2. Б б Б б b 3. В в В в w 4. Г г Г г g 5. Гъ гъ Гъ гъ gh 6. Гь гь Гь гь h 7. ГӀ гӀ ГӀ гӀ ġ 8. Д д Д д d 9. Е е Е е e, yeNote 1 10. Ё ё Ё ё ë 11. Ж ж Ж ж zh 12. З з З з z 13. И и И и i 14. Й й Й й y 15. К к К к k 16. Къ къ Къ къ q’ 1 Avar italics/ Avar Romanization handwriting 17. Кь кь Кь кь tl’ 18. КӀ кӀ КӀ кӀ k’ 19. Л л Л л l 20. Лъ лъ Лъ лъ lh 21. ЛӀ лӀ ЛӀ лӀ tl 22. М м М м m 23. Н н Н н n 24. О о О о o 25. П п П п p 26. Р р Р р r 27. -
Gt Desv H Vkwq Bfum
gt desVh vkWQ bfUM;k ¼laln vf/kfu;e la[;k&35- lu~ 2002 ds vUrZxr xfBr½ gt desVh vkWQ bfUM;k dh iz’kklfud fjiksZV lu~ 2012&2013- ¼gt desVh vf/kfu;e 2002 ds fu;e 28¼1½ esa fufnZ"V micU/kksa ds vuqlkj 1 vizSy 2012 ls 31 ekpZ 2013 rd½ 1- gt desVh vf/kfu;e ¼dzekad 35½ lu~ 2002] 5 fnlEcj 2002 dks izo`Rr gqvk] ns[ksa] vf/klwpuk dzekWsd ,e-¼gt½&1181@33@99] fnukad % 5 fnlEcj] 2002- 2- gt desVh vkWQ bfUM;k dh lajpuk] gt desVh vf/kfu;e dh /kkjk la[;k 35] lu~ 2002 ds vUrZxr gqbZ] ns[ksa] lwpuk dzekWd ,e-¼gt½&1183@74@2009] fnukad 12 tuojh] 2010-tks fuEuor gS%& v½ vf/kfu;e dh /kkjk ¼4½ dh mi/kkjk ¼i½ ds v/khu ukfer lnL; I½ feLVj eksgEen vljk:y gd laln lnL; ¼yksd lHkk½ ns[ksa lwpuk dzekWd ,e- ¼gt½&1183@74@2009] fnukad 12 tuojh 2010- II½ feLVj lS;n “kkguokt gqlsu laln lnL; ¼yksd lHkk½ ns[ksa] lwpuk dzekWd ,e- ¼gt½&1183@74@2009] fnukad 12 tuojh 2010- III½ feLVj egewn ,- enuh laln lnL; ¼jkT; lHkk½ ns[ksa] lwpuk dzekWd ,e- ¼gt½&1183@74@2009] fnukad 12 tuojh 2010- ¼feLVj egewn ,- enuh dk dk;Zdky iw.kZ½ IV½ feLVj lyhe vUlkjh] laln lnL; ¼jkT; lHkk½ ns[ksa] lwpuk dzekWd ,e- ¼gt½&1183@35@2012] fnukad 14 twu] 2012- ¼c½ vf/kfu;e dh /kkjk ¼4½ dh mi/kkjk ¼ii½ ds v/khu fuokZfpr lnL; V½ eqQ~rh uthj vgen dkleh] ¼tksu&I½ lnL; tEew ,oa d”ehj jkT; gt lfefrA VI½ feLVj eksgEen bfy;kl gqlsu mQZ lksuw ckcw ¼tksu&II½ lnL; fcgkj jkT; gt lfefrA 1 VII½ MkW- lyhe jkt ¼tksu&III½ lnL; NRrhlx<+ jkT; gt lfefrA VIII½ MkW- Qqvn gyhe ¼tksu&IV½ lnL; if”pe caxky jkT; gt lfefrA IX½ fjDr&tksu&V. -
For the Annotation of Titlo Diacritic
Irina LOBJANIDZE Associate Professor Ilia State University Tbilisi, Georgia For the annotation of Titlo Diacritic Abstract: The paper describes different levels of annotation used in the Corpus of Modern, Middle and Old Georgian Texts. Aiming at building a new, extensive and representative tool for Georgian language the Corpus was compiled under the financial support of the Shota Rustaveli National Science Foundation and the Ilia State University (AR/266/1-31/13). In particular, the Corpus of Georgian language is envisaged as collecting a substantial amount of data needed for research. The scope and representativeness of texts included as well as free accessibility to it makes the corpus one of the most necessary tools for the study of different texts in Modern, Middle and Old Georgian (see, http://corpora.iliauni.edu.ge/). The corpus consists of different kind of texts, mainly: a) Manuscript- based publications; b) Reprints; c) Previously unpublished manuscripts and; d) Previously published manuscripts and covers Modern, Middle and Old Georgian. The paper presents the research area, the design and structure and applications related to the compilation of the corpus, in particular, different levels of annotation as meta-data, structural mark-up and linguistic annotation at word-level, especially, from the viewpoint of Titlo Diacritic. This paper is structured as follows: Section 1 includes background and research questions; Section 2 presents a methodological approach and briefly summarizes its theoretical prerequisites; Section 3 includes the findings and hypothesis, which refers generally to the differences between the annotation of Modern and Old Georgian texts; and Section 4 presents the answers to the research questions. -
Record Las A
- 6 - 4 , . Case; 1. Ii In the case Of a library that ,does not use' Library 1 . made to,descripl of tongr9ss,..ciall numbers, it would be appropriate.to request.a unit card from OCLC at the time the book record las a not that the LC card-number began send Wily the b: was oraered,,prb'viding to be part of ti with a "7"1- If the LC card number Coes'not have- an -1- the box in the : initial P7", the book would te ocesSed according. card (Fig,. 8):. to 'the 'library's present cataloging procedures. r Case 2. IJ PermanentRecOr'ds at CrIC modifications t( Information received on punch cards from Members' 'ion into the uf will be stored in the.00LC master A record wi,1-1, u-se the brgwn 'be kept kqd.lolding library -of each "book cataloged; 4 -Case3. WI these records to include the additions or changes holdings statemo requested by a Member. Therefore,;libraries need tc Call numPer,,tho report an addition or change. -to ULC only Once. card as Fell" as t Four Requisition Procedures . -Case-4. Member library-1 ioned above, there are four basic call As holdings as- not= number %stems, each fiaving different request procItiures. lib& an will As eachf these procedures is explained, certain options . card-a ell as will be discussed. These op, -ons'permit each klember to alter the cataloging and ,c 11 number to satisfy its Usesof LI .own requirements. class mb r,su: the,altern to c: ,On unit Ards, as acted in .Figure if, LC call labeled "LITERA' numbers or Dewey classtimbersare located in a 22-position area on the bottom g that is called the "user's option arlea"iVlibrary- ay-insert information in this- space on cards*Tn catalog packs. -
Proposal to Encode Combining Half Marks Used for Cyrillic Supralineation in Unicode
Proposal to Encode Combining Half Marks Used for Cyrillic Supralineation in Unicode Aleksandr Andreev* Yuri Shardt Nikita Simmons PONOMAR PROJECT Abstract A Proposal to add two additional characters to the Combining Half Marks block of Unicode to be used for the correct presentation of supralineation in Church Slavonic texts. 1 Introduction e Cyrillic writing system used to record the Church Slavonic language uses the character titlo (Slavonic: ті́тло) as a combining mark, most oen placed over a single character. e placement of this mark has several uses. First, it may be used to indicate that the leer or group of leers are to be interpreted as a numeral (e.g., а҃ = 1, ка҃ = 21, рк҃а = 121). Second, it may be used to indicate that a leer or group of leers are missing from a word, which is thus an abbreviation (e.g., цр҃ь = ца́рь, king). Finally, it may be used to indicate a nomen sacrum, an abbreviation for writing divine names (e.g., бг҃ъ = Бо́гъ, God vs. бо́гъ, a false deity). In the Unicode standard, the titlo has been encoded as U+0483, Combining Cyrillic Titlo. In several instances, a titlo may occur over two or more leers. First, this usage is evident in iconographic inscriptions. For example, in iconography, one finds the inscription МРѲ Ꙋ (a Slavonic rendition of the Greek Μήτηρ του Θεού, Mother of God) or ІСХ С (Іисꙋ съ́ Хрїсто́съ, Jesus Christ). One may also find inscriptions where the titlo balances over more than two leers, for example цр︮ ь︦ ︯ дв︮ д︦ ъ︦ ︯ (Ца́рь Даві́дъ, King David), as can be seen in Figure 4. -
ISO/IEC JTC1/SC2/WG2 N4xxx L2/12-Xxx
ISO/IEC JTC1/SC2/WG2 N4xxx L2/12-xxx 2012-01-27 Universal Multiple-Octet Coded Character Set International Organization for Standardization Organisation Internationale de Normalisation Международная организация по стандартизации Doc Type: Working Group Document Title: Revised proposal for encoding the Old Permic script in the SMP of the UCS Source: UC Berkeley Script Encoding Initiative (Universal Scripts Project) Authors: Michael Everson Status: Liaison Contribution Action: For consideration by JTC1/SC2/WG2 and UTC Replaces: N1687 (1998-01-18), N1947 (1999-01-29), N4177 (2012-01-24) Date: 2012-01-27 1. Introduction. The Old Permic script was devised in the 14th century by Russian missionary Stefan of Perm (fl. 1373–1395), and was used to write the Uralic languages Komi and Komi-Permyak. Its model was based on the Greek and Cyrillic alphabets (as can be seen from the order of the letters) but many of the glyphs were taken from the “Tamga signs”, used in indigenous Komi religious practices; in this way Stefan made a link between traditional signs, which had much to do with the self-identity of the Komi, and Christian traditions. In addition to writing Komi, the script was used cryptographically to write Russian, since it was unknown to most readers of Russian; this explains a number of the extensions made at the end of the alphabet. 2. Processing. Old Permic is a simple, caseless, alphabetic script, read from left to right in horizontal lines running from top to bottom. Several combining diacritics are attested in use in Old Permic. In the table, EF U+1036B and HA U+1036C are given with glyphs which are not the most commonly found ones. -
Old Cyrillic (Serbian) Keyboard Layout (V0.36)
Old Cyrillic (Serbian) keyboard layout (v0.36) a) Plain, Shift, and ⌥/AltGr state 1 2 3 4 5 6 7 8 9 0 Ѣ Ꙓ ! ⁓ " ” ⸫ ҂ \ ◌⃝ ⁜ ◌҈ ◌̆ ◌҉ / ◌꙰ ( ◌꙱ ) ◌꙲ Ѡ Ѿ ? ⹉ ▲ ◌҇ ZWJ ѣ ꙓ ◌҃ ~ ◌̏ “ ⁖ ⁝ ⁘ ⁞ ⸭ ⹃ ◌҅ ‿ ◌҆ ◌҆̑ ◌̑ [ ◌̀ ] ѡ ѿ ◌́ ◌҄ Ѫ Ѭ Ѧ Ѩ Е Ѥ Р Т Ѳ З Ꙁ У Ꙋ И І О П Ѱ Ш * Ю Ꙉ ѫ ѭ ѧ ѩ е ѥ р = т ѳ з ꙁ у ꙋ и і о Ꙩ п ѱ ш ꙳ ю ꙉ А Ꙗ С > Д Ф ‖ Г Ґ Х ’ Ы Ї К Ѯ Л Ч » Щ + Ж Џ а ꙗ с < д ф | г ґ х ‘ ы ї к ѯ л ◌̅ ч « щ ✠ ж џ SHY ◌҇ ◌҆̑ Ѕ Ꙃ ъ ⸯ Ц — В Ѵ Б ⁒ Н Ꙟ М ◌︮ ; ◌︦ : ◌︯ _ NB- ▲ ◌҆̑ ѕ ꙃ ь ꙿ ц – в ѵ б ꙾ н ꙟ м ◌꙯ , ⸴ . · - Shift + NBSP ZWSP Shift ⌥/AltGr Space NNBSP plain ⌥/AltGr b) after deadkey (“extra” characters/variants) 1 2 3 4 5 6 7 8 9 0 ∻ ≁ ◌̋ ⸪ ※ { } Ѽ ε ◌̃ ∽ ◌̈ ჻ ⸬ ⁙ ◌̇ ◌̂ ◌᷀ ѽ ◌᷁ ʼ Ꙛ Ꙙ Ꙝ Є Э Й Ꙇ Ѻ Ꙕ ꙛ ꙙ ꙝ є э й ꙇ ѻ ꙕ Я Σ 〉 Ꙣ Ꙑ Ꙥ Ҁ † α я 〈 ꙣ γ ꙑ ꙥ ◌̿ ҁ ☦ Ꙅ Ꙡ Ѷ Ҥ Ꙧ ◌︢ ; ◌︦ ◌︣ ꙅ ꙏ ◌͘ ꙡ ѷ ҥ ꙧ ◌͠◌ • · с) after deadkey (superscripts and combining liturgical symbols) 1 2 3 4 5 6 7 8 9 0 ◌ⷺ ◌̄ ◌᷸ ◌᷷ ◌᷶ ◌͘ ◌᷹ ◌ꙻ ◌ꙴ ◌ⷾ ◌ⷿ ◌ⷽ ◌ⷷ ◌ꚟ ◌ⷬ ◌ⷮ ◌ⷥ ◌ⷥ ◌ꙷ ◌ⷹ ◌ꙵ ◌ꙶ ◌ⷪ ◌ⷫ ◌ⷲ ◌ⷻ ◌ⷸ ◌ꙶ ◌ⷶ ◌ⷼ ◌ⷭ ◌ⷣ ◌ꚞ ◌ⷴ ◌ⷢ ◌ⷯ ◌ꙹ ◌ꙶ ◌ⷦ ◌ⷧ ◌ⷱ ◌ⷳ ◌ⷤ ◌ꙸ ◌̾ ◌︤ ◌︦ ◌︥ ◌ꙺ ◌꙽ ◌ⷰ ◌ⷡ ◌ⷠ ◌꙼ ◌ⷩ ◌ⷨ ◌͞◌ d) number keypad e) after Ꙩ deadkey (lexical variants of o) (liturgical symbols and Arabic numbers) 1 → ꙩ Shift + 1 → Ꙩ (1 = singular) ⹆ ⹈ 契 喇 車 豈 Num ⹅ ⹇ 龜 金 - 更 2 → ꙭ Shift + 2 → Ꙭ (2 = dual) Ч → ꙫ Shift + Ч → Ꙫ (очи) 7 8 ⧟ 9 3 → ꙮ (3 = plural) + Б → ꚙ Shift + Б → Ꚙ (оба) 4 賈 5 6 К → ꚛ Shift + К → Ꚛ (окрестъ) Enter 1 句 2 串 3 滑 f) Capital Ъ, Ь, and Ꙏ can be entered by activating CapsLock , typing ъ, ь, or ꙏ, and deactivating 0 龜 , CapsLock again. -
Cyrillic # Version Number
############################################################### # # TLD: xn--j1aef # Script: Cyrillic # Version Number: 1.0 # Effective Date: July 1st, 2011 # Registry: Verisign, Inc. # Address: 12061 Bluemont Way, Reston VA 20190, USA # Telephone: +1 (703) 925-6999 # Email: [email protected] # URL: http://www.verisigninc.com # ############################################################### ############################################################### # # Codepoints allowed from the Cyrillic script. # ############################################################### U+0430 # CYRILLIC SMALL LETTER A U+0431 # CYRILLIC SMALL LETTER BE U+0432 # CYRILLIC SMALL LETTER VE U+0433 # CYRILLIC SMALL LETTER GE U+0434 # CYRILLIC SMALL LETTER DE U+0435 # CYRILLIC SMALL LETTER IE U+0436 # CYRILLIC SMALL LETTER ZHE U+0437 # CYRILLIC SMALL LETTER ZE U+0438 # CYRILLIC SMALL LETTER II U+0439 # CYRILLIC SMALL LETTER SHORT II U+043A # CYRILLIC SMALL LETTER KA U+043B # CYRILLIC SMALL LETTER EL U+043C # CYRILLIC SMALL LETTER EM U+043D # CYRILLIC SMALL LETTER EN U+043E # CYRILLIC SMALL LETTER O U+043F # CYRILLIC SMALL LETTER PE U+0440 # CYRILLIC SMALL LETTER ER U+0441 # CYRILLIC SMALL LETTER ES U+0442 # CYRILLIC SMALL LETTER TE U+0443 # CYRILLIC SMALL LETTER U U+0444 # CYRILLIC SMALL LETTER EF U+0445 # CYRILLIC SMALL LETTER KHA U+0446 # CYRILLIC SMALL LETTER TSE U+0447 # CYRILLIC SMALL LETTER CHE U+0448 # CYRILLIC SMALL LETTER SHA U+0449 # CYRILLIC SMALL LETTER SHCHA U+044A # CYRILLIC SMALL LETTER HARD SIGN U+044B # CYRILLIC SMALL LETTER YERI U+044C # CYRILLIC