Date   

Updates to Github #github

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

1 New Commit:

[espeak-ng:master] By Samuel Thibault <samuel.thibault@...>:
171e8a4e0958: Fix testsuite with /bin/sh being bash

With bash, echo "a\nb" will not interpret \n, while with dash, echo will
interpret \n. bash's echo would need -e, but dash does not know that
option and just prints it.

We can however just put \n litteraly in the script, both bash and dash
will understand it.

Modified: tests/language-pronunciation.test
Modified: tests/translate.test


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

#698 Fix testsuite with /bin/sh being bash

With bash, echo "a\nb" will not interpret \n, while with dash, echo will interpret \n. bash's echo would need -e, but dash does not know that option and just prints it.

We can however just put \n litteraly in the script, both bash and dash will understand it.


[espeak-ng:master] New Comment on Pull Request #698 Fix testsuite with /bin/sh being bash
By rhdunn:

Merged, thanks.


Pull Request Opened #github

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

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

#698 Fix testsuite with /bin/sh being bash

With bash, echo "a\nb" will not interpret \n, while with dash, echo will interpret \n. bash's echo would need -e, but dash does not know that option and just prints it.

We can however just put \n litteraly in the script, both bash and dash will understand it.


[espeak-ng:master] new issue: Espeak ENG speech-dispatcher driver produces electric noise sounds while using it with Pulseaudio sound server #github

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

[espeak-ng:master] New Issue Created by JanuszChmiel:
#697 Espeak ENG speech-dispatcher driver produces electric noise sounds while using it with Pulseaudio sound server

Dear specialists, Does somebodyof you know how to setup Pulseaudio sound server and how to setup Speech-dispatcher Espeak eng driver configuration file, so it will finally stop to produce electric noise while speaking? Those noises are louder when user have swap file enabled. I have got so far while I have thought that The most sad think is, that if Espeak app is being used to produce speech output, no noise present. But when Speech-dispatcher is being used, there are issues.

Thank you very much for yours tips.


Updates to Github #github

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

2 New Commits:

[espeak-ng:master] By Ejaz Shah <eashah67@...>:
c17df16da475: Improvements for Urdu

Modified: dictsource/ur_list
Modified: dictsource/ur_rules


[espeak-ng:master] By Valdis Vitolins <valdis.vitolins@...>:
9ebfd55871dd: Update changelog

Modified: CHANGELOG.md


1 New Commit:

[espeak-ng:master] By Valdis Vitolins <valdis.vitolins@...>:
b3bab5df052e: Update changelog

Modified: CHANGELOG.md


1 New Commit:

[espeak-ng:master] By Valdis Vitolins <valdis.vitolins@...>:
baa8c55a016c: Update changelog

Modified: CHANGELOG.md


1 New Commit:

[espeak-ng:master] By Valdis Vitolins <valdis.vitolins@...>:
ee92524af8ba: Update changelog

Modified: CHANGELOG.md


Re: Improvements for Urdu

Valdis Vitolins
 

Thanks!

Added into project with commit:
https://github.com/espeak-ng/espeak-ng/commit/c17df16da475d477797746c44
0cd91a104b60e24

Valdis

Some more changes for Urdu in the attached dictionary files. I hope 
these can be included in eSpeak-ng.
>
Thanks!




[espeak-ng:master] new issue: What is expected value for -d option? Document -d expects device index not device name #github

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

[espeak-ng:master] New Issue Created by guest271314:
#696 What is expected value for -d option? Document -d expects device index not device name

List devices

$ pactl list short sources
0	alsa_output.pci-0000_00_1b.0.analog-stereo.monitor	module-alsa-card.c	s16le 2ch 44100Hz	RUNNING
1	alsa_input.pci-0000_00_1b.0.analog-stereo	module-alsa-card.c	s16le 2ch 44100Hz	RUNNING

The suggested value at https://github.com/espeak-ng/espeak-ng/issues/99#issuecomment-272613882

On some systems, the default audio device does not work. Because of this, in espeak-ng you can use the -d DEVICE_NAME option, e.g. espeak-ng -d sysdefault.

outputs an error at *nix

$ espeak-ng -d sysdefault 'test'
ALSA lib pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave
error: No such file or directory

Using device name output an error

$ espeak-ng -d alsa_output.pci-0000_00_1b.0.analog-stereo.monitor 'test'
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM alsa_output.pci-0000_00_1b.0.analog-stereo.monitor
error: No such file or directory

Using index does not output error

$ espeak-ng -d 0 'test test test test test test test test test test'

The value expected following -d option is not clearly detailed. Kindly update the man pages, -h output, and relevant documentation to reflect the value expected for -d device option.

Related https://github.com/espeak-ng/espeak-ng/issues/554


Improvements for Urdu

Ejaz Shah
 

Some more changes for Urdu in the attached dictionary files. I hope these can be included in eSpeak-ng.


Thanks!


Updates to Github #github

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

2 New Commits:

[espeak-ng:master] By Karl Eick <hozosch@...>:
ff941a7bfa6a: add iven 4 variant

Added: espeak-ng-data/voices/!v/iven4


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

Added: espeak-ng-data/voices/!v/iven4


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

#695 add iven 4 variant

This is a smoother version of iven. I personally like it, and I also told about this variant in the german NVDA mailing list. I got one reply from someone being curious about it, so I'll include it in espeak NG. If people don't want to use it, they don't have to. I'm saying all this because I know that I should be careful with changes as it might result in angry users.


Pull Request Opened #github

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

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

#695 add iven 4 variant

This is a smoother version of iven. I personally like it, and I also told about this variant in the german NVDA mailing list. I got one reply from someone being curious about it, so I'll include it in espeak NG. If people don't want to use it, they don't have to. I'm saying all this because I know that I should be careful with changes as it might result in angry users.


Updates to Github #github

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

3 New Commits:

[espeak-ng:master] By John Bowler <jbowler@...>:
bfef0120683a: Fixed UTF8 BOM and consequent damage to !v files

The six modified files all had spurious characters introduced apparently
as a result of files with the UTF8 BOM marker, U-FFFE, which is
conventionally used at the start of text files to indicate a UTF-8 file
and is invisible under normal circumstances (e.g. the file is opened as
a text file).

None of these files are recognized by espeak-ng on Linux systems because
the 'language variant' line is seen by espeak-ng as starting with a new
character.

'gustave' is an uncorrupted file, it correctly starts with the BOM in
UTF-8 (three bytes), however even though it is correct espeak-ng does
not read it (this may be a separate bug!)

'marcelo' somehow got the BOM character replaced by a literal '?',
notice that 'git diff' on these changes will, indeed, show the removed
character in 'gustave' as a literal '?'. Notice also that the character
in question, the BOM, is actually the Unicode 'zero width no-break
space', so it is pretty invisible.

The remaining files seem to have suffered major corruption possible as a
result of dostounix style convertions. The line endings, normally <lf>
on Unix or <cr><lf> on Windows, had been converted to <cr><lf><lf> and
the BOM had been replaced by a <tab> character.

Signed-off-by: John Bowler <jbowler@...>

Modified: espeak-ng-data/voices/!v/Andy
Modified: espeak-ng-data/voices/!v/AnxiousAndy
Modified: espeak-ng-data/voices/!v/Lee
Modified: espeak-ng-data/voices/!v/gustave
Modified: espeak-ng-data/voices/!v/linda
Modified: espeak-ng-data/voices/!v/marcelo


[espeak-ng:master] By Valdis Vitolins <valdis.vitolins@...>:
53f65b51eb46: Add a test to ensure source files do not have Byte Order Mark

Added: tests/bom.test
Modified: .gitignore
Modified: Makefile.am


[espeak-ng:master] By Valdis Vitolins <valdis.vitolins@...>:
a99937f6c43e: Remove Byte Order Marks from source files

Modified: android/res/values-es-rUS/strings.xml
Modified: dictsource/af_list
Modified: dictsource/af_rules
Modified: dictsource/an_list
Modified: dictsource/bn_list
Modified: dictsource/bn_rules
Modified: dictsource/bs_list
Modified: dictsource/bs_rules
Modified: dictsource/da_list
Modified: dictsource/da_rules
Modified: dictsource/de_list
Modified: dictsource/de_rules
Modified: dictsource/en_list
Modified: dictsource/es_list
Modified: dictsource/fr_list
Modified: dictsource/gn_list
Modified: dictsource/hr_list
Modified: dictsource/hr_rules
Modified: dictsource/ht_list
Modified: dictsource/it_list
Modified: dictsource/it_listx
Modified: dictsource/ja_list
Modified: dictsource/ja_rules
Modified: dictsource/kn_list
Modified: dictsource/lfn_rules
Modified: dictsource/ne_list
Modified: dictsource/nl_list
Modified: dictsource/pa_list
Modified: dictsource/pa_rules
Modified: dictsource/pt_list
Modified: dictsource/sr_list
Modified: dictsource/sr_rules
Modified: espeak-ng-data/voices/!v/sandro
Modified: phsource/ph_italian
Modified: src/windows/data.vcxproj
Modified: src/windows/data.vcxproj.filters
Modified: src/windows/espeak-ng.sln
Modified: src/windows/espeak-ng.vcxproj
Modified: src/windows/espeak-ng.vcxproj.filters
Modified: src/windows/installer/installer.wixproj
Modified: src/windows/libespeak-ng.vcxproj
Modified: src/windows/libespeak-ng.vcxproj.filters


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

#693 Fixed UTF8 BOM and consequent damage to !v files

The six modified files all had spurious characters introduced apparently as a result of files with the UTF8 BOM marker, U-FFFE, which is conventionally used at the start of text files to indicate a UTF-8 file and is invisible under normal circumstances (e.g. the file is opened as a text file).

None of these files are recognized by espeak-ng on Linux systems because the 'language variant' line is seen by espeak-ng as starting with a new character.

'gustave' is an uncorrupted file, it correctly starts with the BOM in UTF-8 (three bytes), however even though it is correct espeak-ng does not read it (this may be a separate bug!)

'marcelo' somehow got the BOM character replaced by a literal '?', notice that 'git diff' on these changes will, indeed, show the removed character in 'gustave' as a literal '?'. Notice also that the character in question, the BOM, is actually the Unicode 'zero width no-break space', so it is pretty invisible.

The remaining files seem to have suffered major corruption possible as a result of dostounix style convertions. The line endings, normally on Unix or on Windows, had been converted to and the BOM had been replaced by a character.

Signed-off-by: John Bowler jbowler@...


[espeak-ng:master] New Comment on Pull Request #693 Fixed UTF8 BOM and consequent damage to !v files
By valdisvi:

Thanks for contribution! Note that files you fixed were not only files with Byte order marks. I also added test for that and fixed other files.


Updates to Github #github

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

[espeak-ng:master] New Comment on Issue #694 Phone separator sometimes adds additional separators trailing the end of a word
By RhyanJohnson:

Single trailing separator: editions of the evening papers gives ɪ*d*ɪ*ʃ*ə*n*z ʌ*v*ð*ɪ* iː*v*n*ɪ*ŋ p*eɪ*p*ɚ*z


[espeak-ng:master] New Comment on Issue #694 Phone separator sometimes adds additional separators trailing the end of a word
By RhyanJohnson:

Single trailing separator (after 'of the'): editions of the evening papers gives ɪ*d*ɪ*ʃ*ə*n*z ʌ*v*ð*ɪ* iː*v*n*ɪ*ŋ p*eɪ*p*ɚ*z


[espeak-ng:master] New Comment on Issue #694 Phone separator sometimes adds additional separators trailing the end of a word
By RhyanJohnson:

Single trailing separator (on phonemic 'of the'): editions of the evening papers gives ɪ*d*ɪ*ʃ*ə*n*z ʌ*v*ð*ɪ* iː*v*n*ɪ*ŋ p*eɪ*p*ɚ*z


Updates to Github #github

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

[espeak-ng:master] New Comment on Issue #694 Phone separator sometimes adds additional separators trailing the end of a word
By RhyanJohnson:

Also around the conjunction 'which': He wanted to see her about a plan **which** he had in his head. gives h*iː w*ɑː*n*t*ᵻ*d t*ə s*iː h*ɜː*ɹ ɐ*b*aʊ*t ɐ p*l*æ*n** w*ɪ*tʃ h*iː h*ɐ*d ɪ*n h*ɪ*z h*ɛ*d


[espeak-ng:master] New Comment on Issue #694 Phone separator sometimes adds additional separators trailing the end of a word
By RhyanJohnson:

Also around the conjunction 'which': He wanted to see her about a plan which he had in his head. gives h*iː w*ɑː*n*t*ᵻ*d t*ə s*iː h*ɜː*ɹ ɐ*b*aʊ*t ɐ p*l*æ*n** w*ɪ*tʃ h*iː h*ɐ*d ɪ*n h*ɪ*z h*ɛ*d


[espeak-ng:master] new issue: Phone separator sometimes adds additional separators trailing the end of a word #github

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

[espeak-ng:master] New Issue Created by RhyanJohnson:
#694 Phone separator sometimes adds additional separators trailing the end of a word

See issue initially reported here: https://github.com/bootphon/phonemizer/issues/31

Note the two trailing '*' after the phonemic representation of 'lion'

$ echo "The lion and the tiger ran" | espeak-ng -x --ipa -q --sep=**
ð*ə l*aɪə*n** æ*n*d ð*ə t*aɪ*ɡ*ɚ ɹ*æ*n

Additional examples: the hello but the gives ð*ə h*ə*l*oʊ** b*ʌ*t ð*ə Here there and everywhere gives h*ɪɹ ð*ɛɹ** æ*n*d ɛ*v*ɹ*ɪ*w*ɛɹ He was hungry and tired. gives h*iː w*ʌ*z h*ʌ*ŋ*ɡ*ɹ*i** æ*n*d t*aɪɚ*d He was hungry but tired. gives h*iː w*ʌ*z h*ʌ*ŋ*ɡ*ɹ*i** b*ʌ*t t*aɪɚ*d The tiger or the lion gives ð*ə t*aɪ*ɡ*ɚ** ɔːɹ ð*ə l*aɪə*n The lion or the tiger gives ð*ə l*aɪə*n** ɔːɹ ð*ə t*aɪ*ɡ*ɚ

I noticed it around conjunctions like 'and', 'but, and 'or', but not always: Lions and tigers and bears, oh my! gives l*aɪə*n*z æ*n*d t*aɪ*ɡ*ɚ*z** æ*n*d b*ɛɹ*z oʊ m*aɪ Lions and tigers run together gives l*aɪə*n*z æ*n*d t*aɪ*ɡ*ɚ*z ɹ*ʌ*n t*ə*ɡ*ɛ*ð*ɚ


Updates to Github #github

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

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

#693 Fixed UTF8 BOM and consequent damage to !v files

The six modified files all had spurious characters introduced apparently as a result of files with the UTF8 BOM marker, U-FFFE, which is conventionally used at the start of text files to indicate a UTF-8 file and is invisible under normal circumstances (e.g. the file is opened as a text file).

None of these files are recognized by espeak-ng on Linux systems because the 'language variant' line is seen by espeak-ng as starting with a new character.

'gustave' is an uncorrupted file, it correctly starts with the BOM in UTF-8 (three bytes), however even though it is correct espeak-ng does not read it (this may be a separate bug!)

'marcelo' somehow got the BOM character replaced by a literal '?', notice that 'git diff' on these changes will, indeed, show the removed character in 'gustave' as a literal '?'. Notice also that the character in question, the BOM, is actually the Unicode 'zero width no-break space', so it is pretty invisible.

The remaining files seem to have suffered major corruption possible as a result of dostounix style convertions. The line endings, normally on Unix or on Windows, had been converted to and the BOM had been replaced by a character.

Signed-off-by: John Bowler jbowler@...


[espeak-ng:master] New Comment on Pull Request #693 Fixed UTF8 BOM and consequent damage to !v files
By jbowler:

NOTE: 'gustave' really does have a change, the github.com HTML interface does not display anything for the zero-width non-breaking space.


Updates to Github #github

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

[espeak-ng:master] New Issue Created by Qchristensen:
#692 Crash when folder has accented character

(Template copied from NVDA issue template)

Steps to reproduce:

  1. Start NVDA 2019.3 beta 1.
  2. Create a portable copy.
  3. When asked where to create the portable copy, specify a folder name which includes a character such as é, ç, ş, ğ.
  4. Start the portable version.
  5. Open NVDA's synthesizer dialog (NVDA+control+g)
  6. Press HOME or use the arrow keys to select the "eSpeak NG" synthesizer.
  7. Press ENTER.

Actual behavior:

At the last step, NVDA immediately stops running (visually, the icon stays in the system tray until you mouse over it, that's simply an artifact of Windows not cleaning up properly - NVDA is not running by this point).

The very last entry in my NVDA log at Debug level is:

IO - inputCore.InputManager.executeGesture (13:03:39.817) - winInputHook (17464): Input: kb(desktop):enter

(Registering the ENTER key being pressed to activate the OK button, set the synthesizer and close the synthesizer dialog.)

Expected behavior:

Synthesizer should switch to eSpeak NG and NVDA should continue working normally.

System configuration

NVDA installed/portable/running from source:

Portable, and setup in a folder which includes an accented character such as é, ç, ş, ğ

NVDA version:

2019.3 beta 1 (which uses eSpeak NG 1.51-dev, commit ca65812ac6019926f2fbd7f12c92d7edd3701e0c).

Windows version:

Windows 10 Version: 18362.388

Name and version of other software in use when reproducing the issue:

Other information about your system:

Other questions

Does the issue still occur after restarting your PC?

Yes

Have you tried any other versions of NVDA? If so, please report their behaviors.

Yes, 2019.2.1 works fine in this situation.


[espeak-ng:master] New Issue Created by Qchristensen:
#692 Crash when folder has accented character

(Template copied from NVDA issue template - filed as NVDA issue 10607 https://github.com/nvaccess/nvda/issues/10607)

Steps to reproduce:

  1. Start NVDA 2019.3 beta 1.
  2. Create a portable copy.
  3. When asked where to create the portable copy, specify a folder name which includes a character such as é, ç, ş, ğ.
  4. Start the portable version.
  5. Open NVDA's synthesizer dialog (NVDA+control+g)
  6. Press HOME or use the arrow keys to select the "eSpeak NG" synthesizer.
  7. Press ENTER.

Actual behavior:

At the last step, NVDA immediately stops running (visually, the icon stays in the system tray until you mouse over it, that's simply an artifact of Windows not cleaning up properly - NVDA is not running by this point).

The very last entry in my NVDA log at Debug level is:

IO - inputCore.InputManager.executeGesture (13:03:39.817) - winInputHook (17464): Input: kb(desktop):enter

(Registering the ENTER key being pressed to activate the OK button, set the synthesizer and close the synthesizer dialog.)

Expected behavior:

Synthesizer should switch to eSpeak NG and NVDA should continue working normally.

System configuration

NVDA installed/portable/running from source:

Portable, and setup in a folder which includes an accented character such as é, ç, ş, ğ

NVDA version:

2019.3 beta 1 (which uses eSpeak NG 1.51-dev, commit ca65812ac6019926f2fbd7f12c92d7edd3701e0c).

Windows version:

Windows 10 Version: 18362.388

Name and version of other software in use when reproducing the issue:

Other information about your system:

Other questions

Does the issue still occur after restarting your PC?

Yes

Have you tried any other versions of NVDA? If so, please report their behaviors.

Yes, 2019.2.1 works fine in this situation.


Updates to Github #github

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

[espeak-ng:master] New Comment on Issue #691 Differences between bashkir and tatar?
By valdisvi:

They are related, but completely different languages used in different regions of Russian Federation: - Tatar in Tatarstan, - Bashkir in Bashkortostan.

For both of them I created initial configuration as a starting point for interested contributors, looking at https://www.101languages.net/. It may be, I did something wrong, but potential contributors have not tried to give any contribution/feedback yet.


[espeak-ng:master] New Comment on Issue #691 Differences between bashkir and tatar?
By valdisvi:

They are related, but different languages used in different regions of Russian Federation: - Tatar in Tatarstan, - Bashkir in Bashkortostan.

For both of them I created initial configuration as a starting point for interested contributors, looking at https://www.101languages.net/. It may be, I did something wrong, but potential contributors have not tried to give any contribution/feedback yet.


[espeak-ng:master] new issue: Differences between bashkir and tatar? #github

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

[espeak-ng:master] New Issue Created by hozosch:
#691 Differences between bashkir and tatar?

Hi, I noticed that the numbers in these two languages I mentioned are exactly the same, so is there a difference there? I don't see a point in adding the same language twice with different names.


Updates to Github #github

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

[espeak-ng:master] New Comment on Issue #690 Testsuite fails on various archs
By sthibaul:

That fixes it indeed, thanks!


[espeak-ng:master] Issue #690 Testsuite fails on various archs closed by sthibaul.


Updates to Github #github

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

5 New Commits:

[espeak-ng:master] By Samuel Thibault <samuel.thibault@...>:
d3ecd919e4ea: Factorize mbrola build rule

Modified: Makefile.am
Modified: docs/mbrola.md


[espeak-ng:master] By Samuel Thibault <samuel.thibault@...>:
03ec60543249: Use $(CURDIR) instead of $(PWD)

Modified: Makefile.am


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
00c37d667f58: grc: add Greek variant letter form support; fixes pronunciation of the test

Modified: CHANGELOG.md
Modified: dictsource/grc_rules
Modified: tests/language-pronunciation.test


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
1c2e662cbbb4: el: add Greek variant letter form support

Modified: CHANGELOG.md
Modified: dictsource/el_rules


[espeak-ng:master] By Reece H. Dunn <msclrhd@...>:
f47559438bfa: Merge remote-tracking branch 'sthibaul/fix3'

Modified: Makefile.am
Modified: docs/mbrola.md


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

#689 Use $(CURDIR) instead of $(PWD)

$(CURDIR) is set by make, while $(PWD) would have to come from the shell, which may not define it.


[espeak-ng:master] New Comment on Issue #690 Testsuite fails on various archs
By rhdunn:

I've pushed a fix for the missing letter issue (00c37d667f58e5a36853eb9ac08b09567a150704) so the platforms that are currently failing the tests should now pass.

I haven't investigated a better way to handle/recover from a letter not having a .group/.replace entry, nor have I investigated why there is a different behaviour between the two platforms when the letter is at the start of a word.


[espeak-ng:master] reported: Testsuite fails on various archs #github

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

[espeak-ng:master] New Comment on Issue #690 Testsuite fails on various archs
By rhdunn:

In the grc_dict file there are no entries for the letters that have issues -- no .group or .replace entries. For example, the letter ϰ is Unicode character U+03F0 (GREEK KAPPA SYMBOL) -- a cursive version of kappa [κ] -- is missing.

This is why the translation is aborting part way through, although I don't understand why amd64 and arm64 have a different behaviour when a missing letter is at the start of a word.

The fix for this test is to map the cursive Greek letters to their non-cursive counterparts.