| 186 | With the files generated by the Transcription tool, we can now create a first instance of the NLP components in the TTS system for our language. |
| 187 | |
| 188 | We add support for our language to MARY TTS by creating a new config file in the folder MARY TTS\conf. By convention the file is called <locale>.config. It tells the MARY server which TTS modules to load, and which data files to use. |
| 189 | |
| 190 | The following is an example for Turkish (locale "tr"). |
| 191 | |
| 192 | {{{ |
| 193 | ########################################################################## |
| 194 | # MARY TTS configuration file tr.config |
| 195 | ########################################################################## |
| 196 | |
| 197 | name = tr |
| 198 | tr.version = 4.0.0 |
| 199 | |
| 200 | provides = a-language |
| 201 | |
| 202 | requires = \ |
| 203 | marybase |
| 204 | |
| 205 | |
| 206 | ########################################################################### |
| 207 | ############################## The Modules ############################### |
| 208 | ########################################################################### |
| 209 | modules.classes.list = \ |
| 210 | marytts.modules.JPhonemiser(tr.) \ |
| 211 | marytts.modules.MinimalisticPosTagger(tr,tr.) \ |
| 212 | |
| 213 | |
| 214 | #################################################################### |
| 215 | ####################### Module settings ########################### |
| 216 | #################################################################### |
| 217 | |
| 218 | # Phonemiser settings |
| 219 | tr.allophoneset = MARY_BASE/lib/modules/tr/lexicon/allophones.tr.xml |
| 220 | tr.lexicon = MARY_BASE/lib/modules/tr/lexicon/tr_lexicon.fst |
| 221 | tr.lettertosound = MARY_BASE/lib/modules/tr/lexicon/tr.lts |
| 222 | #tr.userdict = MARY_BASE/lib/modules/tr/lexicon/userdict.txt |
| 223 | |
| 224 | # POS tagger settings |
| 225 | tr.partsofspeech.fst = MARY_BASE/lib/modules/tr/tagger/tr_pos.fst |
| 226 | tr.partsofspeech.punctuation = ,.?!; |
| 227 | |
| 228 | }}} |
| 229 | |
| 230 | |
| 231 | It can be seen that the tr.config file refers to the following files: |
| 232 | |
| 233 | {{{ |
| 234 | MARY_BASE/lib/modules/tr/lexicon/allophones.tr.xml |
| 235 | MARY_BASE/lib/modules/tr/lexicon/tr_lexicon.fst |
| 236 | MARY_BASE/lib/modules/tr/lexicon/tr.lts |
| 237 | MARY_BASE/lib/modules/tr/tagger/tr_pos.fst |
| 238 | }}} |
| 239 | |
| 240 | They must be copied from the TranscriptionGUI folder to the expected place on the file system. |
| 241 | |
| 242 | |
| 243 | Now, it should be possible to start the mary server, and place a query via the HTTP interface, for input format TEXT, locale tr, and output formats up to TARGETFEATURES. A suitable test request can be placed from http://localhost:59125/documentation.html. It is a good idea to check whether the output for TOKENS, PARTSOFSPEECH, PHONEMES, INTONATION and ALLOPHONES looks roughly as expected. |
| 244 | |
| 245 | In order to continue with the next step, you will need to have a mary server with this config file running, so that the FeatureMaker can compute feature vectors for computing diphone coverage. |