[prev in list] [next in list] [prev in thread] [next in thread] 

List:       irssi-users
Subject:    Small bug in text-to-speech handling
From:       "Dr. Rich Artym" <rartym () galacta ! demon ! co ! uk>
Date:       1999-05-17 6:42:40
[Download RAW message or body]

[This is going to both lists because it's both a user problem report
 and an analysis/problem-fix suggestion for the developers.]

I've found a bug in the text-to-speech handling.  The following
was seen on the stderr output of the Festival server:-

  SIOD ERROR: unbound variable 
  open
  SIOD ERROR: unbound variable 
  v3NetDNS
  SIOD ERROR: unbound variable 
  nontrivial
  SIOD ERROR: unbound variable 
  cosmio.h
  SIOD ERROR: unbound variable 
  long

Looking through the irssi logfile, the tokens 'Les', 'open', 'v3NetDNS'
and so on appear in the following lines:

  [23:17] <Duncan3> ah, the wonders of "open source" linux...
  [00:02] <ElNounch> Next update tomorrow. Tonight was : "v3NetDNS's resolv
  [00:05] <Duncan3> it's definately going to be "nontrivial" in win32
  [00:16] <NCruiser> working on cosmnet.c, remove #include "cosmio.h" at
  [00:48] <Ferd^> Ooh.. But use "long long" on the 64bit machines anyhow..


This is somewhere halfway between being a bug in irssi and a bug in
Festival.  The pragmatic thing to do at this stage is to either filter
out double quotes altogether or backquote them, since they appear to
make the word following each one trigger a SIOD variable lookup.  This
is not at all surprising, since irssi/plugins/speech/speech-events.c
just passes the text across to Festival using:-

  str = g_strdup_printf("(SayText \"%s\")\n", text);

Consequently, all text following a double quote is seen by SIOD as a
second argument to SayText, which is bound (:-) to cause a hiccup.

I haven't tested what Festival would do with quoted double quotes
within its text string, but I would expect it to be better than what
it does at the moment --- it'll probably ignore them, but if it were
clever then it could treat the two-character sequence \" as a real
double quote and change the intonation accordingly.

If it does something horribly nasty with quoted double quotes, then I
suppose we could turn double quotes into single quotes or backquotes
instead.

Cheers,

Rich.

[prev in list] [next in list] [prev in thread] [next in thread]