forked from kripken/speak.js
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathadd_language.html
executable file
·161 lines (155 loc) · 9.75 KB
/
add_language.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
<META NAME="generator" CONTENT="http://txt2tags.sf.net">
</HEAD><BODY BGCOLOR="white" TEXT="black">
<FONT SIZE="4">
</FONT></CENTER>
<HR NOSHADE SIZE=1>
<H2>6. ADDING OR IMPROVING A LANGUAGE</H2>
<HR NOSHADE SIZE=1>
<P>
Most of the work doesn't need any programming knowledge. Just an understanding of the language, an awareness of its features, patience and attention to detail. Wikipedia is a good source of basic phonetic information, eg <A HREF="http://en.wikipedia.org/wiki/Vowel">http://en.wikipedia.org/wiki/Vowel</A>.
</P>
<P>
In many cases it should be fairly easy to add a rough implementation of a new language, hopefully enough to be intelligible. After that it's a gradual process of improvement.
</P>
<HR NOSHADE SIZE=1>
<H3>6.1 Language Code</H3>
<P>
Generally, the language's international <A HREF="http://en.wikipedia.org/wiki/ISO_639-1">ISO 639-1</A> code is used to identify the language. It is used in the filenames which contain the language's data. In the examples below the code <B>"fr"</B> is used as an example. Replace this with the code of your language.
</P>
<P>
If the language does not have a 2-letter ISO_639-1 code, then use the 3-letter ISO_639-3 code. Language codes may differ from country codes.
</P>
<P>
It is possible to have different variants of a language for different dialects. For example the sound of some phonemes are changed, or some of the pronunciation rules differ.
</P>
<HR NOSHADE SIZE=1>
<H3>6.2 Language Files</H3>
<P>
The following files are needed for your language.
</P>
<UL>
<LI><B>espeak-data/voices/fr</B>. The voice file. This gives the language name and may set some options.
<P></P>
<LI><B>phsource/ph_french</B>. The phoneme definition file. This contains phoneme definitions for the vowels and consonants which the language uses. Usually it will contain mostly vowels. Most consonants will be inherited from the common phoneme definitions in the master phoneme file, <B>phsource/phonemes</B>. The master phoneme file needs to be edited to call your new ph_french file.
<P></P>
<LI><B>dictsource/fr_rules</B>. This contains the spelling-to-phoneme translation rules.
<P></P>
<LI><B>dictsource/fr_list</B>. This contains pronunciations for numbers, letter and symbol names, and words with exceptional pronunciations. It also gives attributes such as "unstressed" and "pause" to some common words.
</UL>
<P>
The <B>fr_rules</B> and <B>fr_list</B> files are compiled to produce the file <B>espeak-data/fr_dict</B>, which eSpeak uses when it is speaking.
</P>
<HR NOSHADE SIZE=1>
<H3>6.3 Voice File</H3>
<P>
Each language needs a voice file in <B>espeak-data/voices</B> or <B>espeak-data/voices/test</B>. The filename of the default voice for a language should be the same as the language code (eg. "fr" for French).
</P>
<P>
Details of the contents of voice files are given in <A HREF="http://espeak.sf.net/voices.html">voices.html</A>.
</P>
<P>
The simplest voice file would contain just 2 lines to give the language name and language code, eg:
</P>
<PRE>
name french
language fr
</PRE>
<P></P>
<P>
This language code specifies which phoneme table and dictionary to use (i.e. <B>phonemetable fr</B> and <B>espeak-data/fr_dict</B>) to be used. If needed, these can be overridden by <B>phonemes</B> and <B>dictionary</B> attributes in the voice file. For example you may want to start the implementation of a new language by using the phoneme table of an existing language.
</P>
<HR NOSHADE SIZE=1>
<H3>6.4 Phoneme Definition File</H3>
<P>
You must first decide on the set of phonemes (vowel and consonant sounds) for the language. These should be defined in a phoneme definition file <B>ph_xxxx</B>, where "ph_xxxx" is the name of your language. A reference to this file is then included at the end of the master phoneme file, <B>phsource/phonemes</B>, eg:
</P>
<PRE>
phonemetable fr base
include ph_french
</PRE>
<P></P>
<P>
This example defines a phoneme table <B>"fr"</B> which inherits the contents of phoneme table <B>"base"</B>. Its contents are found in the file <B>ph_french</B>.
</P>
<P>
The <B>base</B> phoneme table contains definitions of a basic set of consonants, and also some "control" phonemes such as stress marks and pauses. These are defined in <B>phsource/phonemes</B>. The phoneme table for a language will inherit these, or alternatively it may inherit the phoneme table of another language which in turn inherits the <B>base</B> phoneme table.
</P>
<P>
The phonemes file for the language defines those additional phonemes which are not inherited (generally the vowels and diphthongs, plus any additional consonants that are needed), or phonemes whose definitions differ from the inherited version (eg. the redefinition of a consonant).
</P>
<P>
Details of phonemes files are given in <A HREF="http://espeak.sf.net/phontab.html">phontab.html</A>.
</P>
<P>
The <B>Compile phoneme data</B> function of the <B>espeakedit</B> program compiles the phonemes files of all languages to produce the files <B>espeak-data/phontab</B>, <B>phonindex</B>, and <B>phondata</B> which are used by eSpeak.
</P>
<P>
For many languages, the consonant phonemes which are already available in eSpeak, together with the available vowel files which can be used to define vowel phonemes, will be sufficient. At least for an initial implementation.
</P>
<HR NOSHADE SIZE=1>
<H3>6.5 Dictionary Files</H3>
<P>
Once the language's phonemes have been defined, then pronunciation dictionary data can be produced in order to translate the language's source text into phonemes. This consists of two source files: <B>fr_rules</B> (the spelling to phoneme rules) and <B>fr_list</B> (an exceptions list, and attributes of certain words). The corresponding compiled data file is <B>espeak-data/fr_dict</B> which is produced from <B>fr_rules</B> and <B>fr_list</B> sources by the command:
</P>
<BLOCKQUOTE>
<CODE>espeak --compile=fr</CODE>.
</BLOCKQUOTE>
<P></P>
<P>
Or by using the <B>espeakedit</B> program.
</P>
<P>
Details of the contents of the dictionary files are given in <A HREF="http://espeak.sf.net/dictionary.html">dictionary.html</A>.
</P>
<P>
The <B>fr_list</B> file contains:
</P>
<UL>
<LI>Pronunciations which exceptions to the rules in fr_rules, (eg. foreign names).
<LI>Pronunciation of letter names, symbol names, and punctuation names.
<LI>Pronunciation of numbers.
<LI>Attributes for words. For example, common function words which should not be stressed, or conjunctions which should be preceded by a pause.
</UL>
<HR NOSHADE SIZE=1>
<H3>6.6 Program Code</H3>
<P>
The behaviour of the eSpeak program is controlled by various options such as:
</P>
<UL>
<LI>Default rules for which syllable of a word has the main stress.
<LI>Relative lengths and amplitude of vowels in stressed and unstressed syllables.
<LI>Which intonation tunes to use.
<LI>Rules for speaking numbers.
</UL>
<P>
The function SetTranslator() at the start of the source code file tr_languages.cpp recognizes the language code and sets the appropriate options. For a new language, you would add its language code and the required options in SetTranslator(). However, this may not be necessary during testing because most of the options can also be set in the voice file in espeak-data/voices (see <A HREF="http://espeak.sf.net/voices.html">Voice files</A>).
</P>
<HR NOSHADE SIZE=1>
<H3>6.7 Improving a Language</H3>
<P>
Listen carefully to the eSpeak voice. Try to identify what sounds wrong and what needs to be improved.
</P>
<UL>
<LI>Make the spelling-to-phoneme translation rules more accurate, including the position of stressed syllables within words. Some languages are easier than others. I expect most are easier than English.
<P></P>
<LI>Improve the sounds of the phonemes. It may be that a phoneme should sound different depending on adjacent sounds, or whether it's at the start or the end of a word, between vowels, in a stressed or unstressed syllable, etc. This may consist of making small adjustments to vowel and diphthong quality or length, or adjusting the strength of consonants. Phoneme definitions can include conditional statements which can be used to change the sound of a phoneme depending on its environment. Bigger changes may be recording new or replacement consonant sounds, or may even need program code to implement new types of sounds.
<P></P>
<LI>Some common words should be added to the dictionary (the fr_list file for the language) with an "unstressed" attribute <B>$u</B> or <B>$u+</B> (eg. in English, words such as "the", "is", "had", "my", "she", "of", "in", "some"), or should be preceded by a short pause (such as "and", "but", "which"), or have other attributes, in order to make the speech flow better.
<P></P>
<LI>Improve the rhythm of the speech by adjusting the relative lengths of vowels in different contexts, eg. stressed/unstressed syllable, or depending on the following phonemes. This is important for making the speech sound good for the language.
<P></P>
<LI>Make new intonation "tunes" for statements or questions (see <A HREF="http://espeak.sf.net/intonation.html">Intonation</A>).
</UL>
<P>
<B>If you are interested in working on a language, please contact me so that I can set up the initial data and discuss the features of the language.</B>
</P>
<P>
For most of the eSpeak voices, I do not speak or understand the language, and I do not know how it should sound. I can only make improvements as a result of feedback from speakers of that language. If you want to help to improve a language, listen carefully and try to identify individual errors, either in the spelling-to-phoneme translation, the position of stressed syllables within words, or the sound of phonemes, or problems with rhythm and vowel lengths.
</P>
<HR NOSHADE SIZE=1>
<!-- html code generated by txt2tags 2.3 (http://txt2tags.sf.net) -->
<!-- cmdline: txt2tags -t html add_lang.txt -->
</BODY></HTML>