File Information
File: 05-lr/acl_arc_1_sum/cleansed_text/xml_by_section/intro/90/c90-3014_intro.xml
Size: 1,927 bytes
Last Modified: 2025-10-06 14:04:56
<?xml version="1.0" standalone="yes"?> <Paper uid="C90-3014"> <Title>A Phonological</Title> <Section position="2" start_page="0" end_page="0" type="intro"> <SectionTitle> 1, Introduction </SectionTitle> <Paragraph position="0"> syllable consists of all the segments that precede the neeleus and are tantosyllabic segments that follow the necleus. A syllable that has no coda is called &quot;open syllable&quot; : one with a coda is called &quot;closed syllable&quot;. According to the above definitions of a syllable structure, the Korean syllable can be described as follows : This paper has two main goals: one is to investigate the phonological &quot;knowledge base system for constructing a Korean speech recognition and synthesis system, the other is to show that our formalism is more describable than other systems employing the traditional phonological approaches\[I\] \[21.</Paragraph> <Paragraph position="1"> A language has its own sound patterns. By sound pattens we mean (1) set of sounds that occur is a language, (2) the permissible arrangement of the sounds in words and (3) the processing for adding, deleting, or changing sound \[3\].</Paragraph> <Paragraph position="2"> A speech recognition/synthesis system also needs a phonological knowledge base system (data base), and the rules which govern the sound sequences and the phonological processes.</Paragraph> <Paragraph position="3"> Traditinoally, a computational phonological systems have been described and classified in terms of 'Generative Phonology\[4\]', However most of those approaches are not sufficient to describe the various knowledge of a computational speech system.</Paragraph> <Paragraph position="4"> In this paper, we show the feasibility of phonological knowledge base system with a uriification-based formalism, and illustrate the flexibility of implementation and representation.</Paragraph> </Section> class="xml-element"></Paper>