-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TTS of registered tickets starting with 0 pronounced incorrectly #174
Comments
I'm not able to reproduce the issue. I tested it in English and Arabic seems to work as expected. Also the system should start incrementing tickets from
Update: i was able to reproduce the issue, using numeric registered tickets. and inserting |
Remove 0 noise from registered tickets. Resolves #174
I'm using FQM v0.8 beta. I only use en-us. I somehow found a solution to this. I tried putting "<double space> + 1" instead of "001".
I also want to request that the announcement could say a phrase before the number (ticket) e.g.: "Client number 1, please proceed to table number 5."
Thank you!
Sent from Yahoo Mail on Android
On Thu, Jul 9, 2020 at 3:27 AM, Mohamed Feddad<[email protected]> wrote:
I'm not able to reproduce the issue. I tested it in English and Arabic seems to work as expected. Also the system should start incrementing tickets from 100 so you should never face a scenario where a ticket is 001 or 010, same with the offices numbers if you enter 030 it will automatically change it to 30 and it's pronounced correctly.
- What version of FQM you're running ?
- What languages are you using ?
- Can you include a screenshots or steps on how to reproduce the issue ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Supporting custom TTS announcements is not implemented yet , probably won't be anytime soon. You can us Most welcome! |
It reads "001" as "O-O-One". Could be better if it reads it as "One".
Example: "040" is announced as "O-Four-O". It should be announced as "Forty".
The text was updated successfully, but these errors were encountered: