After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 342325 - Gnopernicus and Festival TTS working in Spanish regression in bug #141516
Gnopernicus and Festival TTS working in Spanish regression in bug #141516
Status: RESOLVED DUPLICATE of bug 141516
Product: gnome-speech
Classification: Deprecated
Component: drivers
0.4.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Speech Maintainer(s)
GNOME Speech Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2006-05-19 07:40 UTC by Javier
Modified: 2006-07-01 16:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Javier 2006-05-19 07:40:36 UTC 
+++ This bug was initially created as a clone of Bug #141516 +++

When the words are stress them are not pronounced,they are spelling no good.
For example, the word 'Rat
Comment 1 Javier 2006-05-19 07:47:57 UTC 
Another restrictive change, may consits on applying the iso-8859-15 only to speaker's voices that needs it, but We would need to know these.
Comment 2 Willie Walker 2006-06-13 16:30:13 UTC 
The UTF-8 encoding is set by hardcoding it in festivalsynthesisdriver.c at lines 485 and 489:

        d->channel_pipe = g_io_channel_unix_new(d->pipe);
	g_io_channel_set_encoding (d->channel_pipe, "UTF-8", NULL);
        g_io_add_watch (d->channel_pipe, G_IO_IN , festival_response_pipe, d);
	
	d->channel_sock = g_io_channel_unix_new(d->sock);
	g_io_channel_set_encoding (d->channel_sock, "UTF-8", NULL);
        g_io_add_watch (d->channel_sock, G_IO_IN, festival_response_sock, d);

I wonder if there might be a way to pick up the character set encoding from the user's environment rather than hardcoding it?
Comment 3 Willie Walker 2006-07-01 16:17:56 UTC 

*** This bug has been marked as a duplicate of 141516 ***