DOCSLIB.ORG

Petit Manuel Unix®

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Août 2010 Petit Manuel Unix® Jacques MADELAINE Département d’informatique Université de CAEN 14032 CAEN CEDEX La première édition de ce manuel décrivait SMX un Unix développé à l’INRIA pour la machine française SM90, la deuxième édition une adaptation pour SPIX, un Unix pour SM90 basé sur System V et développé par Bull. Il a été ensuite modifié et corrigé pour SunOS l’Unix de Sun Microsystems, puis pour Solaris. La cinquième version a été adaptée pour tenir compte des particularités du système GNU-Linux. Un chapitre supplémentaire dédié aux accès réseau a été ensuite ajouté. Rappelons que presque toutes les commandes décrites vont fonctionner comme indiqué sur tout système Unix commercial (Solaris, HP-UX, AIX, ...) ou libre (Linux, OpenBSD, FreeBSD, NetBSD, ...). Mes remerciements à Sara Aubry pour sa relecture attentive etàFrançois Girault pour avoir fourni la mise en tableau des commandes d’emacs. Mes remerciements à Davy Gigan pour m’avoir poussé à publier la version html en octobre 2003. 1 INTRODUCTION() INTRODUCTION() 2Petit manuel Unix 2002 INTRODUCTION NOM intro − introduction to the mini manual − introduction au petit manuel DESCRIPTION Ce manuel donne les principales commandes de Unix. Unix est une famille de systèmes d’exploitation ; les commandes décrites existent, sauf précision contraire, sous Linux et Solaris, les deux systèmes disponibles au département. Seules les principales options sont données, reportez-vous au manuel en ligne pour une liste exhaustive.Chaque commande est décrite par trois sections : NOM qui donne le nom de la commande, son nom en anglais (le nom Unix étant un mnémonique anglais ne correspondant pas toujours bien aveclefrançais) et en français. SYNTAXE donne la syntaxe. Les parties entre crochets ([ ]) sont optionnelles. Les noms en caractères gras désignent la commande ou des options. Les arguments en italique désignent des noms de fichiers, les autres arguments sont en police normale. Les arguments de contrôle sont traditionnellement, sous Unix, introduits par le caractère tiret (-), et sont composés d’une seule lettre, ex. : -alx.Avecles commandes GNU est apparu la possibilité de donner l’option de contrôle en format long (un mot) introduit par deux tirets ; on est obligé alors de donner les options une par une, cela donnera sur l’exemple précédent : --all --long.Les commandes qui suivent le standard GNU doivent avoir les options --help et --version qui donnent respectivement une petite aide en ligne et le numéro de version de la commande sans l’exécuter. DESCRIPTION est la section qui donne les effets de la commande et de ces arguments. Ce document se termine (uniquement dans la version papier) par quelques pages de manuels originales de GNU/Linux : dash(1), ed(1), gawk(1), join(1), sed(1), sort(1). La page de ed contient en particulier la définition des expressions régulières utilisées par grep. Pour finir nous donnons les tables des codes ASCII et iso-latin9 obtenues comme page du manuel standard asciii(7) et iso_8859_15(7) et les pages de manuel unicode(7) et utf-8(7). Les commandes sont regroupées en chapitres : GESTION DE L’ACCÈS UTILISATEUR login stty passwd ACCÈS EN RÉSEAU rsync ssh scp sshfs MANIPULATION DE RÉPERTOIRES cd mkdir rmdir MANIPULATION DE FICHIERS a2ps ar basename bzip2 cat comm compress convert cp cut diffexpand gzip head iconvlpmore paste pr recode sox split tail tar tee tr uniq wc MANIPULATION D’ATTRIBUTS DE FICHIERS chgrp chmod chown ln mv rm touch PARCOURS DE HIÉRARCHIE df du find locate whereis which LANGAGES cc cl f77 hugs javacpcperl php python OUTILS DE DÉVELOPPEMENT cpp cplus-dem doxygen eclipse gdb gprof grep indent javadoc ld ldd lint makenetbeans nm nmap od patch prof ranlib size strace strip time EXÉCUTION DE PROGRAMMES echo kill killall nice nohup script sleep DEMANDES D’ÉTATS date file id ls ps pwd rusers tty users w who DIVERS Petit manuel Unix 2002 3 INTRODUCTION bc cal expr man test COMMUNICATION ENTRE USAGERS mail mesg talk write OUTILS RÉSEAUX ftp sftp web-browsers MESURES ET SURVEILLANCE DE SYSTÈME arch free fuser host lsof netstat perfmeter rup top uname uptime vmstat ÉDITEURS DE TEXTES emacs nano vi COMPOSEURS DE TEXTES grofflatex OUTILS GRAPHIQUES 4Petit manuel Unix 2002 GESTION DE L’ACCÈS UTILISATEUR NOM login − login − connexion SYNTAXE login [utilisateur] DESCRIPTION Enregistre la connexion d’un utilisateur au système. Vérifie le mot de passe et établit l’identité de l’utilisa- teur et celle du groupe auquel il appartient. Fait l’initialisation du terminal. Établit le catalogue de travail. Annonce la présence de courrier.Affiche les messages du jour.Exécute le fichier « .login » de l’usager. Lance l’interpréteur de commande ou un autre programme initial suivant ce qui est indiqué dans le fichier «/etc/passwd ». Si ce programme est un shell, ce dernier exécutera le fichier « ˜/.profile » ou « ˜/.bash_pro- file » s’il s’agit de bash ; notons que par défaut au département le bash_profile se contente d’exécuter le «.bashrc » de l’utilisateur. NOM stty − set terminal type − positionner des options de terminal SYNTAXE stty [options] DESCRIPTION Positionne certaines options d’entrées-sorties pour le terminal. Les options sont données en argument de la commande. Sans argument cette commande donne l’état actuel du terminal. Voici quelques options : -a imprime toutes les options du terminal (à utiliser seul). vitesse change la vitesse de transmission. En général vitesse est 1200, 9600 ou 19200. ctrlcar c «c» devient le caractère de contrôle donné. Si « c» est précédé du chapeau « ˆ»,lavaleur utilisée est le caractère de contrôle correspondant. Voici la liste des contrôles possibles avec leur valeur par défaut : erase annulation du dernier caractère (DEL). kill annulation de la ligne (ˆU). werase annulation du dernier mot (ˆW). eof fin de fichier (ˆD). eol fin de ligne (ˆJ). intr interruption , envoie le signal SIGINT(ˆC). quit quit, envoie le signal SIGQUIT (ˆ\). start caractère de contrôle de flux :reprend l’affichage (ˆQ). stop caractère de contrôle de flux :arrête l’affichage (ˆS). susp suspend la tâche courante (ˆZ). rprnt réaffiche la ligne courante (reprint) (ˆR). flush prise en compte immédiate de l’entrée (ˆO). lnext supprime le sens particulier du caractère suivant (ˆV). echo fait l’écho de tout caractère tapé (pas d’écho avec -echo). echoe fait l’écho du caractère « erase » de façon telle que le caractère annulé soit effacé d’un écran vidéo (fonctionne très mal sur un terminal papier). Pas d’écho spécial de « erase » av ec -echo. echok envoie (n’envoie pas avec -echok)uncaractère de nouvelle ligne sur réception du caractère «kill ». icanon les caractères sont disponibles après réception d’une fin de ligne. Les caractères erase, kill, rprnt et werase sont traités. -icanon les caractères erase, kill, rprnt et werase n’ont plus de signification particulière. Le code du car- actère eof indique le nombre de caractères à taper pour qu’ils soient disponibles. Il suffit de prendre « ˆA » pour eof pour que les caractères soient immédiatement disponibles au Petit manuel Unix 2002 5 GESTION DE L’ACCÈS UTILISATEUR programme : $stty -icanon eof « ˆA » Si on veut que le programme gère l’écho lui même (comme more, vi, emacs, ...), faire : $stty -icanon eof "ˆA" -echo Cf raw. isig les caractères INTR et QUIT envoient des signaux. -isig les caractères INTR et QUIT n’envoient pas de signaux. ixon permet (ne permet pas avec -ixon)d’arrêter la sortie avec«ˆS » et de la faire repartir avec «ˆQ». ixany permet de faire repartir la sortie avecn’importe quel caractère. Seul « ˆQ » est autorisé avec -ixany. ixoff demande que le système envoie (n’envoie pas avec -ixoff)les caractères de contrôle de flux (« ˆS » et « ˆQ ») quand la file d’entrée est presque vide ou pleine. tabs préservelecaractère de tabulation (« ˆI »). Av ec -tabs ou tabs3,les caractères de tabulation sont remplacés par des espaces (un taquet de tabulation toutes les 8 colonnes). lcase ne transforme plus les minuscules en majuscules. Utile si on a tapé un nom de login en majus- cules. Les options suivantes sont les combinaisons qui sont le plus souvent utilisées : sane positionne des options jugées « saines » par le système. Étant donné qu’en général la ligne n’est pas « saine », il faut taper stty sane entre des control-J et non des retours-chariot. raw littéralement : le mode cru ; tous les caractères sont disponibles immédiatement au programme sans traitement de erase ou kill. Attention ceci est valable aussi pour ˆD donc on ne peut plus spécifier fin de fichier,etbien sûr pour ˆC et on ne peut plus arrêter l’exécution en envo yant un sig- nal à l’aide du clavier.Pour lancer un programme qui veut gérer toutes les entrées faire : stty raw; programme; stty sane Ainsi après la fin d’exécution du programme, stty sane remet tout en place. NOM passwd − password − mot de passe SYNTAXE passwd DESCRIPTION Change le mot de passe de l’usager.L’ancien mot de passe est demandé et le nouveau mot de passe est demandé deux fois. Un mot de passe doit avoir au moins 6 caractères, dont au moins 3 caractères alphabétiques et un caractère spécial ou numérique. Rappelons qu’il faut choisir son mot de passe comme n’étant pas un mot d’un dictionnaire français ou étranger. Lorsque la station est cliente NIS (Network Information System), la commande passwd va enfait changer le mot de passe valable sur toutes les stations du réseau. 6Petit manuel Unix 2002 ACCÈS EN RÉSEAU NOM rsync − remote file synchronisation − synchronisation de fichiers à distance SYNTAXE rsync [options] source... [destination] rsync [options][utilisateur@]hôte:source... [destination] rsync [options] source... [utilisateur@]hôte:destination DESCRIPTION rsync permet de synchroniser des arborescences de fichiers sur la même machine (première forme d’appel), ou depuis ou vers des machines distantes (les deux dernières formes d’appel).
Recommended publications
  • Armenian Secret and Invented Languages and Argots

    Armenian Secret and Invented Languages and Argots

    Armenian Secret and Invented Languages and Argots The Harvard community has made this article openly available. Please share how this access benefits you. Your story matters Citation Russell, James R. Forthcoming. Armenian secret and invented languages and argots. Proceedings of the Institute of Linguistics of the Russian Academy of Sciences. Citable link http://nrs.harvard.edu/urn-3:HUL.InstRepos:9938150 Terms of Use This article was downloaded from Harvard University’s DASH repository, and is made available under the terms and conditions applicable to Open Access Policy Articles, as set forth at http:// nrs.harvard.edu/urn-3:HUL.InstRepos:dash.current.terms-of- use#OAP 1 ARMENIAN SECRET AND INVENTED LANGUAGES AND ARGOTS. By James R. Russell, Harvard University. Светлой памяти Карена Никитича Юзбашяна посвящается это исследование. CONTENTS: Preface 1. Secret languages and argots 2. Philosophical and hypothetical languages 3. The St. Petersburg Manuscript 4. The Argot of the Felt-Beaters 5. Appendices: 1. Description of St. Petersburg MS A 29 2. Glossary of the Ṙuštuni language 3. Glossary of the argot of the Felt-Beaters of Moks 4. Texts in the “Third Script” of MS A 29 List of Plates Bibliography PREFACE Much of the research for this article was undertaken in Armenia and Russia in June and July 2011 and was funded by a generous O’Neill grant through the Davis Center for Russian and Eurasian Studies at Harvard. For their eager assistance and boundless hospitality I am grateful to numerous friends and colleagues who made my visit pleasant and successful. For their generous assistance in Erevan and St.
  • Guide to the Use of Character Set Standards in Europe

    Guide to the Use of Character Set Standards in Europe

    CEN TECHNICAL REPORT Draft 3 for CEN Trnnnn:1999 1999-07-23 Descriptors: Data processing, information interchange, text processing, text communication, graphic characters, character sets, representation of characters, coded character sets, architecture Information Technology - Guide to the use of character set standards in Europe This CEN Technical Report has been drawn up by CEN/TC 304 This CEN Technical Report was established by TC 304 in one official version (English). A version in any other language made by translation under the responsibility of a CEN member into its own lan- guage and notified to the Central Secretariat has the same status as the official version. CEN members are the national bodies of Austria, Belgium, the Czech Republic, Denmark, Finland, France, Germany, Greece, Iceland, Ireland, Italy, Luxembourg, Netherlands, Norway, Portugal, Spain, Sweden, Switzerland, and the United Kingdom. CEN European Committee for Standardization Comité Européen de Normalisation Europäisches Komitee für Normung Central Secretariat: rue de Stassart 36, B-1050 Brussels © CEN 1999 Copyright reserved to all CEN members Ref.No. TR xxxx:1999 E CEN TR nnnn : Draft 2 Guide to the use of character set standards in Europe ii Guide to the use of character set standards in Europe CEN TR nnnn : Draft 2 FOREWORD This report was produced by a CEN/TC 304 Project Team, set up in June, 1998, as one of several to carry out the funded work program of TC 304 (documented in CEN/TC 304 N 666 R2). A first draft was discussed at the TC meeting in Brussels in November, 1998. A revised draft was circulated for comments within the TC and thereafter discussed at the TC plenary meeting in April, 1999.
  • Choosing Inscriptions Making Font for 'Armazuli' Aramaic Objectives Mark up of the Texts and Linked Data New Photo Document

    Choosing Inscriptions Making Font for 'Armazuli' Aramaic Objectives Mark up of the Texts and Linked Data New Photo Document

    @EAGLE 2016, Rome Epigraphic Corpus of Georgia Inscriptions found in Georgia are diverse in their typology, content and language. From among this range perhaps the most compelling examples are those inscriptions The Institute of Linguistic Research, in Aramaic and Old Greek (numbering more than 1000), and dating from V AC to XIX (T. Kaukhchishvili 2009.) None of these have been published online according to the EpiDoc guidelines. Thanks to a year’s funding from The Institute of Linguistic Research of the Ilia State University (ISU), the “Epigraphic Corpus of Georgia Project”, Ilia State University led by Prof. Nino Doborjginidze, began on March 1st 2015. It aims to make the first, key 30 inscriptions available to both a scholarly audience and to the general public. It presents an opportunity to question the strict practice of the “print-only” publishing of epigraphic materials among Georgian epigraphists. Objectives New photo documentation and web page - epigraphy.iliauni.edu.ge A desired outcome of the digital publishing of the inscriptions of Georgia is, on the one hand, to preserve those inscriptions and likewise to preserve editions of these inscriptions that were made by Georgian experts from 1930s onwards, although only a few of these were published in international scientific journals because of the So- viet restrictions. Thus the aims of the project can be summarized thus: • to protect these inscriptions as an element of our cultural heritage • to document the printed critical editions of the inscriptions, which likewise consti- tute a part of that cultural heritage • to demonstrate and illustrate common, historical-cultural contexts(e.g.
  • Proposal for the Georgian Script Root Zone LGR

    Proposal for the Georgian Script Root Zone LGR

    Proposal for the Georgian Script Root Zone LGR LGR Version 2 Date: 2016-11-24 Document version: 1.1 Authors: GEORGIAN SCRIPT GENERATION PANEL 1 General Information/ Overview/ Abstract The purpose of this document is to give an overview of the proposed Georgian LGR in the XML format and the rationale behind the design decisions taken. It includes a discussion of relevant features of the script, the communities or languages using it, the process and methodology used and information on the contributors. The formal specification of the LGR can be found in the accompanying XML document: • Proposed-LGR-Georgian-20160915.xml Labels for testing can be found in the accompanying text document: • Labels-GeorgianScript-20160915.txt 2 Script for which the LGR is proposed ISO 15924 Code: Geor ISO 15924 Key N°: 240 ISO 15924 English Name: Georgian Mkhedruli Latin transliteration of native script name: Mkhedruli Native name of the script: მხედრული Maximal Starting Repertoire (MSR) version: MSR-2 Proposal for a Georgian Script Root Zone LGR Georgian Script GP 3 Background on Script and Principal Languages Using It The Georgian scripts are the three writing systems used to write the Georgian language: Asomtavruli, Nuskhuri and Mkhedruli. Mkhedruli (Georgian: მხედრული) is the current Georgian script and is therefore the standard script for modern Georgian and its related Kartvelian languages, whereas Asomtavruli and Nuskhuri are used only in ceremonial religious texts and iconography. In the following, the term Georgian script is used synonymously with Mkhedruli. Like the two other scripts, Mkhedruli is purely unicameral. Mkhedruli first appears in the 10th century - the oldest Mkhedruli inscription found is dated back to 982 AD.
  • Sylfaen : Foundations of Multiscript Typography

    Sylfaen : Foundations of Multiscript Typography

    Sylfaen : Foundations of Multiscript Typography John Hudson, 2000 © INTRODUCTION In the autumn of 1997, I was hired by the Microsoft Typography Group to consult For a general introduction to OpenType, see David Lemon’s on the production of support materials for OpenType font developers working with article in the first issue of Type. For more detailed information, multiple scripts and languages. The project was given the working title Web Resource including the current version of the OpenType specification, for International Typography (WRIT). A year later, I had the pleasure of showing this see the Microsoft Typography work in progress at the 1998 ATypI Conference in Lyon, where it was well received website at: www.microsoft.com/typography by my colleagues in the type industry. Shortly after my return to Canada, Microsoft decided to put further development of this work on hold, so this paper, inevitably, lacks some of the enthusiasm I had for the project in 1998. It is difficult to remain excited about something which has been effectively cancelled, but at the same time I am happy to respond to the editors’ invitation to write something about the project for the Type journal, because I think the small team at Microsoft who worked on this project achieved something important. Perhaps I still hope that some day the project may be revived, even if in a different or more limited form. Certainly, I still believe that the ever increasing emphasis on internationalisation in software development, business and, of course, the Internet, requires a better level of support from font developers, and this in turn requires something like WRIT.
  • Binary Codes

    Binary Codes

    2 Binary Codes The present chapter is an extension of the previous chapter on number systems. In the previous chapter, beginning with some of the basic concepts common to all number systems and an outline on the familiar decimal number system, we went on to discuss the binary, the hexadecimal and the octal number systems. While the binary system of representation is the most extensively used one in digital systems, including computers, octal and hexadecimal number systems are commonly used for representing groups of binary digits. The binary coding system, called the straight binary code and discussed in the previous chapter, becomes very cumbersome to handle when used to represent larger decimal numbers. To overcome this shortcoming, and also to perform many other special functions, several binary codes have evolved over the years. Some of the better-known binary codes, including those used efficiently to represent numeric and alphanumeric data, and the codes used to perform special functions, such as detection and correction of errors, will be detailed in this chapter. 2.1 Binary Coded Decimal The binary coded decimal (BCD) is a type of binary code used to represent a given decimal number in an equivalent binary form. BCD-to-decimal and decimal-to-BCD conversions are very easy and straightforward. It is also far less cumbersome an exercise to represent a given decimal number in an equivalent BCD code than to represent it in the equivalent straight binary form discussed in the previous chapter. The BCD equivalent of a decimal number is written by replacing each decimal digit in the integer and fractional parts with its four-bit binary equivalent.
  • UTF-8 and Unicode FAQ for Unix/Linux by Markus Kuhn

    UTF-8 and Unicode FAQ for Unix/Linux by Markus Kuhn

    UTF-8 and Unicode FAQ for Unix/Linux by Markus Kuhn This text is a very comprehensive one-stop information resource on how you can use Unicode/UTF-8 on POSIX systems (Linux, Unix). You will find here both introductory information for every user, as well as detailed references for the experienced developer. Unicode has started to replace ASCII, ISO 8859 and EUC at all levels. It enables users to handle not only practically any script and language used on this planet, it also supports a comprehensive set of mathematical and technical symbols to simplify scientific information exchange. With the UTF-8 encoding, Unicode can be used in a convenient and backwards compatible way in environments that were designed entirely around ASCII, like Unix. UTF-8 is the way in which Unicode is used under Unix, Linux, and similar systems. It is now time to make sure that you are well familiar with it and that your software supportsUTF-8 smoothly. Contents • What are UCS and ISO 10646? • What are combining characters? • What are UCS implementation levels? • Has UCS been adopted as a national standard? • What is Unicode? • So what is the difference between Unicode and ISO 10646? • What is UTF-8? • Who invented UTF-8? • Where do I find nice UTF-8 example files? • What different encodings are there? • What programming languages support Unicode? • How should Unicode be used under Linux? • How do I have to modify my software? • C support for Unicode and UTF-8 • How should the UTF-8 mode be activated? • How do I get a UTF-8 version of xterm? • How much of Unicode
  • Nill-1BER 97 the ORIGINS of CAUCASIAN CIVILIZATION: the CHRISTIAN COMPONENT R

    Nill-1BER 97 the ORIGINS of CAUCASIAN CIVILIZATION: the CHRISTIAN COMPONENT R

    Nill-1BER 97 THE ORIGINS OF CAUCASIAN CIVILIZATION: THE CHRISTIAN COMPONENT R. W. Thomson Harvard University Conference on "NATIONALISM AND SOCIAL CHA."iGE IN TRM-l"SCAUCASIA" Co-sponsored by Kennan Institute for Ad\'anced Russian Studies, The Wilson Center· and American Association for the Advancement of Slavic Studies April 24-25, 1980 ) R. W. Thomson Harvard University THE ORIGINS OF CAUCASIAN CIVILIZATION: THE CHRISTIAN C0f..1PONENT* The Caucasus has been home for members of the human race since the early Stone Age, yet it is only in comparatively recent times - in the last 1500 years or so - that the two most significant peoples of the area, the Armenians and the Georgians, have acquired truly individual cultures expressed in their own native languages. I shall not be concerned here with the origin of these peoples, with the thorny question of the mingling of newcomers and indigenous inhabitants, or with the development of social and material culture in the pre-Christian era. This paper will deal with Christian Armenia and .Georgia, for it was only with their conversion that the Armenians and Georgians developed their own scripts and native literatures. Not that they were illiterate and ignorant until then. Indeed, they had played a role in the Greco-Roman world, and in the Old Persian empire and the civilizations of the Near East that had preceded it. But with the development of their o~n literature and art in a Christian context the Armenians and Georgians set themselves apart from these other civilizations to a certain extent and moulded more truly national cultures out of the heritage they owed to Greece, Rome and Iran.
  • 'Links Between Scripts, Writing Systems, Orthographies, Fonts And

    'Links Between Scripts, Writing Systems, Orthographies, Fonts And

    April 2019 Field School in Bova, Calabria, IT Fantastic Languages and where to find them ‘Links between scripts, writing systems, orthographies, fonts and ethnolinguistic identities’ Tomasz Wicherkiewicz [email protected] Adam Mickiewicz University in Poznań, Poland Dept. of Language Policy & Minority Studies Minority Languages, Major Opportunities. Collaborative Research, Community Engagement and Innovative Educational Tools Standardization & Literacy Since at least the rise of nationalism, Westerners have in large part judged languages by whether they are written and standardized. As the colonial era came to an end across much of the world in the 1960s, this tendency intermingled with the rising developmentist impulse: what would be the place of the local, languages all over the world in educational and political projects of the post-colonial states across the globe? This led to a still-flourishing of orthography development for a large number of languages. The process has been even strengthened with the worldwide wave of language revival of the 1990s-2010s The language revival, however, is often~still directly associated with the standardization of its written form Linguists have generally claimed that script is something that does not belong to language, it is something secondary, rather left to culture scientists or historians. Even those sociolinguists, who deal with interrelations between scripts, writing systems and orthographies from one side and users’ societies and speech communities from the other, claim that the former are fundamentally independent of languages. Yet, they absolutely are not independent of language ideologies. On the other hand, scripts are thought by their speakers to be intrinsically related to their languages.
  • Revitalizing Endangered Languages

    Revitalizing Endangered Languages

    Downloaded from https://www.cambridge.org/core. IP address: 170.106.40.219, on 30 Sep 2021 at 21:18:31, subject to the Cambridge Core terms of use, available at https://www.cambridge.org/core/terms. https://www.cambridge.org/core/product/ADCBBA31190F259BA13525C769E92A9A Downloaded from https://www.cambridge.org/core. IP address: 170.106.40.219, on 30 Sep 2021 at 21:18:31, subject to the Cambridge Core terms of use, available at https://www.cambridge.org/core/terms. https://www.cambridge.org/core/product/ADCBBA31190F259BA13525C769E92A9A Revitalizing Endangered Languages Of the approximately 7,000 languages in the world, at least half may no longer be spoken by the end of the twenty-first century. Languages are endangered by a number of factors, including globalization, education pol- icies, and the political, economic, and cultural marginalization of minority groups. This guidebook provides ideas and strategies, as well as some background, to help with the effective revitalization of endangered languages. It covers a broad scope of themes including effective planning, benefits, well- being, economic aspects, attitudes, and ideologies. The chapter authors have hands-on experience of language revitalization in many countries around the world, and each chapter includes a wealth of examples, such as case studies from specific languages and language areas. Clearly and accessibly written, it is suitable for nonspecialists as well as for academic researchers and students interested in language revitalization. This book is also available as Open Access on Cambridge Core. justyna olko, director of the Center for Research and Practice in Cultural Continuity at the University of Warsaw, is engaged in revitalizing the Nahuatl language in Mexico and works with activists supporting other endangered languages, especially in the area of Poland.
  • Section 7.9, Combining Marks, and Also Section 2.11, Combining Characters

    Section 7.9, Combining Marks, and Also Section 2.11, Combining Characters

    The Unicode® Standard Version 13.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. © 2020 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 13.0. Includes index. ISBN 978-1-936213-26-9 (http://www.unicode.org/versions/Unicode13.0.0/) 1.
  • Proposal for Malayalam Script Root Zone Label Generation

    Proposal for Malayalam Script Root Zone Label Generation

    Proposal for Malayalam Script Root Zone Label Generation Rules – Second Public Comment Proceeding Publication Date: 23 June 2020 Prepared By: Internationalized Domain Name (IDN) Program, ICANN Org Public Comment Proceeding Important Information Links Open Date: 7 May 2020 Close Date: 17 June 2020 Announcement Staff Report 23 June 2020 Public Comment Proceeding View Comments Submitted Due Date: Staff Contact: Pitinan Kooarmornpatana Email: [email protected] Section I: General Overview and Next Steps The Neo-Brahmi Generation Panel (NBGP) was formed by nine communities that use scripts derived from the Brahmi script. NBGP has developed Root Zone Label Generation Rules (LGR) proposals for Bangla, Devanagari, Gujarati, Gurmukhi, Kannada, Malayalam, Oriya, Tamil and Telugu scripts. The Malayalam LGR proposal (LGR and supporting documentation) is being updated to address an inconsistency involving the conjunct "nta" and adjust the cross-script variants with Myanmar and Georgian scripts. As per the LGR Procedure, the updated proposal was posted for Public Comments to allow those who have not participated in the NBGP to make their views known. Based on feedback received, the NBGP will finalize the proposal for its evaluation and re-integration into the Label Generation Rules for the Root Zone. Section II: Contributors At the time this report was prepared, a total of two (2) community submissions had been posted to the forum. The contributors are listed below with initials noted. To the extent that quotations are used in the foregoing narrative (Section III), such citations will reference the contributor’s initials. Individuals: Name Affiliation (if provided) Initials Wil Tan WT 梁海 (Liang Hai) LH Section III: Summary of Comments General Disclaimer: This section intends to summarize broadly and comprehensively the comments submitted to this public comment proceeding but does not address every specific position stated by each contributor.