From Navit's Wiki

Using the web-based tool

We are currently using Launchpad : https://translations.launchpad.net/navit/trunk If you want to update a translation, or add a new one, please try using launchpad. Translations are usually updated once a week.

Configuring Speech in your language

To test results and for normal operation you should configure a speech program in navit.xml to listen the sentences, for example in spanish you could substitute the default speech definition:

<speech type="cmdline" data="echo 'Fix the speech tag in navit.xml to let navit say:' '%s'" />

with an appropiate one, that uses festival:

<speech type="cmdline" data="echo '%s' | festival --tts --language spanish" />

Here's how to use espeak:

<speech type="cmdline" data="espeak -s 150 -v german '%s' &amp;" />

where -s is the "Speed in words per minute" (150 seems to be quite good for german) and -v specifies the language to use. Please refer to espeak to see which languages you can use on your system and which other command-line-options are useful. The & is replaced by & when the file is parsed and makes the call to espeak asynchronus. This is for not to freeze the GUI while espeak is speaking to you.

If you are running multiple programs with audio output, it is possible that /dev/dsp is locked (the default DSP for both festival and espeak). Use the following command to re-route the sound to ALSA. (To be exact, the Wave channel on the default sound card).

<speech type="cmdline" data="espeak -s 150 -v english --stdout '%s' | aplay > /dev/null &amp;" />

Note on the Dutch language

I had good success with the dutch extensions for festival. nextens

Especially the spoken dutch streetnames are much more clear this way.

It takes a bit of work to compile it, but i think it is worth the effort.