Mende Kikakui Script

Total Page:16

File Type:pdf, Size:1020Kb

Mende Kikakui Script Mende Kikakui script The Mende Kikakui script is a syllabary used for writing the Mende language of Sierra Leone. Mende /ˈmÉ›ndi/ (MÉ›nde yia) is a major language of Sierra Leone, with some speakers in neighboring Liberia. It is spoken by the Mende people and by other ethnic groups as a regional lingua franca in southern Sierra Leone. Mende is a tonal language belonging to the Mande branch of the Nigerâ“Congo language family. Early systematic descriptions of Mende were by F. W. Migeod and Kenneth Crosby. The Mende Kikakui script is a syllabary used for writing the Mende language of Sierra Leone. For faster navigation, this Iframe is preloading the Wikiwand page for Mende Kikakui script. Home. News. Random Article. Install Wikiwand. Follow Us. Send a suggestion. Konrad Tuchscherer, African Script and Scripture: The History of the Kikakui (Mende) Writing System for Bible Translations," African Languages and Cultures, 8, 2 (1995), pp. 169-188. External links. http://www.omniglot.com/writing/mende.htm. Kikakui â” is a syllabary used for writing the Mende language. History It was devised by Mohammed Turay (born ca. 1850), an Islamic scholar, at a town called Maka (Barri Chiefdom, southern Sierra Leone). Unicode Script: Mende Kikakui. The Mende Kikakui script has 213 characters. ISO 15924 code: Mend. There are 1 fonts that have a character in this range. 213 characters (100%) of the script is covered. 1 2 Next Showing 1 to 201 of 213 Results. Image. Browser. Mende Kikakui script was added to the Unicode Standard in June 2014 with the release of version 7.0. The Unicode block for Mende Kikakui is U+1E800â“U+1E8DF: Mende Kikakui[1][2] Official Unicode Consortium code chart (PDF). 0. 1..
Recommended publications
  • ONIX for Books Codelists Issue 40
    ONIX for Books Codelists Issue 40 23 January 2018 DOI: 10.4400/akjh All ONIX standards and documentation – including this document – are copyright materials, made available free of charge for general use. A full license agreement (DOI: 10.4400/nwgj) that governs their use is available on the EDItEUR website. All ONIX users should note that this is the fourth issue of the ONIX codelists that does not include support for codelists used only with ONIX version 2.1. Of course, ONIX 2.1 remains fully usable, using Issue 36 of the codelists or earlier. Issue 36 continues to be available via the archive section of the EDItEUR website (http://www.editeur.org/15/Archived-Previous-Releases). These codelists are also available within a multilingual online browser at https://ns.editeur.org/onix. Codelists are revised quarterly. Go to latest Issue Layout of codelists This document contains ONIX for Books codelists Issue 40, intended primarily for use with ONIX 3.0. The codelists are arranged in a single table for reference and printing. They may also be used as controlled vocabularies, independent of ONIX. This document does not differentiate explicitly between codelists for ONIX 3.0 and those that are used with earlier releases, but lists used only with earlier releases have been removed. For details of which code list to use with which data element in each version of ONIX, please consult the main Specification for the appropriate release. Occasionally, a handful of codes within a particular list are defined as either deprecated, or not valid for use in a particular version of ONIX or with a particular data element.
    [Show full text]
  • Script Encoding, Part 2
    Script Encoding, Part 2 Working with the user community Debbie Anderson, SEI, UC Berkeley Internationalization and Unicode Conference 40 2 November 2016 Script Encoding Initiative, UC Berkeley • Started 2002 • Helped get over 70 scripts into Unicode • 100+ scripts remain to be encoded A few words about scripts... • Can carry significant emotional feeling • Ol Chiki • Even if the “user” can’t read the script , script can be a symbol of identity & pride • Can make one community different from another • But a new script can delay its use on devices Bamum Who make up the “user community”? • Anyone with an interest in the script: • linguists, native users, liturgical script users, librarians, historians, script enthusiasts... • May not be able to actively read and write the script • To assist on Unicode proposals, should have very good working knowledge of script Steps to Encoding a Script Steps to Encoding a Script: Identify script as eligible Factors: • Users (beyond creator and few others) • Printed materials in script • Taught today (esp. new script) • Script relatively stable • Not unifiable with another encoded script Identify script as eligible Steps to Encoding a Script: Identify script as eligible Lakhum Mossang - Tangsa Identify script as eligible Shuishu Steps to Encoding a Script: Collect materials Kpelle Collect materials Khitan Large Script Identify script as eligible Steps to Encoding a Script: Write proposal l Write proposal Collect materials Identify script as eligible Steps to Encoding a Script: Get Experts / User Community
    [Show full text]
  • Name Hierarchy Methods Enums and Flags
    Pango::Gravity(3pm) User Contributed Perl Documentation Pango::Gravity(3pm) NAME Pango::Gravity − represents the orientation of glyphs in a segment of text HIERARCHY Glib::Enum +−−−−Pango::Gravity METHODS gravity = Pango::Gravity::get_for_matrix ($matrix) • $matrix (Pango::Matrix) gravity = Pango::Gravity::get_for_script ($script, $base_gravity, $hint) • $script (Pango::Script) • $base_gravity (Pango::Gravity) • $hint (Pango::GravityHint) boolean = Pango::Gravity::is_vertical ($gravity) • $gravity (Pango::Gravity) double = Pango::Gravity::to_rotation ($gravity) • $gravity (Pango::Gravity) ENUMS AND FLAGS enum Pango::Gravity • ’south’ / ’PANGO_GRAVITY_SOUTH’ • ’east’ / ’PANGO_GRAVITY_EAST’ • ’north’ / ’PANGO_GRAVITY_NORTH’ • ’west’ / ’PANGO_GRAVITY_WEST’ • ’auto’ / ’PANGO_GRAVITY_AUTO’ enum Pango::GravityHint • ’natural’ / ’PANGO_GRAVITY_HINT_NATURAL’ • ’strong’ / ’PANGO_GRAVITY_HINT_STRONG’ • ’line’ / ’PANGO_GRAVITY_HINT_LINE’ enum Pango::Script • ’invalid−code’ / ’PANGO_SCRIPT_INVALID_CODE’ • ’common’ / ’PANGO_SCRIPT_COMMON’ • ’inherited’ / ’PANGO_SCRIPT_INHERITED’ • ’arabic’ / ’PANGO_SCRIPT_ARABIC’ • ’armenian’ / ’PANGO_SCRIPT_ARMENIAN’ • ’bengali’ / ’PANGO_SCRIPT_BENGALI’ • ’bopomofo’ / ’PANGO_SCRIPT_BOPOMOFO’ • ’cherokee’ / ’PANGO_SCRIPT_CHEROKEE’ • ’coptic’ / ’PANGO_SCRIPT_COPTIC’ • ’cyrillic’ / ’PANGO_SCRIPT_CYRILLIC’ • ’deseret’ / ’PANGO_SCRIPT_DESERET’ • ’devanagari’ / ’PANGO_SCRIPT_DEVANAGARI’ • ’ethiopic’ / ’PANGO_SCRIPT_ETHIOPIC’ • ’georgian’ / ’PANGO_SCRIPT_GEORGIAN’ perl v5.28.0 2018-10-29 1 Pango::Gravity(3pm) User Contributed
    [Show full text]
  • Unifoundry.Com GNU Unifont Glyphs
    Unifoundry.com GNU Unifont Glyphs Home GNU Unifont Archive Unicode Utilities Unicode Tutorial Hangul Fonts Unifont 9.0 Chart Fontforge Poll Downloads GNU Unifont is part of the GNU Project. This page contains the latest release of GNU Unifont, with glyphs for every printable code point in the Unicode 9.0 Basic Multilingual Plane (BMP). The BMP occupies the first 65,536 code points of the Unicode space, denoted as U+0000..U+FFFF. There is also growing coverage of the Supplemental Multilingual Plane (SMP), in the range U+010000..U+01FFFF, and of Michael Everson's ConScript Unicode Registry (CSUR). These font files are licensed under the GNU General Public License, either Version 2 or (at your option) a later version, with the exception that embedding the font in a document does not in itself constitute a violation of the GNU GPL. The full terms of the license are in LICENSE.txt. The standard font build — with and without Michael Everson's ConScript Unicode Registry (CSUR) Private Use Area (PUA) glyphs. Download in your favorite format: TrueType: The Standard Unifont TTF Download: unifont-9.0.01.ttf (12 Mbytes) Glyphs above the Unicode Basic Multilingual Plane: unifont_upper-9.0.01.ttf (1 Mbyte) Unicode Basic Multilingual Plane with CSUR PUA Glyphs: unifont_csur-9.0.01.ttf (12 Mbytes) Glyphs above the Unicode Basic Multilingual Plane with CSUR PUA Glyphs: unifont_upper_csur-9.0.01.ttf (1 Mbyte) PCF: unifont-9.0.01.pcf.gz (1 Mbyte) BDF: unifont-9.0.01.bdf.gz (1 Mbyte) Specialized versions — built by request: SBIT: Special version at the request
    [Show full text]
  • The Fontspec Package Font Selection for X LE ATEX and Lualatex
    The fontspec package Font selection for X LE ATEX and LuaLATEX WILL ROBERTSON With contributions by Khaled Hosny, Philipp Gesang, Joseph Wright, and others. http://wspr.io/fontspec/ 2020/02/21 v2.7i Contents I Getting started 5 1 History 5 2 Introduction 5 2.1 Acknowledgements ............................... 5 3 Package loading and options 6 3.1 Font encodings .................................. 6 3.2 Maths fonts adjustments ............................ 6 3.3 Configuration .................................. 6 3.4 Warnings ..................................... 6 4 Interaction with LATEX 2ε and other packages 7 4.1 Commands for old-style and lining numbers ................. 7 4.2 Italic small caps ................................. 7 4.3 Emphasis and nested emphasis ......................... 7 4.4 Strong emphasis ................................. 7 II General font selection 8 1 Main commands 8 2 Font selection 9 2.1 By font name ................................... 9 2.2 By file name ................................... 10 2.3 By custom file name using a .fontspec file . 11 2.4 Querying whether a font ‘exists’ ........................ 12 1 3 Commands to select font families 13 4 Commands to select single font faces 13 4.1 More control over font shape selection ..................... 14 4.2 Specifically choosing the NFSS family ...................... 15 4.3 Choosing additional NFSS font faces ....................... 16 4.4 Math(s) fonts ................................... 17 5 Miscellaneous font selecting details 18 III Selecting font features 19 1 Default settings 19 2 Working with the currently selected features 20 2.1 Priority of feature selection ........................... 21 3 Different features for different font shapes 21 4 Selecting fonts from TrueType Collections (TTC files) 23 5 Different features for different font sizes 23 6 Font independent options 24 6.1 Colour .....................................
    [Show full text]
  • Overview and Rationale
    Integration Panel: Maximal Starting Repertoire — MSR-5 Overview and Rationale REVISION – APRIL 06, 2021 – PUBLIC COMMENT Table of Contents 1 Overview 3 2 Maximal Starting Repertoire (MSR-5) 3 2.1 Files 3 2.1.1 Overview 3 2.1.2 Normative Definition 4 2.1.3 HTML Presentation 4 2.1.4 Code Charts 4 2.2 Determining the Contents of the MSR 5 2.3 Process of Deciding the MSR 6 3 Scripts 8 3.1 Comprehensiveness and Staging 8 3.2 What Defines a Related Script? 9 3.3 Separable Scripts 9 3.4 Deferred Scripts 9 3.5 Historical and Obsolete Scripts 9 3.6 Selecting Scripts and Code Points for the MSR 10 3.7 Scripts Appropriate for Use in Identifiers 10 3.8 Modern Use Scripts 11 3.8.1 Common and Inherited 12 3.8.2 Scripts included in MSR-1 12 3.8.3 Scripts added in MSR-2 12 3.8.4 Scripts added in MSR-3 through MSR-5 13 3.8.5 Modern Scripts Ineligible for the Root Zone 13 3.9 Scripts for Possible Future MSRs 13 3.10 Scripts Identified in UAX#31 as Not Suitable for identifiers 14 4 Exclusions of Individual Code Points or Ranges 16 4.1 Historic and Phonetic Extensions to Modern Scripts 16 4.2 Code Points That Pose Special Risks 17 4.3 Code Points with Strong Justification to Exclude 17 4.4 Code Points That May or May Not be Excludable from the Root Zone LGR 17 4.5 Non-spacing Combining Marks 18 Integration Panel: Maximal Starting Repertoire — MSR-3 Overview and Rationale 5 Discussion of Particular Code Points 20 5.1 Digits and Hyphen 20 5.2 CONTEXT O Code Points 21 5.3 CONTEXT J Code Points 21 5.4 Code Points Restricted for Identifiers 21 5.5 Compatibility
    [Show full text]
  • Unicode Reference Lists: Other Script Sources
    Other Script Sources File last updated October 2020 General ALA-LC Romanization Tables: Transliteration Schemes for Non-Roman Scripts, Approved by the Library of Congress and the American Library Association. Tables compiled and edited by Randall K. Barry. Washington, DC: Library of Congress, 1997. ISBN 0-8444-0940-5. Adlam Barry, Ibrahima Ishagha. 2006. Hè’lma wallifandè fin èkkitago’l bèbèrè Pular: Guide pra- tique pour apprendre l’alphabet Pulaar. Conakry, 2006. Ahom Barua, Bimala Kanta, and N.N. Deodhari Phukan. Ahom Lexicons, Based on Original Tai Manuscripts. Guwahati: Department of Historical and Antiquarian Studies, 1964. Hazarika, Nagen, ed. Lik Tai K hwam Tai (Tai letters and Tai words). Souvenir of the 8th Annual conference of Ban Ok Pup Lik Mioung Tai. Eastern Tai Literary Association, 1990. Kar, Babul. Tai Ahom Alphabet Book. Sepon, Assam: Tai Literature Associate, 2005. Alchemical Symbols Berthelot, Marcelin. Collection des anciens alchimistes grecs. 3 vols. Paris: G. Steinheil, 1888. Berthelot, Marcelin. La chimie au moyen âge. 3 vols. Osnabrück: O. Zeller, 1967. Lüdy-Tenger, Fritz. Alchemistische und chemische Zeichen. Würzburg: JAL-reprint, 1973. Schneider, Wolfgang. Lexikon alchemistisch-pharmazeutischer Symbole. Weinheim/Berg- str.: Verlag Chemie, 1962. Anatolian Hieroglyphs Hawkins, John David, and Halet Çambel. Corpus of Hieroglyphic Luwian Inscriptions. Ber- lin and New York: Walter de Gruyter, 2000. ISBN 3-11-010864-X. Herbordt, Suzanne. Die Prinzen- und Beamtensiegel der hethitischen Grossreichszeit auf Tonbullen aus dem Ni!antepe-Archiv in Hattusa. Mit Kommentaren zu den Siegelin- schriften und Hieroglyphen von J. David Hawkins. Mainz am Rhein: Verlag Philipp von Zabern, 2005. ISBN: 3-8053-3311-0.
    [Show full text]
  • IBM AIX Enhancements and Modernization
    Front cover IBM AIX Enhancements and Modernization Navdeep Dhaliwal Ahmed Mashhour Armin Röll Liviu Rosca Redbooks IBM Redbooks IBM AIX Enhancements and Modernization January 2020 SG24-8453-00 Note: Before using this information and the product it supports, read the information in “Notices” on page xv. First Edition (January 2020) This edition applies to AIX Version 7.2 Standard Edition (product number 5765-G98), AIX Version 7.2 Enterprise Edition (product number 5765-CD3), IBM PowerVM Version 3.1 Enterprise Edition (product number 5765-VE3), IBM PowerVC Version 1.4.3 Standard Edition (product number 5765-VCS), and IBM servers that are based on POWER9 processor-based technology. © Copyright International Business Machines Corporation 2020. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures . vii Tables . ix Examples . xi Notices . .xv Trademarks . xvi Preface . xvii Authors. xvii Now you can become a published author, too! . xviii Comments welcome. xviii Stay connected to IBM Redbooks . xix Chapter 1. General enhancements . 1 1.1 Live Update function . 2 1.1.1 Live Update concepts and procedure . 2 1.1.2 Live Update modes . 4 1.1.3 Live Update management types . 4 1.1.4 Live Update methods . 4 1.1.5 AIX Live Update integration with Power Enterprise Pools . 7 1.1.6 Live Update CPU resource reduction . 11 1.1.7 Live Update across frames . 15 1.1.8 Automount File System support with Live Update . 19 1.1.9 Kerberos authentication support in Live Update .
    [Show full text]
  • Tracklang: Tracking Language Options
    tracklang v1.5: tracking language options Nicola L. C. Talbot http://www.dickimaw-books.com/ 2020-06-30 Abstract The tracklang package is provided for package developers who want a simple inter- face to find out which languages the user has requested through packages such as ba- bel and polyglossia. This package doesn’t provide any translations. Its purpose is sim- ply to track which languages have been requested by the user. Generic TEX code is in tracklang.tex for non-LATEX users. If the shell escape is enabled or \directlua is available, this package may also be used to query the LC_ALL or LANG environment variable (see Section5). Windows users, who don’t have the locale stored in environment variables, can use texosquery in combina- tion with tracklang. (Similarly if LC_ALL or LANG don’t contain sufficient information.) In order to use texosquery through the restricted shell escape, you must have at least Java 8 and set up texosquery.cfg appropriately. (See the texosquery manual for fur- ther details.) The fundamental aim of this generic package is to be able to effectively say: The user (that is, the document author) wants to use dialects xx-XX, yy-YY-Scrp, etc in their document. Any packages used by their document that provide multi- lingual or region-dependent support should do whatever is required to activate the settings for those languages and regions (or warn the user that there’s no sup- port). Naturally, this is only of use if the locale-sensitive packages use tracklang to pick up this infor- mation, which is entirely up to the package authors, but at the moment there’s no standard method for packages to detect the required language and region.
    [Show full text]
  • Unidings.Pdf
    Unidings Glyphs and Icons for Blocks of The Unicode Standard O Unidings, version 13.00, March 2020 free strictly for personal, non-commercial use available under the general ufas licence Unicode Fonts for Ancient Scripts George Douros C0 Controls � � 0000..001F Basic Latin � � 0020..007F C1 Controls � � 0080..009F Latin-1 Supplement � � 00A0..00FF Latin Extended-A � � 0100..017F Latin Extended-B � � 0180..024F IPA Extensions � � 0250..02AF Spacing Modifier Leters � � 02B0..02FF Combining Diacritical Marks � � 0300..036F Greek and Coptic � � 0370..03FF Cyrillic � � 0400..04FF Cyrillic Supplement � � 0500..052F Armenian � � 0530..058F Hebrew � � 0590..05FF Arabic � � 0600..06FF Syriac � � 0700..074F Arabic Supplement � � 0750..077F Thaana � � 0780..07BF NKo � � 07C0..07FF Samaritan � � 0800..083F Mandaic � � 0840..085F Syriac Supplement � � 0860..086F � � Arabic Extended-B Arabic Extended-A � � 08A0..08FF Devanagari � � 0900..097F Bengali � � 0980..09FF Gurmukhi � � 0A00..0A7F Gujarati � � 0A80..0AFF Oriya � � 0B00..0B7F Tamil � � 0B80..0BFF Telugu � � 0C00..0C7F Kannada � � 0C80..0CFF Malayalam � � 0D00..0D7F Sinhala � � 0D80..0DFF Thai � � 0E00..0E7F Lao � � 0E80..0EFF Tibetan � � 0F00..0FFF Myanmar � � 1000..109F Georgian � � 10A0..10FF Hangul Jamo � � 1100..11FF Ethiopic � � 1200..137F Ethiopic Supplement � � 1380..139F Cherokee � � 13A0..13FF Unified Canadian Aboriginal Syllabics � � 1400..167F Ogham � � 1680..169F Runic � � 16A0..16FF Tagalog � � 1700..171F Hanunoo � � 1720..173F Buhid � � 1740..175F Tagbanwa � � 1760..177F Khmer
    [Show full text]
  • 19 Africa 19
    The Unicode® Standard Version 12.0 – Core Specification To learn about the latest version of the Unicode Standard, see http://www.unicode.org/versions/latest/. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and the publisher was aware of a trade- mark claim, the designations have been printed with initial capital letters or in all capitals. Unicode and the Unicode Logo are registered trademarks of Unicode, Inc., in the United States and other countries. The authors and publisher have taken care in the preparation of this specification, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. The Unicode Character Database and other files are provided as-is by Unicode, Inc. No claims are made as to fitness for any particular purpose. No warranties of any kind are expressed or implied. The recipient agrees to determine applicability of information provided. © 2019 Unicode, Inc. All rights reserved. This publication is protected by copyright, and permission must be obtained from the publisher prior to any prohibited reproduction. For information regarding permissions, inquire at http://www.unicode.org/reporting.html. For information about the Unicode terms of use, please see http://www.unicode.org/copyright.html. The Unicode Standard / the Unicode Consortium; edited by the Unicode Consortium. — Version 12.0. Includes index. ISBN 978-1-936213-22-1 (http://www.unicode.org/versions/Unicode12.0.0/) 1.
    [Show full text]
  • Iso/Iec Jtc 1/Sc 2 N 4371
    ISO/IEC JTC 1/SC 2 N 4371 ISO/IEC JTC 1/SC 2 Coded character sets Secretariat: JISC (Japan) Document type: Other document (Open) Title: Snapshot of Pictorial view of Roadmaps to BMP, SMP, SIP, TIP and SSP [WG 2 N 4617] Status: This document is circulated to the SC 2 members for referencing as a guide for future submissions of their proposals to WG 2. Date of document: 2014-10-29 Source: WG 2 Expected action: INFO No. of pages: 70 Email of secretary: [email protected] Committee URL: http://isotc.iso.org/livelink/livelink/open/jtc1sc2 ISO/IEC JTC 1/SC 2/ N______ INTERNATIONAL ORGANIZATION FOR STANDARDIZATION ORGANISATION INTERNATIONALE DE NORMALISATION ISO/IEC JTC 1/SC 2/WG 2 Universal Multiple-Octet Coded Character Set (UCS) ISO/IEC JTC 1/SC 2/WG 2 N4617 2014-09-22 Snapshot of Pictorial view of Roadmaps to BMP, SMP, SIP, TIP and Title: SSP Ad hoc group on Roadmaps (Michael Everson, Rick McGowan, Ken Whistler, and V.S. Source: UMAmaheswaran) Adapted by: V.S. UMAmaheswaran Status: For review and adoption by WG 2 at its meeting no. 63 ISO/IEC JTC 1/SC 2/WG 2, ISO/IEC JTC 1/SC 2 and Liaison Distribution: Organizations Replaces: JTC 1/SC 2/ WG 2/ N4530 Summary This document is the latest snapshot of the roadmap documents that has been presented to and adopted by WG 2 (ISO/IEC JTC1/SC2/WG 2). Included in this document are five tables containing the roadmaps to the Basic Multilingual Plane (BMP - Plane 0) version bmp-7-0-1, 2014-09-18)) the Supplementary Multilingual Plane (SMP - Plane 1) (version smp-7-0-1, 2014- 09-18) the Supplementary Ideographic Plane (SIP - Plane 2) (version sip-7-0-1, 2014-09- 18) the Tertiary Ideographic Plane (TIP - Plane 3) (version tip-7-0-0, 2014-08-07), and the Supplementary Special-purpose Plane (SSP - Plane 14) (version ssp-7-0-0, 2014-08-07).
    [Show full text]