Date   
Re: Thinking of trying to use MakeMSI to create the espeak-ng installer

Simon Eigeldinger
 

Hi Reece,

OK.
Is that components list built automatically?
If that one makes a lot of work i would just remove it.
The install size doesn't increase all that much when we install all languages.
What do you think?


For SAPI voices we could do it like the old inno setup installer that jonathan duddington has created.
Having a text box where you enter the voices and variants to get them enabled as sapi voices.

Greetings,
Simon


Am 16.11.2019 um 00:21 schrieb Reece H. Dunn:

Hi Simon,
I would rather make use of something like https://wixtoolset.org/documentation/manual/v3/msbuild/task_reference/heatdirectory.html to generate the installation for files in a given directory.
Currently, the installer allows you to specify which languages to install and it will only install the files needed for those languages. I would need to check if that wix task supports doing that.
Kind regards,
Reece

Re: Thinking of trying to use MakeMSI to create the espeak-ng installer

Reece H. Dunn
 

Hi Simon,

I would rather make use of something like https://wixtoolset.org/documentation/manual/v3/msbuild/task_reference/heatdirectory.html to generate the installation for files in a given directory.

Currently, the installer allows you to specify which languages to install and it will only install the files needed for those languages. I would need to check if that wix task supports doing that.

Kind regards,
Reece

[espeak-ng:master] reported: Build fails on MacOS Catalina #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Comment on Issue #674 Build fails on MacOS Catalina
By rhdunn:

That's strange. It should work on 64-bit.

The error messages relate to compiling the phsource/phonemes file, but the line numbers look wrong. See CompilePhonemeFiles in src/libespeak-ng/compiledata.c.

"Expected a number" is from https://github.com/espeak-ng/espeak-ng/blob/master/src/libespeak-ng/compiledata.c#L819.

"Expected ')'" is from https://github.com/espeak-ng/espeak-ng/blob/master/src/libespeak-ng/compiledata.c#L877.

The "The phoneme feature is not recognised" messages come from the ENS_UNKNOWN_PHONEME_FEATURE error code. It is coming from a call to the phoneme_add_feature function in phoneme.c at https://github.com/espeak-ng/espeak-ng/blob/master/src/libespeak-ng/compiledata.c#L2024.

Looking at that code, we know several things: 1. the values passed to phoneme_add_feature appear to be missing the first character (e.g. "engthmod" instead of "lengthmod"); 2. from the code, NextItem (https://github.com/espeak-ng/espeak-ng/blob/master/src/libespeak-ng/compiledata.c#L740) is returning a value less than 0 as that is what this if branch is checking; 3. this appears to be after processing whitespace.

I would start by printing values and control flow in NextItem to see what is happening there. NOTE: item_string is the string value of the token being read.


My intuition given the above information would be that the issue is at https://github.com/espeak-ng/espeak-ng/blob/master/src/libespeak-ng/compiledata.c#L760 in that it is checking for \n when identifying the end of a comment, so is likely incorrectly processing the file when using Mac (\r) line endings.

There are likely other cases like that, which would also explain why the line numbers are wrong in the output.

Re: Thinking of trying to use MakeMSI to create the espeak-ng installer

Simon Eigeldinger
 

forgot to add maybe the MakeMSI group could help us designing a nice installer.
What do we need?


Greetings,
Simon

Am 15.11.2019 um 23:55 schrieb Simon Eigeldinger:

Hi all,
I found Make MSI.
http://dennisbareis.com/makemsi.htm
which might be interesting for us.
Doesn't need a lot of GUID generation.
I guess mainly just one GUID for the installer.
If i have some time in the next weeks i might look into it.
If someone has more time earlier then that would be also no problem. *smile*
Greetings,
Simon

Thinking of trying to use MakeMSI to create the espeak-ng installer

Simon Eigeldinger
 

Hi all,

I found Make MSI.
http://dennisbareis.com/makemsi.htm
which might be interesting for us.
Doesn't need a lot of GUID generation.
I guess mainly just one GUID for the installer.
If i have some time in the next weeks i might look into it.
If someone has more time earlier then that would be also no problem. *smile*

Greetings,
Simon

[espeak-ng:master] new issue: Build fails on MacOS Catalina #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Issue Created by BenTalagan:
#674 Build fails on MacOS Catalina

Trying to build espeak-ng on Catalina today (on two different machines) resulted in a fail during the compilation of phoneme data. The tool seems to perform strange operations :

...
  CC       src/libespeak-ng/la-event.lo
  CC       src/libespeak-ng/la-fifo.lo
  CCLD     src/libespeak-ng.la
  CCLD     src/espeak-ng
ESPEAK_DATA_PATH=/Users/ben/poub/espeak-ng src/espeak-ng --compile-intonations && \
		ESPEAK_DATA_PATH=/Users/ben/poub/espeak-ng src/espeak-ng --compile-phonemes && \
		touch phsource/phonemes.stamp
Compiled 26 intonation tunes: 0 errors.
Unknown phoneme table: 'en'
Can't read dictionary file: '/Users/ben/poub/espeak-ng/espeak-ng-data/en_dict'
Compiling phoneme data: /Users/ben/poub/espeak-ng/espeak-ng-data/../phsource/phonemes
phonemes(129): Expected a number
phonemes(129): Expected ')'
phonemes(129): The phoneme feature is not recognised: '1='.
phonemes(129): The phoneme feature is not recognised: '2'.
phonemes(129): The phoneme feature is not recognised: '2700'.
phonemes(129): The phoneme feature is not recognised: '400'.
phonemes(129): The phoneme feature is not recognised: '600'.
phonemes(129): The phoneme feature is not recognised: '300'.
phonemes(129): The phoneme feature is not recognised: '80'.
phonemes(131): The phoneme feature is not recognised: '1'.
phonemes(132): The phoneme feature is not recognised: '_'.
phonemes(132): The phoneme feature is not recognised: 'engthmod'.
phonemes(133): The phoneme feature is not recognised: '3'.
phonemes(137): Expected AND, OR, THEN
phonemes(137): Expected a condition, not 'phonemetable'
phonemes(137): Unexpected keyword 'phonemetable'
phonemes(137): Expected AND, OR, THEN
phonemes(138): Expected a condition, not 'base1'
phonemes(138): Unexpected keyword 'base1'
phonemes(138): Expected AND, OR, THEN
phonemes(140): Expected a condition, not 'ph_icelandic'
phonemes(140): Unexpected keyword 'ph_icelandic'
phonemes(140): Expected AND, OR, THEN
phonemes(140): Expected a condition, not 'ja'
phonemes(140): Unexpected keyword 'ja'
phonemes(141): Expected AND, OR, THEN
... etc ... etc ...

Strangely, I get similar bad results on older commits (for which I'm sure it was working before under MacOS Mojave). Does anyone have a clue on how to investigate this? Could it be related to the fact that 64-bits applications and compilation have been ditched from MacOS (is espeak-ng 64-bits bullet proof) ?

Ben

Re: new espeak ng builds

mattias
 

reece if i will try the sapi how to enable?

i have forgot it

On 2019-11-05 19:44, Reece H. Dunn wrote:
On Tue, Nov 5, 2019 at 05:36 PM, Simon Eigeldinger wrote:
Hi all,

I have compiled new builds yesterday.
now they also work on all systems.
Great. Thanks for doing this.

had to get release mode working.
by default visual studio uses debug mode which doesn't let you run the
binaries on a non developer pc.
Seems we don't get voice variants in the msi installer.
We also seem to lack documentation.
I ask myself if it is a good idea to continue with msi installers when
the creation and keeping them up to date of such ones is pretty complex?
What do you think?
MSI is the standard Windows installer format (like deb files on Debian/Ubuntu). While they are a pain to manage, they provide features such as the ability to upgrade, repair, and uninstall. This includes updating the registry and ensuring that dependencies within the installer are installed based on the features the user selects. This is done by keeping the GUIDs the same for each item.

I would like to update the MSI to better reflect the current state (e.g. new voices) before release. I haven't had time to do this yet, but patches are welcome.

Longer term, we can look at better ways to manage the process. Something like having the GUIDs in the language/voice file with the ability to generate the voice data part of the installer XML source. This could then be made so that the tests can check that GUIDs are present and valid, so the regression tests will fail if any are missing/wrong.

Regarding SAPI support: There is an experimental version commented out for English. It has a few bugs and is not complete.

Kind regards,
Reece

Greetings,
Simon


--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

Re: new espeak ng builds

Simon Eigeldinger
 

yes i did.
https://github.com/git-for-windows/git/

Here's the building howto for espeak ng:
https://github.com/espeak-ng/espeak-ng/blob/master/docs/building.md


Here's my script how i build it.
it builds msi files for 32 and 64 bit.
You might need to replace some directory names.


--- Script begin ---

cd\
c:
cd\
cd src
git clone git://github.com/espeak-ng/espeak-ng.git
cd espeak-ng
cd src
git clone git://github.com/espeak-ng/pcaudiolib.git
cd windows
msbuild /p:Configuration=Release /p:PlatformTarget=x86 /p:Platform=x86 espeak-ng.sln
msbuild /p:Configuration=Release /p:PlatformTarget=x64 /p:Platform=x64 espeak-ng.sln


--- Script end ---


Might also be interesting for the howto.
Though i might rewrite the windows part at some time.


Greetings,
Simon

Am 05.11.2019 um 20:05 schrieb mattias:

Simon do you use git for windows to clone the git repo?
Skickades från E-post <https://go.microsoft.com/fwlink/?LinkId=550986> för
Windows 10
*Från: *Simon Eigeldinger <mailto:simon.eigeldinger@...>
*Skickat: *den 5 november 2019 19:52
*Till: *espeak-ng@groups.io <mailto:espeak-ng@groups.io>
*Ämne: *Re: [espeak-ng] new espeak ng builds
Hi,
Yes there is.
You can download visual studio community edition.
This is free.
I am using that over here as well.
Greetings,
Simon
Am 05.11.2019 um 19:49 schrieb mattias:

> Reece yes i know that the sapi5 are experimental

>

> But if i want to try i have to compile espeak myself?

>

> If so fine, but there is no free version of Visual studio?

>

> Skickades från E-post <https://go.microsoft.com/fwlink/?LinkId=550986> för

> Windows 10

>

> *Från: *Reece H. Dunn <mailto:msclrhd@...>

> *Skickat: *den 5 november 2019 19:44

> *Till: *espeak-ng@groups.io <mailto:espeak-ng@groups.io>

> *Ämne: *Re: [espeak-ng] new espeak ng builds

>

> On Tue, Nov 5, 2019 at 05:36 PM, Simon Eigeldinger wrote:

>

> Hi all,

>

> I have compiled new builds yesterday.

> now they also work on all systems.

>

> Great. Thanks for doing this.

>

> had to get release mode working.

> by default visual studio uses debug mode which doesn't let you run the

> binaries on a non developer pc.

> Seems we don't get voice variants in the msi installer.

> We also seem to lack documentation.

> I ask myself if it is a good idea to continue with msi installers when

> the creation and keeping them up to date of such ones is pretty complex?

> What do you think?

>

> MSI is the standard Windows installer format (like deb files on Debian/Ubuntu).

> While they are a pain to manage, they provide features such as the ability to

> upgrade, repair, and uninstall. This includes updating the registry and ensuring

> that dependencies within the installer are installed based on the features the

> user selects. This is done by keeping the GUIDs the same for each item.

>

> I would like to update the MSI to better reflect the current state (e.g. new

> voices) before release. I haven't had time to do this yet, but patches are
welcome.

>

> Longer term, we can look at better ways to manage the process. Something like

> having the GUIDs in the language/voice file with the ability to generate the

> voice data part of the installer XML source. This could then be made so that the

> tests can check that GUIDs are present and valid, so the regression tests will

> fail if any are missing/wrong.

>

> Regarding SAPI support: There is an experimental version commented out for

> English. It has a few bugs and is not complete.

>

> Kind regards,

> Reece

>

> Greetings,

> Simon

>

>

> --

> Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.

> https://www.avast.com/antivirus

>

>

>
--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

Re: new espeak ng builds

Simon Eigeldinger
 

Hi Reece,

No problem.
We are a small community and whoever is able to help with something (big or small) is a big help factor.

I have also tried to get my hands dirty with the wix xml format but never got my head around it.
So i dropped that experiment. *smile*
Way to many guids, gids and whatever other ids they have.
After that i played with NSIS and Inno Setup and got way better results. *lol*
Or i just went with zip files for simplicity.

Greetings,
Simon





Am 05.11.2019 um 19:44 schrieb Reece H. Dunn:

On Tue, Nov 5, 2019 at 05:36 PM, Simon Eigeldinger wrote:


Hi all,

I have compiled new builds yesterday.
now they also work on all systems.
Great. Thanks for doing this.


had to get release mode working.
by default visual studio uses debug mode which doesn't let you run the
binaries on a non developer pc.
Seems we don't get voice variants in the msi installer.
We also seem to lack documentation.
I ask myself if it is a good idea to continue with msi installers when
the creation and keeping them up to date of such ones is pretty complex?
What do you think?
MSI is the standard Windows installer format (like deb files on Debian/Ubuntu). While they are a pain to manage, they provide features such as the ability to upgrade, repair, and uninstall. This includes updating the registry and ensuring that dependencies within the installer are installed based on the features the user selects. This is done by keeping the GUIDs the same for each item.
I would like to update the MSI to better reflect the current state (e.g. new voices) before release. I haven't had time to do this yet, but patches are welcome.
Longer term, we can look at better ways to manage the process. Something like having the GUIDs in the language/voice file with the ability to generate the voice data part of the installer XML source. This could then be made so that the tests can check that GUIDs are present and valid, so the regression tests will fail if any are missing/wrong.
Regarding SAPI support: There is an experimental version commented out for English. It has a few bugs and is not complete.
Kind regards,
Reece


Greetings,
Simon


--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

Re: new espeak ng builds

mattias
 

Simon do you use git for windows to clone the git repo?

 

Skickades från E-post för Windows 10

 

Från: Simon Eigeldinger
Skickat: den 5 november 2019 19:52
Till: espeak-ng@groups.io
Ämne: Re: [espeak-ng] new espeak ng builds

 

Hi,

 

Yes there is.

You can download visual studio community edition.

This is free.

I am using that over here as well.

 

Greetings,

Simon

 

 

Am 05.11.2019 um 19:49 schrieb mattias:

> Reece yes i know that the sapi5 are experimental

>

> But if i want to try i have to compile espeak myself?

>

> If so fine, but there is no free version of Visual studio?

>

> Skickades från E-post <https://go.microsoft.com/fwlink/?LinkId=550986> för

> Windows 10

>

> *Från: *Reece H. Dunn <mailto:msclrhd@...>

> *Skickat: *den 5 november 2019 19:44

> *Till: *espeak-ng@groups.io <mailto:espeak-ng@groups.io>

> *Ämne: *Re: [espeak-ng] new espeak ng builds

>

> On Tue, Nov 5, 2019 at 05:36 PM, Simon Eigeldinger wrote:

>

>      Hi all,

>

>      I have compiled new builds yesterday.

>      now they also work on all systems.

>

> Great. Thanks for doing this.

>

>      had to get release mode working.

>      by default visual studio uses debug mode which doesn't let you run the

>      binaries on a non developer pc.

>      Seems we don't get voice variants in the msi installer.

>      We also seem to lack documentation.

>      I ask myself if it is a good idea to continue with msi installers when

>      the creation and keeping them up to date of such ones is pretty complex?

>      What do you think?

>

> MSI is the standard Windows installer format (like deb files on Debian/Ubuntu).

> While they are a pain to manage, they provide features such as the ability to

> upgrade, repair, and uninstall. This includes updating the registry and ensuring

> that dependencies within the installer are installed based on the features the

> user selects. This is done by keeping the GUIDs the same for each item.

>

> I would like to update the MSI to better reflect the current state (e.g. new

> voices) before release. I haven't had time to do this yet, but patches are welcome.

>

> Longer term, we can look at better ways to manage the process. Something like

> having the GUIDs in the language/voice file with the ability to generate the

> voice data part of the installer XML source. This could then be made so that the

> tests can check that GUIDs are present and valid, so the regression tests will

> fail if any are missing/wrong.

>

> Regarding SAPI support: There is an experimental version commented out for

> English. It has a few bugs and is not complete.

>

> Kind regards,

> Reece

>

>      Greetings,

>      Simon

>

>

>      --

>      Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.

>      https://www.avast.com/antivirus

>

>

>

 

--

Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.

https://www.avast.com/antivirus

 

 

 

 

Re: new espeak ng builds

Simon Eigeldinger
 

Hi,

Yes there is.
You can download visual studio community edition.
This is free.
I am using that over here as well.

Greetings,
Simon


Am 05.11.2019 um 19:49 schrieb mattias:

Reece yes i know that the sapi5 are experimental
But if i want to try i have to compile espeak myself?
If so fine, but there is no free version of Visual studio?
Skickades från E-post <https://go.microsoft.com/fwlink/?LinkId=550986> för
Windows 10
*Från: *Reece H. Dunn <mailto:msclrhd@...>
*Skickat: *den 5 november 2019 19:44
*Till: *espeak-ng@groups.io <mailto:espeak-ng@groups.io>
*Ämne: *Re: [espeak-ng] new espeak ng builds
On Tue, Nov 5, 2019 at 05:36 PM, Simon Eigeldinger wrote:
Hi all,
I have compiled new builds yesterday.
now they also work on all systems.
Great. Thanks for doing this.
had to get release mode working.
by default visual studio uses debug mode which doesn't let you run the
binaries on a non developer pc.
Seems we don't get voice variants in the msi installer.
We also seem to lack documentation.
I ask myself if it is a good idea to continue with msi installers when
the creation and keeping them up to date of such ones is pretty complex?
What do you think?
MSI is the standard Windows installer format (like deb files on Debian/Ubuntu).
While they are a pain to manage, they provide features such as the ability to
upgrade, repair, and uninstall. This includes updating the registry and ensuring
that dependencies within the installer are installed based on the features the
user selects. This is done by keeping the GUIDs the same for each item.
I would like to update the MSI to better reflect the current state (e.g. new
voices) before release. I haven't had time to do this yet, but patches are welcome.
Longer term, we can look at better ways to manage the process. Something like
having the GUIDs in the language/voice file with the ability to generate the
voice data part of the installer XML source. This could then be made so that the
tests can check that GUIDs are present and valid, so the regression tests will
fail if any are missing/wrong.
Regarding SAPI support: There is an experimental version commented out for
English. It has a few bugs and is not complete.
Kind regards,
Reece
Greetings,
Simon
--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

Re: new espeak ng builds

mattias
 

Reece yes i know that the sapi5 are experimental

But if i want to try i have to compile espeak myself?

If so fine, but there is no free version of Visual studio?

 

Skickades från E-post för Windows 10

 

Från: Reece H. Dunn
Skickat: den 5 november 2019 19:44
Till: espeak-ng@groups.io
Ämne: Re: [espeak-ng] new espeak ng builds

 

On Tue, Nov 5, 2019 at 05:36 PM, Simon Eigeldinger wrote:

Hi all,

I have compiled new builds yesterday.
now they also work on all systems.

Great. Thanks for doing this.

had to get release mode working.
by default visual studio uses debug mode which doesn't let you run the
binaries on a non developer pc.
Seems we don't get voice variants in the msi installer.
We also seem to lack documentation.
I ask myself if it is a good idea to continue with msi installers when
the creation and keeping them up to date of such ones is pretty complex?
What do you think?

MSI is the standard Windows installer format (like deb files on Debian/Ubuntu). While they are a pain to manage, they provide features such as the ability to upgrade, repair, and uninstall. This includes updating the registry and ensuring that dependencies within the installer are installed based on the features the user selects. This is done by keeping the GUIDs the same for each item.

I would like to update the MSI to better reflect the current state (e.g. new voices) before release. I haven't had time to do this yet, but patches are welcome.

Longer term, we can look at better ways to manage the process. Something like having the GUIDs in the language/voice file with the ability to generate the voice data part of the installer XML source. This could then be made so that the tests can check that GUIDs are present and valid, so the regression tests will fail if any are missing/wrong.

Regarding SAPI support: There is an experimental version commented out for English. It has a few bugs and is not complete.

Kind regards,
Reece

Greetings,
Simon


--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

 

Re: new espeak ng builds

Reece H. Dunn
 

On Tue, Nov 5, 2019 at 05:36 PM, Simon Eigeldinger wrote:
Hi all,

I have compiled new builds yesterday.
now they also work on all systems.
Great. Thanks for doing this.

had to get release mode working.
by default visual studio uses debug mode which doesn't let you run the
binaries on a non developer pc.
Seems we don't get voice variants in the msi installer.
We also seem to lack documentation.
I ask myself if it is a good idea to continue with msi installers when
the creation and keeping them up to date of such ones is pretty complex?
What do you think?
MSI is the standard Windows installer format (like deb files on Debian/Ubuntu). While they are a pain to manage, they provide features such as the ability to upgrade, repair, and uninstall. This includes updating the registry and ensuring that dependencies within the installer are installed based on the features the user selects. This is done by keeping the GUIDs the same for each item.

I would like to update the MSI to better reflect the current state (e.g. new voices) before release. I haven't had time to do this yet, but patches are welcome.

Longer term, we can look at better ways to manage the process. Something like having the GUIDs in the language/voice file with the ability to generate the voice data part of the installer XML source. This could then be made so that the tests can check that GUIDs are present and valid, so the regression tests will fail if any are missing/wrong.

Regarding SAPI support: There is an experimental version commented out for English. It has a few bugs and is not complete.

Kind regards,
Reece

Greetings,
Simon


--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

Re: new espeak ng builds

Simon Eigeldinger
 

No.


Am 05.11.2019 um 18:47 schrieb mattias:

sapi?
On 2019-11-05 18:36, Simon Eigeldinger wrote:
Hi all,

I have compiled new builds yesterday.
now they also work on all systems.
had to get release mode working.
by default visual studio uses debug mode which doesn't let you run the
binaries on a non developer pc.
Seems we don't get voice variants in the msi installer.
We also seem to lack documentation.
I ask myself if it is a good idea to continue with msi installers when
the creation and keeping them up to date of such ones is pretty complex?
What do you think?

Greetings,
Simon


--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus



Re: new espeak ng builds

mattias
 

sapi?

On 2019-11-05 18:36, Simon Eigeldinger wrote:
Hi all,

I have compiled new builds yesterday.
now they also work on all systems.
had to get release mode working.
by default visual studio uses debug mode which doesn't let you run the
binaries on a non developer pc.
Seems we don't get voice variants in the msi installer.
We also seem to lack documentation.
I ask myself if it is a good idea to continue with msi installers when
the creation and keeping them up to date of such ones is pretty complex?
What do you think?

Greetings,
Simon


--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


new espeak ng builds

Simon Eigeldinger
 

Hi all,

I have compiled new builds yesterday.
now they also work on all systems.
had to get release mode working.
by default visual studio uses debug mode which doesn't let you run the
binaries on a non developer pc.
Seems we don't get voice variants in the msi installer.
We also seem to lack documentation.
I ask myself if it is a good idea to continue with msi installers when
the creation and keeping them up to date of such ones is pretty complex?
What do you think?

Greetings,
Simon


--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

Updates to Github #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

2 New Commits:

[espeak-ng:master] By Karl Eick <hozosch@...>:
a63e8487b188: Improve Y: phoneme

Modified: phsource/ph_german


[espeak-ng:master] By Valdis Vitolins <valdis.vitolins@...>:
fe7aa8742268: Merge pull request #673

Modified: phsource/ph_german


[espeak-ng/espeak-ng] Pull request closed by valdisvi:

#673 Improve Y: phoneme

Pull Request Opened #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng/espeak-ng] Pull request opened by hozosch:

#673 Improve Y: phoneme

[espeak-ng:master] reported: Adding Tagalog /Filipino language to Espeak #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

Updates to Github #github

espeak-ng@groups.io Integration <espeak-ng@...>
 

[espeak-ng:master] New Comment on Issue #598 --ipa option values reversed vs. original espeak
By dmgolubovsky:

Sorry for long silence, was away working on other projects. I was about to submit a patch, but did some research. Looks like the desired effect can be made with

espeak-ng --ipa --sep=_ -q "hello" h_ə_l_ˈəʊ

which makes this bug report irrelevant - so I am closing it now. Thanks


[espeak-ng:master] Issue #598 --ipa option values reversed vs. original espeak closed by dmgolubovsky.