eSpeak - PPC architecture

[Jonathan Duddington]

In article <20070121043156.GA14734 at themuso.com>,
   Luke Yelavich <themuso at themuso.com> wrote:
> > 
> > > 2.  What happens if you send the speech output to a WAV file?
> > 
> > Again, nothing useful.  I think eSpeak is actually creating an
> > invalid wav file.

> I get the same behavior.

What architecture and OS is this on?
Is the byte order different from i386?
Have you ever had eSpeak working on it, or do you know anyone who has?

> Jonathan, I have come to the conclusion that the phoneme data as well
> as dictionaries need to be rebuilt, to suit the architecture the
> package is being built on. I notice that the espeakedit package has
> the routines to compile the phoneme data, but unfortunately one has
> to have a GUI running to use the --compile flag of the binary.

Are you sure?
What happens if you run  espeakedit --compile  or  espeakedit --help ?
Is there an error message?
I've run my system (MEPIS 6, which is a KDE/Ubuntu distro) in
"failsafe" mode, which I think means no GUI, and I can do
  espeakedit --compile
OK.

> Is it possible to separate out the phoneme compile routines to a
> separate binary, independant of any GUI libraries? If so, would you
> mind sending them to me, so I can use them to ensure all
> architectures ship with the correct voice and phoneme data?

Are you able to build the espeakedit program and compile the
espeak-data with it?
Does eSpeak then speak OK?

The espeakedit program uses wxWidgets data types.  It will take a bit
of work to convert the phoneme compile routines so that they don't use
them.