PM's Circumflex, Syntax and Philosophy of Types

Total Page:16

File Type:pdf, Size:1020Kb

PM's Circumflex, Syntax and Philosophy of Types 9 PM’s Circumflex, Syntax and Philosophy of Types Kevin C. Klement From The Palgrave Centenary Companion to Principia Mathematica, edited by Nicholas Griffin and Bernard Linsky. New York: Palgrave Macmillan, 2013, pp. 218–246. (Author’s typesetting with matching pagination.) Introduction While second-order logic has its share of proponents, and specialized forms of type theory play a role in contemporary computer science and linguistics, I think it is fair to say that there’s relatively little contemporary interest in the sort of full-blown higher-order logic ex- emplified by the simple and ramified theories of types, at least for its own sake. One does not often see, for example, a new theory or devel- opment using it as its base system. The reasons for this are no doubt many. I think one major contributing factor, however, is a disconnect between the logicians who first advocated such an approach to logic and those who have been responsible for formulating it with modern standards of rigor. Principia Mathematica (PM), remains, it is fair to say, the best known exemplar of a type-theoretic approach to logic, but exactly what its type-theory is is far from agreed-upon. Whitehead and Russell are accused of unclarity, sloppiness or even outright con- fusion with regard to the syntax of their language, their system’s ax- iomatic foundations, and even its philosophical justification. More re- cent formulations of simple and ramified type-theories, such as those in Alonzo Church’s work, although formally unambiguous and irre- proachable, are seen as idiosyncratic and needlessly restrictive ways of codifying the “iterative conception” of sets or classes, more of a curiosity than a genuine rival to more flexible rival ways of codifying the same conception, such as ZFC and related set theories. But this is not surprising. The modern rigorous formulations have been done in detachment from, if not complete ignorance of, the real—or Russel- lian, at least—philosophical motivation of type theory, and are often done in ways that obscure that motivation. PM‘s Circumflex, Syntax and Philosophy of Types 219 It is not uncommon, for example, to find Church’s system of ram- ified types (or r-types), or something very similar, offered in place of an explanation of PM’s syntax (see, e.g., Church 1976, Linsky 1999, Urquhart 2003). Even if, contrary to what I shall argue, that sys- tem were equivalent to what PM was meant to be, or would become if properly reconstructed, to offer only that is unhelpful to would-be readers of PM. The syntax of that system is flatly unrecognizable in what one finds in PM itself. What is needed is an historically minded intepretation of the actual PM, but one that does not sacrifice contem- porary standards of rigor. Ideally, this would consist first in a formu- lation of the syntax of PM, which, once the definitions, abbreviations and conventions adopted by Whitehead and Russell (Peano’s dot nota- tion, the “typical ambiguity” method of suppressing type-indices, and so on) were accounted for, predicts precisely why and how the actual numbered propositions of PM appear the way they do. This should be presented alongside a philosophical explanation of the motivation for the type hierarchy. If successful, this project might show that even if Whitehead and Russell did not think of the formulation of a logical system and its syn- tax and semantics exactly the way contemporary logicians tend to, their approach had its own rhyme and reason. Contemporary prac- tices have been shaped to a large extent by the demands of logical meta-theory. While I do not agree with those who argue that Rus- sell’s views of logic are antithetical somehow to the very project of logical meta-theory,1 it was not his own focus. One cannot get very far in a metatheoretic proof without a full recursive definition of a well-formed expression of the object language, for example. If one’s aim is rather to use a given object language to state and demonstrate mathematical theorems, it perhaps suffices to make the notation clear enough that the mathematical content of those proofs is not obscured, leaving enough flexibility for refinements to the syntax to be made on the fly. Indeed, I suspect that Whitehead and Russell were deliber- ately less than fully explicit about the details of their system in hopes that the core of their mathematical proofs could be maintained even through substitution of a different precise understanding of the type system (cf. PM p. vii). Nevertheless, for the most part, it is still possi- ble to determine what they had in mind. This project, pursued in its entirety, is a large one. My aim here is a relatively modest one of getting clear about the syntax PM uses for expressions (variables and perhaps other terms) of higher-order: so-called “propositional functions”. My particular emphasis is on the use, or lack thereof, of the circumflex notation for function- abstraction. I argue that in many ways the notation used in PM is a 220 Kevin C. Klement kind of intermediate between the approach to the syntax of a the- ory of types found in Frege’s theory of functions of different levels, involving “incomplete” expressions with different structured kinds of incompleteness, and later, more familiar, devices for function ab- straction, such as the λ-abstracts of the typed λ-calculus, where one can form complete terms for functions of any type. The discussion is one small part of trying to get a better handle on the philosoph- ical justification, or perhaps inevitability, Russell thought there was for type-theory, a discussion which has been helped immensely in re- cent years by the availability of the surviving pre-PM manuscripts. I shall take for granted the conclusion reached not only by myself (Klement 2004, Klement 2010), but also by others (e.g., Landini 1998 and Stevens 2005), that these manuscripts show that even in 1910, Russell did not understand the type-hierarchy of PM as a hierarchy of entities of different logical kinds, whether those entities are to be understood as sets or classes at various stages of the iterative hier- archy or as abstract attributes-in-intension, “propositional functions” understood as mind- and language-independent real things. Indeed, my aim is largely to attempt to explain how this reading is compat- ible with taking the syntax of PM to include a very limited role for terms apparently standing “for” propositional functions, formed with the circumflex. In the appendices, I briefly sketch my reconstruction of the syn- tax and semantics of the 1910 first edition of PM (—I here bracket the question as to whether and to what extent the second edition is different—) though there are aspects to my reconstruction that re- quire more commentary and justification than what’s given here, par- ticularly with regard to those aspects that go beyond the discussion of the circumflex and notation for types. It is worth beginning our discussion with brief recaps of the con- trasting approaches. Frege’s approach On the Fregean approach, variables of different types (“levels” in Frege’s vocabulary) are literally of different shapes. A term for an object or an individual is a complete syntactic unit, whether simple or complex. An expression for a first-level function can be regarded as what is obtained from a complex term for an object by removing (one or more occurrences of) a simpler part which is itself a name for an object. In this way function ex- pressions are gappy, incomplete, or as Frege says, “unsaturated”. PM‘s Circumflex, Syntax and Philosophy of Types 221 A second-level function expression is obtained by removing a first- level function expression from a complex term, and thus, while gappy, is not gappy in precisely the same way that a first-level function ex- pression is. Only another incomplete expression can complete it. Compare the first-level function expression “F( )” and the second- level function expression “(9x) ::: x ::: ”.2 The latter’s argument ex- pression, unlike the former’s, must itself have a place to receive the “x”. The two expressions mutually saturate. This difference is re- flected even when variables are used in Frege’s notation. For a vari- able for second-level concepts, Frege writes not (e.g.) “M”, but “Mβ : : : β : : : ” (Frege 1964, §25). Thus the canonical notation for a type-2 function taking as argument a variable type-1 function is: (1) Mβ f(β) If “f( )” here is instantiated to some complexly defined instance, such as “(F() _ G( ))”, the mutually saturating mark, “β” is placed inside both gaps to create: (2) Mβ(F(β) _ G(β)) If “Mβ : : : β : : : ” is itself instantiated to a complexly defined instance, such as “(x)(::: x ::: ⊃ ::: x ::: )”, the mutual saturation takes place over the whole: (3) (x)((F(x) _ G(x)) ⊃ (F(x) _ G(x))) The expression (3) is of the form “Mβ f(β)”, but multiply so, since it can also be seen as the result of giving f( ) and Mβ : : : β : : : the values ((F() _ G( )) ⊃ (F() _ G( ))) and (x) ::: x ::: , or the values G( ) and (x)((F(x) _ ::: x ::: ) ⊃ (F(x) _ ::: x ::: )), respectively, instead, and so on. This approach suggests a certain kind of philosophy for the lev- els hierarchy itself. There is not necessarily one privileged decom- position of an expression into function and argument. A function expression is not necessarily one unified “piece” of notation; there is no such thing as a “function term”, and hence, no such thing as placing a term of the wrong sort where a term of another sort ought to go.
Recommended publications
  • Ffontiau Cymraeg
    This publication is available in other languages and formats on request. Mae'r cyhoeddiad hwn ar gael mewn ieithoedd a fformatau eraill ar gais. [email protected] www.caerphilly.gov.uk/equalities How to type Accented Characters This guidance document has been produced to provide practical help when typing letters or circulars, or when designing posters or flyers so that getting accents on various letters when typing is made easier. The guide should be used alongside the Council’s Guidance on Equalities in Designing and Printing. Please note this is for PCs only and will not work on Macs. Firstly, on your keyboard make sure the Num Lock is switched on, or the codes shown in this document won’t work (this button is found above the numeric keypad on the right of your keyboard). By pressing the ALT key (to the left of the space bar), holding it down and then entering a certain sequence of numbers on the numeric keypad, it's very easy to get almost any accented character you want. For example, to get the letter “ô”, press and hold the ALT key, type in the code 0 2 4 4, then release the ALT key. The number sequences shown from page 3 onwards work in most fonts in order to get an accent over “a, e, i, o, u”, the vowels in the English alphabet. In other languages, for example in French, the letter "c" can be accented and in Spanish, "n" can be accented too. Many other languages have accents on consonants as well as vowels.
    [Show full text]
  • Diacritics-ELL.Pdf
    Diacritics J.C. Wells, University College London Dkadvkxkdw avf ekwxkrhykwjkrh qavow axxadjfe xs pfxxfvw sg xjf aptjacfx, gsv f|aqtpf xjf adyxf addfrx sr xjf ‘ kr dag‘. M swx parhyahf svxjshvatjkfw cawfe sr xjf Laxkr aptjacfx qaof wsqf ywf sg ekadvkxkdw, aw kreffe es xjswf cawfe sr sxjfv aptjacfxw are {vkxkrh w}wxfqw. Tjf gsdyw sg xjkw avxkdpf kw sr xjf vspf sg ekadvkxkdw kr xjf svxjshvatj} sg parhyahfw {vkxxfr {kxj xjf Laxkr aptjacfx. Ireffe, xjf svkhkr sg wsqf pfxxfvw xjax avf rs{ a wxareave tavx sg xjf aptjacfx pkfw kr xjf ywf sg ekadvkxkdw. Tjf pfxxfv G {aw krzfrxfe kr Rsqar xkqfw aw a zavkarx sg C, ekwxkrhykwjfe c} xjf dvswwcav sr xjf ytwxvsof. Tjf pfxxfv J {aw rsx ekwxkrhykwjfe gvsq I, rsv U gvsq V, yrxkp xjf 16xj dfrxyv} (Saqtwsr 1985: 110). Tjf rf{ pfxxfv 1 kw sczksywp} a zavkarx sr r are ws dsype cf wffr aw krdsvtsvaxkrh a ekadvkxkd xakp. Dkadvkxkdw tvstfv, xjsyhj, avf wffr aw qavow axxadjfe xs a cawf pfxxfv. Ir xjkw wfrwf, m y 1 es rsx krzspzf ekadvkxkdw. Tjf f|xfrwkzf ywf sg ekadvkxkdw xs wyttpfqfrx xjf Laxkr aptjacfx kr dawfw {jfvf kx {aw wffr aw kraefuyaxf gsv xjf wsyrew sg sxjfv parhyahfw kw hfrfvapp} axxvkcyxfe xs xjf vfpkhksyw vfgsvqfv Jar Hyw (1369-1415), {js efzkwfe a vfgsvqfe svxjshvatj} gsv C~fdj krdsvtsvaxkrh 9addfrxfe: pfxxfvw wydj aw ˛ ¹ = > ?. M swx ekadvkxkdw avf tpadfe acszf xjf cawf pfxxfv {kxj {jkdj xjf} avf awwsdkaxfe. A gf{, js{fzfv, avf tpadfe cfps{ kx (aw “) sv xjvsyhj kx (aw B). 1 Laxkr pfxxfvw dsqf kr ps{fv-dawf are yttfv-dawf zfvwksrw.
    [Show full text]
  • 13647: Illinois DOT System ILDOTS3K
    ® ENGINEERING COMPANY INC. 51 Winthrop Road System Overview Chester, Connecticut 06412-0684 Illinois DOT System Model: Phone: (860) 526-9504 ILDOTS3K (01-0617049-01) Internet: www.whelen.com Sales e-mail: [email protected] Customer Service e-mail: [email protected] Warnings to Installers Whelen’s emergency vehicle warning devices must be properly mounted and wired in order to be effective and safe. Read and follow all of Whelen’s written instructions when installing or using this device. Emergency vehicles are often operated under high speed stressful conditions which must be accounted for when installing all emergency warning devices. Controls should be placed within convenient reach of the operator so that they can operate the system without taking their eyes off the roadway. Emergency warning devices can require high electrical voltages and/or currents. Properly protect and use caution around live electrical connections.Grounding or shorting of electrical connections can cause high current arcing, which can cause personal injury and/or vehicle damage, including fire. Many electronic devices used in emergency vehicles can create or be affected by electromagnetic interference. Therefore, after installation of any electronic device it is necessary to test all electronic equipment simultaneously to insure that they operate free of interference from other components within the vehicle. Never power emergency warning equipment from the same circuit or share the same grounding circuit with radio communication equipment. All devices should be mounted in accordance with the manufacturer’s instructions and securely fastened to vehicle elements of sufficient strength to withstand the forces applied to the device. Driver and/or passenger air bags (SRS) will affect the way equipment should be mounted.
    [Show full text]
  • List of Approved Special Characters
    List of Approved Special Characters The following list represents the Graduate Division's approved character list for display of dissertation titles in the Hooding Booklet. Please note these characters will not display when your dissertation is published on ProQuest's site. To insert a special character, simply hold the ALT key on your keyboard and enter in the corresponding code. This is only for entering in a special character for your title or your name. The abstract section has different requirements. See abstract for more details. Special Character Alt+ Description 0032 Space ! 0033 Exclamation mark '" 0034 Double quotes (or speech marks) # 0035 Number $ 0036 Dollar % 0037 Procenttecken & 0038 Ampersand '' 0039 Single quote ( 0040 Open parenthesis (or open bracket) ) 0041 Close parenthesis (or close bracket) * 0042 Asterisk + 0043 Plus , 0044 Comma ‐ 0045 Hyphen . 0046 Period, dot or full stop / 0047 Slash or divide 0 0048 Zero 1 0049 One 2 0050 Two 3 0051 Three 4 0052 Four 5 0053 Five 6 0054 Six 7 0055 Seven 8 0056 Eight 9 0057 Nine : 0058 Colon ; 0059 Semicolon < 0060 Less than (or open angled bracket) = 0061 Equals > 0062 Greater than (or close angled bracket) ? 0063 Question mark @ 0064 At symbol A 0065 Uppercase A B 0066 Uppercase B C 0067 Uppercase C D 0068 Uppercase D E 0069 Uppercase E List of Approved Special Characters F 0070 Uppercase F G 0071 Uppercase G H 0072 Uppercase H I 0073 Uppercase I J 0074 Uppercase J K 0075 Uppercase K L 0076 Uppercase L M 0077 Uppercase M N 0078 Uppercase N O 0079 Uppercase O P 0080 Uppercase
    [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]
  • Design and Positioning of Diacritical Marks in Latin Typefaces Authors
    Turčić et al.: Design and Positioning of Diacritical..., acta graphica 22(2010)3-4, 5-15 udc 655.244 original scientific paper received: 07-12-2010 acta graphica 185 accepted: 23-02-2011 Design and Positioning of Diacritical Marks in Latin Typefaces Authors Maja Turčić1*, Antun Koren2, Vesna Uglješić1, Ivan Rajković1 1Polytechnic of Zagreb 2Faculty of Graphic Arts, Croatia University of Zagreb, Croatia *E-mail: [email protected] Abstract: This paper presents relevant information concerning the types, shape and posi- tioning of diacritical marks in Latin typefaces. The aim is to increase the aware- ness of the importance of diacritics, their design and use. The design of the low- ercase dcroat letter presents a particular problem, because it is present only in the Croatian and Vietnamese script and is therefore often incorrectly designed or it is missing the respective font. Data on the most common methods of shaping and positioning of this diacritical sign was collected by measuring the geometry of the dcroat letter in various fonts. Most common designers’ mistakes were shown and evaluated. Suggestions for the design of diacritical marks are proposed taking into account asymmetry, width, uppercase, vertical and horizontal positioning and cul- tural preferences. Keywords: Diacritical Mark, Typography, Character Design 1. Introduction characters in a particular language. Diacritics are signs that change the meaning or the pro- Despite a large number of fonts, available nunciation of certain letters, and without them, technology (both software and hardware), and correct grammar and written communication technical capabilities in the form of coding come into question. systems, there are many fonts that lack certain characters, thus disturbing proper written com- When designing diacritics one should be munication of non-Western Latin script users.
    [Show full text]
  • The Brill Typeface User Guide & Complete List of Characters
    The Brill Typeface User Guide & Complete List of Characters Version 2.06, October 31, 2014 Pim Rietbroek Preamble Few typefaces – if any – allow the user to access every Latin character, every IPA character, every diacritic, and to have these combine in a typographically satisfactory manner, in a range of styles (roman, italic, and more); even fewer add full support for Greek, both modern and ancient, with specialised characters that papyrologists and epigraphers need; not to mention coverage of the Slavic languages in the Cyrillic range. The Brill typeface aims to do just that, and to be a tool for all scholars in the humanities; for Brill’s authors and editors; for Brill’s staff and service providers; and finally, for anyone in need of this tool, as long as it is not used for any commercial gain.* There are several fonts in different styles, each of which has the same set of characters as all the others. The Unicode Standard is rigorously adhered to: there is no dependence on the Private Use Area (PUA), as it happens frequently in other fonts with regard to characters carrying rare diacritics or combinations of diacritics. Instead, all alphabetic characters can carry any diacritic or combination of diacritics, even stacked, with automatic correct positioning. This is made possible by the inclusion of all of Unicode’s combining characters and by the application of extensive OpenType Glyph Positioning programming. Credits The Brill fonts are an original design by John Hudson of Tiro Typeworks. Alice Savoie contributed to Brill bold and bold italic. The black-letter (‘Fraktur’) range of characters was made by Karsten Lücke.
    [Show full text]
  • Federal Highway Administration, DOT § 393.11
    Federal Highway Administration, DOT § 393.11 § 393.11 Lighting devices and reflec- diately following Table 1. All lighting tors. devices on motor vehicles placed in op- eration after March 7, 1989, must meet The following Table 1 sets forth the the requirements of 49 CFR 571.108 in required color, position, and required effect at the time of manufacture of lighting devices by type of commercial the vehicle. Motor vehicles placed in motor vehicle. Diagrams illustrating operation on or before March 7, 1989, the locations of lighting devices and must meet either the requirements of reflectors, by type and size of commer- this subchapter or part 571 of this title cial motor vehicle, are shown imme- in effect at the time of manufacture. 679 VerDate 27-NOV-96 13:37 Jan 05, 1997 Jkt 167198 PO 00000 Frm 00679 Fmt 8010 Sfmt 8010 E:\CFR\167198.156 167198 VerDate 27-NOV-96 13:37Jan05,1997 Jkt167198 PO00000 Frm00680 Fmt8010 Sfmt8010 E:\CFR\167198.156 167198 § TABLE 1.ÐREQUIRED COMMERCIAL VEHICLE LIGHTING EQUIPMENT 393.11 Height above road surface in Item on the vehicle Quantity Color Location Position inches measured from the cen- Required lighting de- ter of the lamp at curb weight vices/vehicles Headlamps ............................................. 2 At Least ... White ....... Front ................. On the front at the same height, an Not less than 22 nor more than A, B, C equal number at each side of the 54. vertical centerline as far apart as practicable. Turn Signal (Front) See Footnotes #2 & 2 .................. Amber ...... At or Near Front One on each side of the vertical cen- Not less than 15 nor more than A, B, C 12.
    [Show full text]
  • Proposal for "Swedish International" Keyboard
    ISO/IEC JTC 1/SC 35 N 0748 DATE: 2005-01-31 ISO/IEC JTC 1/SC 35 User Interfaces Secretariat: Association Française de Normalisation (AFNOR) TITLE: Proposal for "Swedish International" keyboard SOURCE: Karl Ivar Larsson, Swedish Expert STATUS: FYI DATE: 2005-01-31 DISTRIBUTION: P and O members of JTC1/SC35 MEDIUM: E NO. OF PAGES: 8 Secretariat ISO/IEC JTC 1/SC 35 – Nathalie Cappel-Souquet – 11 Avenue Francis de Pressensé 93571 St Denis La Plaine Cedex France Telephone: + 33 1 41 62 82 55; Facsimile: + 33 1 49 17 91 29 e-mail: [email protected] LWP Consulting R 04/0-3 Notes: 1. This document was handed out in the SC35 Stockholm meeting 2004-11-24. 2. The proposal contained in the document relates to Swedish standardization, and at present not to any SC35 activities. Contents 1 Scope ...................................................................................................................................................................3 2 Characters added ...............................................................................................................................................3 2.1 Diacritical marks.................................................................................................................................................3 2.2 Special-shape letters..........................................................................................................................................3 2.3 Other characters.................................................................................................................................................3
    [Show full text]
  • Iso/Iec Jtc1/Sc2/Wg2 N4191
    ISO/IEC JTC1/SC2/WG2 N4191 Universal Multiple-Octet Coded Character Set International Organization for Standardization Organisation Internationale de Normalisation Международная организация по стандартизации Doc Type: Working Group Document DRAFT 3 – 2011-12-05 Title: Proposal to add Lithuanian accented letters to the UCS Source: Vilnius University, the State Commission of the Lithuanian language, Lithuanian Standards Board Status: Lithuanian Standards Board Contribution Action: For consideration by JTC1/SC2/WG2 and UTC Date: 2011-XX-XX 1. Introduction 2. Proposed characters 3. Rationale 3.1. Lithuanian alphabet 3.2. Lithuanian accented letters 3.3. 8-bit single-byte encoding (National standard code tables) 3.4. Multiple-octet encoding in the ISO/IEC 10646 4. Samples 5. Rendering of the sequences 6. References Addendum I Addendum II Proposal Summary Form 1. Introduction The alphabet of standard modern Lithuanian contains only nine letters with diacritical marks: Ąą, Čč, Ęę, Ėė, Įį, Šš, Ųų, Ūū, Žž. In addition to these, there are optional accent marks, which signify word stress together with its syllabic intonation (in a manner similar to that of the accent signs in ancient Greek). Although most of ordinary Lithuanian writing is done without using stress marks – in fact with the nine letters with phonetic diacritics shown above – the stress signs are used in dictionaries, grammars, manuals for language study, and other such materials. Even in the ordinary texts optional accent marks can be, and are, occasionally used to prevent ambiguity. In standard modern Lithuanian there are three accent (stress) signs, which look like those in ancient (polytonic) Greek: acute ( ´ ), grave ( ` ), and circumflex ( ˜ ).
    [Show full text]
  • Comments on Cedilla and Comma Below (Revision 2)
    Comments on cedilla and comma below (revision 2) Denis Moyogo Jacquerye <[email protected]> 2013-07-30 1. Summary The document provides comments on the recent discussion about cedilla and comma below and the proposal to add characters with invariant cedilla. With the evidence found, our conclusion is that the cedilla can have several forms, including that of the comma below or similar shapes. Adding characters with invariant cedilla would only increase the confusion and could lead to instable data as is the case with Romanian. The right solution to this problem is the same as for other preferred glyph variation: custom fonts or multilingual smart fonts, better application support for language tagging and font technologies. 2. Discussion In the Unicode Standard the cedilla and comma below are two different combining diacritical marks both inherited from previous character encodings. This distinction between those marks has not always been made, like in ISO 8859-2, or before computer encodings where they were used interchangibly based on the font style. The combining cedilla character is de facto a cedilla that can take several shapes or forms, and the combining comma below is a non contrastive character only representing a glyph variant of that cedilla as historically evidence shows. Following discussion about the Marshallese forms used in LDS publications on the mpeg-OT-spec mailing list, Eric Muller’s document (L2/13-037) raises the question of the differentiation between the cedilla and the comma below as characters in precomposed Latvian characters with the example of Marshallese that uses these but with a different preferred form.
    [Show full text]
  • A Comparative Analysis of Arabic Text Steganography
    applied sciences Review A Comparative Analysis of Arabic Text Steganography Reema Thabit 1,* , Nur Izura Udzir 1,* , Sharifah Md Yasin 1 , Aziah Asmawi 1 , Nuur Alifah Roslan 1 and Roshidi Din 2 1 Faculty of Computer Science and Information Technology, Universiti Putra Malaysia, UPM, Serdang 43400, Selangor Darul Ehsan, Malaysia; [email protected] (S.M.Y.); [email protected] (A.A.); [email protected] (N.A.R.) 2 School of Computing, College of Arts and Sciences, Universiti Utara Malaysia, Sintok 06010, Kedah, Malaysia; [email protected] * Correspondence: [email protected] (R.T.); [email protected] (N.I.U.) Abstract: Protecting sensitive information transmitted via public channels is a significant issue faced by governments, militaries, organizations, and individuals. Steganography protects the secret information by concealing it in a transferred object such as video, audio, image, text, network, or DNA. As text uses low bandwidth, it is commonly used by Internet users in their daily activities, resulting a vast amount of text messages sent daily as social media posts and documents. Accordingly, text is the ideal object to be used in steganography, since hiding a secret message in a text makes it difficult for the attacker to detect the hidden message among the massive text content on the Internet. Language’s characteristics are utilized in text steganography. Despite the richness of the Arabic language in linguistic characteristics, only a few studies have been conducted in Arabic text steganography. To draw further attention to Arabic text steganography prospects, this paper reviews the classifications of these methods from its inception.
    [Show full text]