Bug 10483

Summary: text to speech, speak time not speaking it correctly
Product: Mageia Reporter: Ezequiel Partida <ezequiel_partida>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: balcaen.john, lmenut, mageia
Version: 3   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:

Description Ezequiel Partida 2013-06-11 00:18:53 CEST
Description of problem:

Today I was able to enable text to speech in the Digital Clock settings / General / Text to Speech.

And the problem is that time is not spoken correctly.. If it's 3:12pm, it is spoken as: This is Three twelve P.M (This is correc),

But it the time is 12.09 pm it is spoken as: it is three thousand nine p.m


Version-Release number of selected component (if applicable):

I am using mageia 3 final using jovie 4.10.2


How reproducible:


Just install jovie 4.10.2 and choose text to speeck, speak time in the Digital Clock settings on the menu bar and set it to any time lower than 10 minutes, lets'say 3:06pm or am.



Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Manuel Hiebel 2013-06-11 21:06:03 CEST
from the readme.urpmi (which is not shown from a default install :/)

"In order to use jovie you first need to configure the speed-dispatcher daemon
using spd-conf (this binary is provided by python-speechd)
If you're using the default mageia sound configuration (pulseaudio per default)
you should configure speed-dispatcher using spd-conf this way:
- create a user configuration
- default module output is espeak
- select your default language
- default audio output method needs to be pulse & not alsa
- default port needs to be 6560"

CC: (none) => balcaen.john, lmenut, nicolas.lecureuil

Comment 2 Marja Van Waes 2015-03-31 16:04:23 CEST
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD