DOCSLIB.ORG

Record Las A

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
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. For-example, an accession - number could be 'plac d in the useroption argg., , .., 1 , . For each set of'procedureithere 4)a-corresponding flowchart (Figures 2, 3,5,, 6). ThesdTlowchartsg resent thevarious options available to a Mdmber when reques -qatalogcar_dS in accordance with one of the four basic procedures. Users of.LC Call Number (Fig. 2) J TheseNMembers will request catalog cardsvlagoompletfng blue punch _card, which requests production of complete packs. There.are four options in making this type of request .1 1 - DOCENT REgtea r FD 080 118 / LI 004 423. '11 *FOR Kilgour, Frederick Coip.; Davis; Hillis D,.. C comp." . , -The Development of A Computerised RegiontiLibrary Systeil..Appendices 1-4.:rinal Report. C INSTITUTION- Ohi6 library-.Center, colgmbus._ C , . SPOfi AGENCY. Office of-Education r(DREW) Washingtoni BURgAU,NO BR-9-0554 .TUB DATE: Jun 73 4 CONTRACT_ IMW-0,p70-2289(506) *TOTE 228p.; 0 References) EDRS PRICE, MP-80.65 RC-119.87 - ---DESCRIPTORS *Cataloging; Catalogs; college Libraries; Expenditure Per Student; Library Automation; *Library . Expenditures; *Library Networks; Library Technical I Processes;Manualsr *On Line Systems; Regional ti PrOgrams;.Union Catilogs*UniArsity Libratles IDENTIFIERS -Cathode Ray Tubes-OCLC; *Ohio College Library Center ABSTRACT , , The purpose of the 0 ib College Library Center (OCLC) computerized regional library sy itt to provide,ah ow-line-system that *alma available to_faculty and stu4ents in. individual. colleges and _universities the 1 nary resources, throughout' a_region,,_while, at the tame-tike_dece/era gAhe.rate per - student - library costs. The. - fesearch and developme t culminated in the successful =lmplementation_,- of an on -line, union ca_alogand shared cattlagiqg stew. ,The final reports of the project is f,I 04 422._Tbis-document contains appendices one through four:(1) Inetruticin Manual tot Catalog Production' msnuS1 for OCLC Catalog. Card PrOduction, (3) Creation of.kathine Readable Catalog Entried..An Adaptation of the 1Data _Treparation Manual:' MARC Editors," and.(4)- `Cataloging op a Cathode .Ray Tube:*rminal..(Other appendices are LI 004 424 through'Ll 004 428.) (AUttxT/S.7).. S. V c V 0 4 iv C V . ti fDEREISTMENIOR HEALTH, ' 'EDUCATION 1WELFARE - STITIJTE OF ASOMUIL. EOUCATI HAS SEENREPRO - THJS DOCUMENT RECEIVED FROM OuCeD 0AciLyORGANIZATION AS ORIGIN THETERiON OR OF VIEWORCIPINIONS ATiNG IT POINTSNECESSARILY REPRE STATED 00 NOT INSTITUTE OF NATIONAL SENT OFFICIAL OR POLICY EDUCATION POSITION LIBRARY SYSTEM THEDEVELOPMENT.OFACOMPUTERTZED-REC7014AL \` -Frederick G.Kilgour - College*Library Center t The Ohio K 114 WestHenderson Road, Columbus, Ohio.43220 , R Hillis D.-,Davis CooperativeCO/lege Library 159 ForrestAvenue N.E.. Atlanta, Georgia30303 1e I A. A P P D S r ... 1. ,Instruction Manual forCatatt'PridUction. (Li004 423T . td.c. II. Manual for oco Catalog Card Production; (Revisedievised and Enlarged. Judith Hopkins. \ (LI 004- 423) . '., III. Creation of Machine Readable Cata log.Entries;'An Adaptation of the "Data 4 %. .., % . Preparation Manual: MAN Editors." (LI 004 423) A o / * % t IV. Cataloging on a. Cathode Ray Tube Terminal. i(LI 004' 3) . ., 1 '-'. , 4' O. Brief Descriptroncof-the Serials Control. System:It Preliminary Report. (LI 004 424) 4 VI. A PreliininaryDescriptionV the OCLC Serials Control System. (LI 004 424)--- VII. Manual for Checking-In, Binding, and Claiming of Serials on a CRT Teritinal - -- --Drat of Preliminary Procedures.. (1,1'004 424) ' % . - I ft 11 '- . VIII., Suggested 'Minimum Requirementd,for Serials Cataloging. (LI 004 44) IX. OCLC Technical erotessing System - A Preliminary Outline: (LI 004 424) . 1 X. The'Technical ProceSsing Sistem,VMay 1972. (Li 004 424), - -\- XI. Recommended Standards for the Cataloging of Serials. (LI 004 424) * .., . _. +- .... XII. Standards for InlmitCl.taloging: (LI 004 424) . - Thee lechnical Processing Syst'em, Augus*t (LI 004 4 24) XIV. Ohio College Library Center Annual Report 1971/1972. ''(LI `00471g.4) ;4 T. XV. tLarg On-Line-Files of Bibliographic Data: An EfficientDesign and a Mathematical Predictor of, Retrieval- Behavior.P.L. Rastcgi, J.E. RUsh and U,A. Wyckoff. (Not Available EDRS), k -. XVI. OCLC Systems: ,'technical Aspi4s. Phillip Long. and OhiorSXate.Univers0.4 Libraries Systems Gerry D. Guthrie. (Not Available'EDRS) '1., 4. XVII; Name-Title Entry Rptrieval frjik-a MARC File. Philip-L. Long and Frgderick G. _ , KilgdUr. (Note Available EDRS) . t. 1 , XVIII, A Truncated Search Key Title Index. Philip L. Long and Frederick-G.-Kilgour. (Not Available EDRS) XIX. Title-Only Entries Retrieved by Use of Truncated Search Keys. -Ftederick G. 4. Long, Eugene B. Leiderman and Alan L.,Landgraf.(Not Available EDRS) ; XX. Ohio College Library Center Systems. Frederia Kilgour. (Not Available EDRS) XXI. -Evolving, Co4uterizing, Personalizing. Frederick Kilgour. (Not Available EDRS) A 4. XII. The Shared Cataloging System of the Ohio College Library Center. Frederick C. Kilgour, Philip L. Long, Alan L. Landgraf, and John W. Wyckoff. Available ED11) ; , . pkrns. XXIII. Cataloging with akComputa - OCLC Comes to Pennsylvania. Robert C. Stew (Not Available EDRS) . XXIV._The &do cottege Library Center Program/Subroutine Documentation; .Ease,Update (M1=6). (LI 004 425) XXV. The Ohio C011ege Library1 Center Program/Subroutine Documentation; Call Number (CNVTi (LI 004 426) XXVI. The Ohio college tibtary Center lorhgram/SubroutineDocumentation; Generate , Pack DefinitionTabls (GEgPDTS). (LI 004 427) 4 The Ohio College-Library Center Program/Subroutine Documentation; Card Format Zrogram,(CCFP). (LI 004 427) , XXVIII. The Ohio College Library Center Program /Subroutine Documentation; Tape (BPT). (LI 004 428) G. ur. vailable' DRi) e EDRS) 4 4. , .... edericit jNot- .. venerate, l'ts .... :atalog s s - -.4 Wild. Print I- - 4. sl .4, ' Ohicr_College'LibraryCenter. 1314 Kinnear Road Columbus, Ohio 43212 February, 1970 .. , - t 41111 r a TABLE OF CONTENTS Defining the Pack. Purpose of the Catalog Profild;Questionpaire Ty?es Entries .Completing the Catalog Profile,Questionnaire II 'Request PrOedures When to Request Permanent Records at OCL9 .Four Requisition Procedures Users LC Call Number Users of LC Class Number Users of Dewey Class umb,er Users of Local Call Number Modifications and Multiple Holdings ,16 III Description of Precoded Punch Cards 16 Blue -Punch Card 16 Green Punch Card 19 Red Punch Card f ielloW Punch ard . 20, Brown Punch -Card Orange.PunchiCard 11. .LIST OF FIGURES Page Number -1 Catalog Profile Questiohnaire 2 Flowchart; Library Using'LC Call Number . _ tire 1 Flowchart; Library Using LC Class Number 3 .. f. Unit Card " tire 1 . V . Flowchart; Lib4ry Using Local 5 Blue Card 17 6. Blue Cards; Multiple dokiest ls- 6 Green Caid 2? 6 .Creen "Literature" Card 20 9 21 12 21 22 ,16 23 16 26 16 L 19 , 20. 23 25 t The purpose of this Ihstruction Manualis three - fold. objectives of . Page ' Section I, DEFINING THE PACK, delineates the the.gatalog Profile Questionnaireand'describes how to 4 . complete it. Section II, REQUESTPROCEDURES, provides Membership with various procedures to follow whenaski'hg 8 . for catalog Cards from OCLC. Sectidn III,TESCRIPTION OF PRECODED PUNCH CARDS, contains a detailedexplanation for 10 completing pi,ecnde'd punch cards.. ti r , 11 The,Ohio College Library Center will producecards weekly when each new MARC tape isreceived. riber 13 )er DEFINING THE PACK 7 A' '"NSECTION I: 17 .- Purpose' Of the Catal gPrOfile Questionnaire 14- The Ohio College Library Center biasdeveloped a Catalog Production Syster4 Capable of handling theindividual needs likely to have a number of 2p . .of a*MenOuer library, which-is receivirig catalogs, such a public catalog; official catalog, 20 or shelf 'list withinits s tem. To secure from theMembership information about catalogards to be trbduced for each t 21 catalog, op...Chas devi-qd a CatalogProfile Questpmnaire. A 21 Questionnaire must be completed . A separate Catalog P"ofile for'each receivingicatalo since types of cards will 'vary 22 ,-for each catalpg. Catalo cards produced for any onereceiving tatalog are called a pack' When a Member library hat more 23 ,than one receiving catalop the entriesproduced for,all of its ricelving cataloes.arp referred to ascomplete packs. 26 / Types of Entries Catalog cards ising a pack can be ninedifferent types.
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 "Я".
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • 1 Symbols (2286)
    1 Symbols (2286) USV Symbol Macro(s) Description 0009 \textHT <control> 000A \textLF <control> 000D \textCR <control> 0022 ” \textquotedbl QUOTATION MARK 0023 # \texthash NUMBER SIGN \textnumbersign 0024 $ \textdollar DOLLAR SIGN 0025 % \textpercent PERCENT SIGN 0026 & \textampersand AMPERSAND 0027 ’ \textquotesingle APOSTROPHE 0028 ( \textparenleft LEFT PARENTHESIS 0029 ) \textparenright RIGHT PARENTHESIS 002A * \textasteriskcentered ASTERISK 002B + \textMVPlus PLUS SIGN 002C , \textMVComma COMMA 002D - \textMVMinus HYPHEN-MINUS 002E . \textMVPeriod FULL STOP 002F / \textMVDivision SOLIDUS 0030 0 \textMVZero DIGIT ZERO 0031 1 \textMVOne DIGIT ONE 0032 2 \textMVTwo DIGIT TWO 0033 3 \textMVThree DIGIT THREE 0034 4 \textMVFour DIGIT FOUR 0035 5 \textMVFive DIGIT FIVE 0036 6 \textMVSix DIGIT SIX 0037 7 \textMVSeven DIGIT SEVEN 0038 8 \textMVEight DIGIT EIGHT 0039 9 \textMVNine DIGIT NINE 003C < \textless LESS-THAN SIGN 003D = \textequals EQUALS SIGN 003E > \textgreater GREATER-THAN SIGN 0040 @ \textMVAt COMMERCIAL AT 005C \ \textbackslash REVERSE SOLIDUS 005E ^ \textasciicircum CIRCUMFLEX ACCENT 005F _ \textunderscore LOW LINE 0060 ‘ \textasciigrave GRAVE ACCENT 0067 g \textg LATIN SMALL LETTER G 007B { \textbraceleft LEFT CURLY BRACKET 007C | \textbar VERTICAL LINE 007D } \textbraceright RIGHT CURLY BRACKET 007E ~ \textasciitilde TILDE 00A0 \nobreakspace NO-BREAK SPACE 00A1 ¡ \textexclamdown INVERTED EXCLAMATION MARK 00A2 ¢ \textcent CENT SIGN 00A3 £ \textsterling POUND SIGN 00A4 ¤ \textcurrency CURRENCY SIGN 00A5 ¥ \textyen YEN SIGN 00A6
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • Romancyrillic Std V9
    RomanCyrillic Std v. 9 Online Documentation incl. support for Unicode v. 12 and 13 (2019–2020) UNi A PDF code З ! Ѿ © Sebastian Kempgen 2020 !2 RomanCyrillic Std: new in v. 9 Version 9 of RomanCyrillic Std implements all relevant additions from Unicode versions 12 (2019) and 13 (2020). Latest additions were: • lowercase Cyrillic character variants; • Typicon symbols and marks (East Slavic Orthodox printing); • Various small additions and corrections. In this documentation, new additions are marked in red; other notes are in blue. The font is free for academic use. Commercial licenses are available. The font is not in the public domain. No modification or disassembling is allowed. All rights are reserved by the author. !3 RomanCyrillic Std: its mission RomanCyrillic Std enables scholars, especially Slavists and Medievalists in general, linguists, editors, teachers etc. to display and write all the characters they need - including historical ones, accents, diacritics, phonetics etc. It’s the Swiss Army knife of fonts for the Latin, Greek, Coptic, and Cyrillic script - plus many more transliterated ones (like Glagolitic and Gothic). It is updated regularly in accordance with new releases of the Unicode® standard. The font blends perfectly with Times® and Times New Roman®, and does many things better much than these! The font is free for academic use. Commercial licenses are available. The font is not in the public domain. No modification or disassembling is allowed. All rights are reserved by the author. !4 RomanCyrillic Std: Basic Latin The Basics; nothing special here !5 RomanCyrillic Std: Latin 1-Supplement The Basics; nothing special here !6 RomanCyrillic Std: Latin Extended-A Croatian German long s !7 RomanCyrillic Std: Latin Extended Add.
    [Show full text]
  • Primo Technical Guide
    Technical Guide May 2016 Ex Libris Confidential 6/7 1 CONFIDENTIAL INFORMATION The information herein is the property of Ex Libris Ltd. or its affiliates and any misuse or abuse will result in economic loss. DO NOT COPY UNLESS YOU HAVE BEEN GIVEN SPECIFIC WRITTEN AUTHORIZATION FROM EX LIBRIS LTD. This document is provided for limited and restricted purposes in accordance with a binding contract with Ex Libris Ltd. or an affiliate. The information herein includes trade secrets and is confidential. DISCLAIMER The information in this document will be subject to periodic change and updating. Please confirm that you have the most current documentation. There are no warranties of any kind, express or implied, provided in this documentation, other than those expressly agreed upon in the applicable Ex Libris contract. This information is provided AS IS. Unless otherwise agreed, Ex Libris shall not be liable for any damages for use of this document, including, without limitation, consequential, punitive, indirect or direct damages. Any references in this document to third‐party material (including third‐party Web sites) are provided for convenience only and do not in any manner serve as an endorsement of that third‐ party material or those Web sites. The third‐party materials are not part of the materials for this Ex Libris product and Ex Libris has no liability for such materials. TRADEMARKS ʺEx Libris,ʺ the Ex Libris bridge , Primo, Aleph, Alephino, Voyager, SFX, MetaLib, Verde, DigiTool, Preservation, Rosetta, URM, ENCompass, Endeavor eZConnect, WebVoyáge, Citation Server, LinkFinder and LinkFinder Plus, and other marks are trademarks or registered trademarks of Ex Libris Ltd.
    [Show full text]
  • 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
    [Show full text]