DOCSLIB.ORG

Unicode Technical Report #14 Line Breaking Properties

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Unicode Technical Report #14 Line Breaking Properties Unicode Technical Report #14 Line Breaking Properties Revision 5 Authors Asmus Freytag Date August 20, 1999 This Version http://www.unicode.org/unicode/reports/tr14-5 Previous Version http://www.unicode.org/unicode/reports/tr14-4.html Latest Version http://www.unicode.org/unicode/reports/tr14 Summary This report presents the specification of line breaking properties for Unicode characters. Status of this document This document contains informative material and normative specifications which have been considered and approved by the Unicode Technical Committee for publication as a Technical Report and as part of the Unicode Standard, Version 3.0 (forthcoming). Any reference to version 3.0 of the Unicode Standard automatically includes this technical report. The content of all technical reports must be understood in the context of the appropriate version of the Unicode Standard. References in this technical report to sections of the Unicode Standard refer to the Unicode Standard, Version 3.0. See http://www.unicode.org/unicode/standard/versions/ for more information. This technical report may undergo further editorial work before the release of the Unicode Standard, Version 3.0. The contents of section 7.2 are preliminary. Please mail corrigenda and other comments to the authors. 1.0 Overview and Scope The Unicode Standard presents a summary of basic line-breaking behavior, but does not give a complete specification. This technical report provides the needed information in a way that reflects best practices. Normative line-breaking properties are assigned to those characters whose line breaking behavior must be identical across all implementations. Default, informative line-breaking properties for all other classes of characters are supplied as well. 2.0 Definitions All terms not defined here shall be as defined in the Unicode Standard. Line fitting - the process of determining the how much text will fit on a line of text, given the available space between the margins and the actual display width of the text. Overfull - a line that contains so much text that it does not fit in the space allotted, or only after unacceptable compression of the text. Underfull - a line that contains so little text that it ends too far from the margin, or one that would require unacceptable expansion when lines are justified. Line Break - the position in the text where one line ends and the next one starts. Line Break Opportunity - a place where a line is allowed to end. Whether a given position in the text is a valid line break opportunity depends on the line breaking rules in force, as well as on context. Line Breaking Property - A character property with mutually exclusive values, as set out in Table 1. Line breaking properties are used to determine the type of break. Copyright © 1998-1999 The Unicode Consortium. All Rights Reserved. Unicode Technical Report #14 Mandatory Break - a line must break following a character that has the mandatory break property. Also known as a forced break. Direct Break - a line break opportunity exists between two characters of given line breaking properties. In addition, if they are separated by one or more spaces, a break opportunity exists after the last space. This is indicated in the text as B ‡ A, where B is the character class of the character before and A is the character class of the character after the break. Indirect Break - no line breaking opportunity exists between two adjacent characters of given line breaking properties. However, if they are separated by one or more space characters, a break opportunity exists after the last space. This indicated in the text as B % A. Prohibited Break - no line breaking opportunity exists between two characters of given line breaking properties. This is indicated in the text as B ^ A. Line Breaking - the process of selecting that part of a text that can be displayed on a line. In other words, selecting one among several line breaking opportunities such that the resulting line is optimal (unless the user requested an explicit line break). Hyphenation — Hyphenation uses language specific rules to provide additional line breaking opportunities within a word. Hyphenation improves the layout of narrow columns, especially for languages with many longer words, such as German or Finnish. For the purpose of this document, it is assumed that hyphenation is equivalent to insertion of soft hyphen characters. All other aspects of hyphenation are outside the scope of this document. Value Line Breaking Property Examples Characters with this property BK * Mandatory Break NL, PS cause a line break. CR * Carriage Return CR cause a line break, except between CR and LF LF * Line Feed LF cause a line break, except between CR and LF CM * Combining Marks Combining Marks, prohibit a line break between the character and Conjoining Jamo the preceding character SG * Surrogates High Surrogates prohibit a break from a following low surrogate ZW * Zero Width Space ZWSP optional break IN Inseparable Leaders allow only indirect line breaks between pairs. GL * Non-breaking (“Glue”) NBSP, ZWNSP prohibit line breaks before or after. CB * Contingent Break Inline Objects provide a line break opportunity contingent on Opportunity additional information. SP * Space Space generally provide a line break opportunity after the character, enables indirect breaks BA Break Opportunity After Spaces, Hyphens generally provide a line break opportunity after the character BB Break Opportunity Before Punctuation used generally provide a line break opportunity before in dictionaries the character. B2 Break Opportunity Before EM Dash provide a line break opportunity before and after and After the character HY Hyphen Hyphen-Minus provide a line break opportunity after the character, except in numeric context NS Non Starter small kana allow only indirect line break before OP Opening “(“, “[“, “{“, etc. prohibit a line break after CL Closing “)”, “]”, “}”, etc. prohibit a line break before QU Ambiguous Quotation Quotation marks act like they are both opening and closing EX Exclamation “!”, “?” etc. prohibit line break before ID Ideographic Ideographs break before or after NU Numeric Digits form numeric expressions for line breaking purposes IS Infix Separator (Numeric) . , prevent breaks after any and before numeric SL Symbols allowing breaks / prevent a break before, and allow a break after AL Ordinary Alphabetic Alphabets and are alphabetic characters regular symbols PR Prefix (Numeric) $, £, ¥, etc. don't break in front of a numeric expression PO Postfix (Numeric) %, ¢, ‰, º don’t break following a numeric expression 2 Unicode Technical Report #14 SA Complex Context South East Asian: Provide a line break opportunity contingent on Thai, Lao, Khmer additional, language specific context analysis XX Unknown Unassigned are all characters with (as yet) unknown line breaking behavior or unassigned code positions Table 1 Line Breaking Properties (* = normative) 3.0 Description Lines are broken as result of either of two conditions. The first condition is the presence of an explicit line breaking character. The second condition results from a formatting algorithm having selected among available line breaking opportunities the particular one that results in the optimal layout of the text. The definition of optimal line break is outside the scope of this document. Different formatting algorithms may use different methods of determining an optimal break. For example, simple implementations just consider a line at a time, trying find a locally optimal line break. A common approach is to allow no compression and consider the longest line that fits. When compression is allowed, a locally optimal line break seeks to balance the relative merits of the resulting amounts compression and expansion for different line break candidates. More complex algorithms may take into account the interaction of line breaking decisions for the whole paragraph. TEX is a well known example of such a globally optimal strategy that may make complex tradeoffs to avoid unnecessary hyphenation and other legal, but inferior breaks. For the purpose of this document, what is important is not so much what defines the optimal amount of text on the line, but how line breaking opportunities are defined. Three principal styles of context analysis determine line-breaking opportunities. 1. Western (spaces and hyphens are used to determine breaks) 2. East Asian (lines can break anywhere, unless prohibited) 3. South East Asian (require morphological analysis) The first is commonly used for scripts employing the space character. The second is used with East Asian ideographic scripts. The third is used for scripts such as Thai, which do not use spaces, but which restrict word-breaks to syllable boundaries, the determination of which requires knowledge of the language comparable to that required by a hyphenation algorithm. NOTE: Korean may alternately use a space-based (style 1) instead of the style 2 context analysis. Space-based line breaking is often augmented by hyphenation. Some Unicode characters have explicit line breaking properties assigned to them. These can be used for the first and second type context analysis for line break opportunities. For multilingual text, styles one and two can be unified into a single set of specifications. NOTE: Interpretation of line breaking properties in bi-directional text takes place before applying rule L1. of the Unicode Bidirectional Algorithm. However, it is strictly independent of directional properties of the characters or of any auxiliary information determined by the application of rules of that algorithm. 4.0 Conformance • The line breaking behavior of characters with normative line breaking properties are described in The Unicode Standard. (See The Unicode Standard, Version 3.0, Chapters 6 and 13). Unless otherwise stated, the information in this technical report is not intended to supersede the normative specifications found in The Unicode Standard, but to organize the description in a different context and provide additional informative detail. • All line breaking properties are informative, except for the line breaking properties marked with a * in Table 1 Line Breaking Properties.
Load more

Recommended publications
  • Chapter 2 Working with Text: Basics Copyright
    Writer Guide Chapter 2 Working with Text: Basics Copyright This document is Copyright © 2021 by the LibreOffice Documentation Team. Contributors are listed below. You may distribute it and/or modify it under the terms of either the GNU General Public License (https://www.gnu.org/licenses/gpl.html), version 3 or later, or the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), version 4.0 or later. All trademarks within this guide belong to their legitimate owners. Contributors To this edition Rafael Lima Jean Hollis Weber Kees Kriek To previous editions Jean Hollis Weber Bruce Byfield Gillian Pollack Ron Faile Jr. John A. Smith Hazel Russman John M. Długosz Shravani Bellapukonda Kees Kriek Feedback Please direct any comments or suggestions about this document to the Documentation Team’s mailing list: [email protected] Note Everything you send to a mailing list, including your email address and any other personal information that is written in the message, is publicly archived and cannot be deleted. Publication date and software version Published April 2021. Based on LibreOffice 7.1 Community. Other versions of LibreOffice may differ in appearance and functionality. Using LibreOffice on macOS Some keystrokes and menu items are different on macOS from those used in Windows and Linux. The table below gives some common substitutions for the instructions in this document. For a detailed list, see the application Help. Windows or Linux macOS equivalent Effect Tools > Options LibreOffice >
    [Show full text]
  • The Kleene Language for Weighted Finite-State Programming: User Documentation, Version 0.9.4.0
    The Kleene Language for Weighted Finite-State Programming: User Documentation, Version 0.9.4.0 This Document is Work in Progress Corrections and Suggestions Are Welcome Kenneth R. Beesley SAP Labs, LLC P.O. Box 540475 North Salt Lake Utah 84054, USA [email protected] 19 May 2014 Copyright © 2014 SAP AG. Released under the Apache License, Version 2. http://www.apache.org/licenses/LICENSE-2.0.html Beesley i Preface What is Kleene? Kleene is a programming language that can be used to create many useful and efficient linguistic applications based on finite-state machines (FSMs). These applications include tokenizers, spelling checkers, spelling correc- tors, morphological analyzer/generators and shallow parsers. FSMs are also widely used in speech synthesis and speech recognition. Kleene allows programmers to define, build, manipulate and test finite- state machines using regular expressions and right-linear phrase-structure grammars; and Kleene supports variables, rule-like expressions, user-defined functions and familiar programming-language control syntax. The FSMs can include acceptors and two-projection transducers, either weighted un- der the Tropical Semiring or unweighted. If this makes no sense, the pur- pose of the book is to explain it. Pre-edited Kleene scripts can be run from the command line, and a graphical user interface is provided for interactive learning, programming and testing. Operating Systems Kleene runs on OS X and Linux, requiring Java version 1.5 or higher. Prerequisites This book assumes only superficial familiarity with regular languages, reg- ular relations and finite-state machines. While readers need not have any experience with finite-state program- ming, those who have no programming experience at all, e.g.
    [Show full text]
  • AIX Globalization
    AIX Version 7.1 AIX globalization IBM Note Before using this information and the product it supports, read the information in “Notices” on page 233 . This edition applies to AIX Version 7.1 and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 2010, 2018. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About this document............................................................................................vii Highlighting.................................................................................................................................................vii Case-sensitivity in AIX................................................................................................................................vii ISO 9000.....................................................................................................................................................vii AIX globalization...................................................................................................1 What's new...................................................................................................................................................1 Separation of messages from programs..................................................................................................... 1 Conversion between code sets.............................................................................................................
    [Show full text]
  • International Language Environments Guide
    International Language Environments Guide Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A. Part No: 806–6642–10 May, 2002 Copyright 2002 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, docs.sun.com, AnswerBook, AnswerBook2, Java, XView, ToolTalk, Solstice AdminTools, SunVideo and Solaris are trademarks, registered trademarks, or service marks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. SunOS, Solaris, X11, SPARC, UNIX, PostScript, OpenWindows, AnswerBook, SunExpress, SPARCprinter, JumpStart, Xlib The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry.
    [Show full text]
  • Singing in English in the 21St Century: a Study Comparing
    SINGING IN ENGLISH IN THE 21ST CENTURY: A STUDY COMPARING AND APPLYING THE TENETS OF MADELEINE MARSHALL AND KATHRYN LABOUFF Helen Dewey Reikofski Dissertation Prepared for the Degree of DOCTOR OF MUSICAL ARTS UNIVERSITY OF NORTH TEXAS August 2015 APPROVED:….……………….. Jeffrey Snider, Major Professor Stephen Dubberly, Committee Member Benjamin Brand, Committee Member Stephen Austin, Committee Member and Chair of the Department of Vocal Studies … James C. Scott, Dean of the College of Music Costas Tsatsoulis, Interim Dean of the Toulouse Graduate School Reikofski, Helen Dewey. Singing in English in the 21st Century: A Study Comparing and Applying the Tenets of Madeleine Marshall and Kathryn LaBouff. Doctor of Musical Arts (Performance), August 2015, 171 pp., 6 tables, 21 figures, bibliography, 141 titles. The English diction texts by Madeleine Marshall and Kathryn LaBouff are two of the most acclaimed manuals on singing in this language. Differences in style between the two have separated proponents to be primarily devoted to one or the other. An in- depth study, comparing the precepts of both authors, and applying their principles, has resulted in an understanding of their common ground, as well as the need for the more comprehensive information, included by LaBouff, on singing in the dialect of American Standard, and changes in current Received Pronunciation, for British works, and Mid- Atlantic dialect, for English language works not specifically North American or British. Chapter 1 introduces Marshall and The Singer’s Manual of English Diction, and LaBouff and Singing and Communicating in English. An overview of selected works from Opera America’s resources exemplifies the need for three dialects in standardized English training.
    [Show full text]
  • Metathesis Is Real, and It Is a Regular Relation A
    METATHESIS IS REAL, AND IT IS A REGULAR RELATION A Dissertation submitted to the Faculty of the Graduate School of Arts and Sciences of Georgetown University in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Linguistics By Tracy A. Canfield, M. S. Washington, DC November 17 , 2015 Copyright 2015 by Tracy A. Canfield All Rights Reserved ii METATHESIS IS REAL, AND IT IS A REGULAR RELATION Tracy A. Canfield, M.S. Thesis Advisor: Elizabeth C. Zsiga , Ph.D. ABSTRACT Regular relations are mathematical models that are widely used in computational linguistics to generate, recognize, and learn various features of natural languages. While certain natural language phenomena – such as syntactic scrambling, which requires a re-ordering of input elements – cannot be modeled as regular relations, it has been argued that all of the phonological constraints that have been described in the context of Optimality Theory can be, and, thus, that the phonological grammars of all human languages are regular relations; as Ellison (1994) states, "All constraints are regular." Re-ordering of input segments, or metathesis, does occur at a phonological level. Historically, this phenomenon has been dismissed as simple speaker error (Montreuil, 1981; Hume, 2001), but more recent research has shown that metathesis occurs as a synchronic, predictable phonological process in numerous human languages (Hume, 1998; Hume, 2001). This calls the generalization that all phonological processes are regular relations into doubt, and raises other
    [Show full text]
  • Typesetting Catalan Texts with TEX
    Typesetting Catalan Texts with TEX Gabriel Valiente Feruglio Universitat de les Illes Balears Departament de Ciencies Matematiques i Inforrnatica E-07071 Palma de Mallorca (Spain) Internet: dmi gvaO@ps. ui b . es Robert Fuster Universitat Politecnica de Valencia Departament de Matematica Aplicada Cami de Vera, 14. E-46071 Valencia (Spain) Internet: mat5rf c@cci. upv .es Abstract As with other non-American English languages, typesetting Catalan texts imposes some special requirements on TEX. These include a particular set of hyphenation patterns and support for a special ligature: unlike other Romanic languages, Catalan incorporates the middle point in the 11 digraph. Hyphenation rules for Catalan are reviewed in ths paper, after a short introduction to hyphenation by TEX. A minimal set of hyphenation patterns covering all Catalan accents and diacritics is also presented. A discussion about the 1'1 ligature concludes the paper. This work represents a first step towards the Catalan TLP (TEX Language Package), under development within the TWGMLC (Technical Working Group on Multiple Language Coordination), where the first author is chairing the Catalan linguistic subgroup. Resum Aixi com en altres llengiies, la composicio de textos escrits en catala demana requeriments especials a1 TEX. Aquests inclouen un conjunt particular de patrons de guionat, aixi com suport per a un lligam especial ja que, a diferencia d'altres llengiies romaniques, el catala incorpora el punt volat a1 digraf I'l. En aquest paper es fa una introduccio a1 guionat arnb TEX i es revisen les regles de guionat per a1 catala. Tanmateix, es presenta un conjunt minim de patrons de guionat que cobreix tots els accents i marques diacritiques del catala.
    [Show full text]
  • Department of English Linguistics School of English and American Studies Eötvös Loránd University Budapest, Hungary Table of Contents
    The Odd Yearbook 2014 Department of English Linguistics School of English and American Studies Eötvös Loránd University Budapest, Hungary Table of Contents Foreword ................................................................................................................................i Fodor, Brigitta: Scottish Vowel Length: Regular Vowel Length Alternations and the Raising of /ae/ in Scottish Standard English ........................................................................................ 1 Pándi, Julianna Sarolta: Flapping in American English: A Theoretical Approach .............. 14 Szalay, Tünde: L Vocalisation in Three English Dialects .................................................... 35 Szabó, Petra Florina: Social and Regional Variation and Intrusive /r/ ................................. 49 Szabó, Lilla Petronella: “You’re a good friend, bro!”—A Corpus-based Investigation of the Meanings of ‘bro’ ................................................................................................................. 81 Kiss, Angelika: A remark on the Individual/Stage-Level Predicate Distinction in English ... 98 Biczók, Bálint: Approaches to Antecedent-Contained Deletion ......................................... 110 Tomacsek, Vivien: Approaches to the Structure of English Small Clauses ......................... 128 Kucsera, Márton: Restrictive relative clauses in Alignment Syntax .................................. 155 Foreword This is the ninth volume in the series ODD Yearbook, which is the collection of undergraduate
    [Show full text]
  • DVB); Specification for Service Information (SI) in DVB Systems
    Final draft ETSI EN 300 468 V1.5.1 (2003-01) European Standard (Telecommunications series) Digital Video Broadcasting (DVB); Specification for Service Information (SI) in DVB systems European Broadcasting Union Union Européenne de Radio-Télévision EBU·UER 2 Final draft ETSI EN 300 468 V1.5.1 (2003-01) Reference REN/JTC-DVB-128 Keywords broadcasting, digital, DVB, MPEG, service, TV, video ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, send your comment to: [email protected] Copyright Notification No part may be reproduced except as authorized by written permission.
    [Show full text]
  • Control Characters in ASCII and Unicode
    Control characters in ASCII and Unicode Tens of odd control characters appear in ASCII charts. The same characters have found their way to Unicode as well. CR, LF, ESC, CAN... what are all these codes for? Should I care about them? This is an in-depth look into control characters in ASCII and its descendants, including Unicode, ANSI and ISO standards. When ASCII first appeared in the 1960s, control characters were an essential part of the new character set. Since then, many new character sets and standards have been published. Computing is not the same either. What happened to the control characters? Are they still used and if yes, for what? This article looks back at the history of character sets while keeping an eye on modern use. The information is based on a number of standards released by ANSI, ISO, ECMA and The Unicode Consortium, as well as industry practice. In many cases, the standards define one use for a character, but common practice is different. Some characters are used contrary to the standards. In addition, certain characters were originally defined in an ambiguous or loose way, which has resulted in confusion in their use. Contents Groups of control characters Control characters in standards o ASCII control characters o C1 control characters o ISO 8859 special characters NBSP and SHY o Control characters in Unicode Control characters in modern applications Character list o ASCII o C1 o ISO 8859 Categories Translations Character index Sources This article starts by looking at the history of control characters in standards. We then move to modern times.
    [Show full text]
  • Character Properties 4
    The Unicode® Standard Version 14.0 – Core Specification To learn about the latest version of the Unicode Standard, see https://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. © 2021 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 https://www.unicode.org/reporting.html. For information about the Unicode terms of use, please see https://www.unicode.org/copyright.html. The Unicode Standard / the Unicode Consortium; edited by the Unicode Consortium. — Version 14.0. Includes index. ISBN 978-1-936213-29-0 (https://www.unicode.org/versions/Unicode14.0.0/) 1.
    [Show full text]
  • Archisegment-Based Letter-To-Phone Conversion for Concatenative Speech Synthesis in Portuguese
    ARCHISEGMENT-BASED LETTER-TO-PHONE CONVERSION FOR CONCATENATIVE SPEECH SYNTHESIS IN PORTUGUESE Eleonora Cavalcante Albano and Agnaldo Antonio Moreira LAFAPE-IEL-UNICAMP, Campinas, SP, Brazil [email protected] ABSTRACT sive. Interestingly, such exceptions occur precisely where complexity at both the phonetic and the morphological level leads A letter-to-phone conversion scheme is proposed for Portuguese to ambiguity in phonological analysis. which excludes representation of allophonic detail. Phonetically unstable segments are treated as archisegments, their articulatory Take, for example, the representation of rhyme nasality, which weakness being analyzed in terms of feature underspecification. motivates the controversy whether Portuguese has distinctive Besides solving classical problems of allophony and allomorphy, nasal vowels [4,5]. Such nasality, which tends to be rather heavy this analysis provides an efficient principle for building a unit phonetically, is orthographically represented as 'm' or 'n' before a inventory for concatenative speech synthesis. word internal consonant (e.g., samba, santa, sanca) and as a tilde diacritic on the vowel before another vowel or word finally (e.g., 1. PHONOLOGY AND LETTER-TO-PHONE são, sã). This cannot be said to be a reasonable phonemic representation because /m/ and /n/ do not contrast in rhymes, a CONVERSION fact that orthography acknowledges by making the choice of one or the other letter dependent on the following consonant ('m' Concatenative speech synthesis depends crucially on the adequacy before 'p,b' and 'n' elsewhere). Nor can it be said to be a of the phonological analysis underlying its unit list. In the same reasonable allophonic representation because the phonetic way as intelligibility requires concatenative units to be based on realization of nasal rhymes shows no correspondence with the a consistent minimal set of allophones, quality requires enriching diacritic/digraph distinction.
    [Show full text]