when the numbers are placed in the following way, for example... 250 250 in the Spanish language, it is read as follows

[titet11]

250 250... (two hundred fifty thousand two hundred fifty.)

This error occurs only when using 6-digit numbers, but separated by a space in the third digit.

[rmcpantoja]

Hi @titet11,
Look at this NVDA add-on which is designed to improve the readability of numbers, and was inspired precisely by the eloquence ECI bugs to create something better.

[titet11]

@rmcpantoja

Unfortunately this did not solve the problem.

[rmcpantoja]

@rmcpantoja

Unfortunately this did not solve the problem.

Hi @titet11.
Are you using real-time conversion mode? That being the case, the synthesizer should say doscientos cincuenta doscientos cincuenta.

[davidacm]

Hi. This is an issue with the library itself, not the driver. Although it could be solved from the driver side, I think it's outside the driver's responsibilities.
This problem also occurs with other synthesizers. So, a better approach is to fix it before the string is sent to the synthesizer.

[titet11]

@davidacm

Do you think you can solve this problem?

[titet11]

@rmcpantoja
How can I activate the real-time converter?

[davidacm]

No issues need to be fixed here, but the feature could be implemented. Although I don't want to add unnecessary complexity to the driver, as this isn't a bug but rather an original behavior of the synthesizer itself.
I'll analyze this situation and implement some changes to test it. If the added changes involve only a few lines, I'll add the feature with a check setting to enable or disable it.

[titet11]

@davidacm

Perfect, I love your way of thinking and treating the complement. You always think about maintaining the optimization and original functionalities.

I think the new option should be called: "enable correct word and numbers handling"

[titet11]

@rmcpantoja

I just realized that it was necessary to activate an option for this plugin, located within the NVDA options.
What happened is that I previously thought that when installing this plugin I wouldn't have to do any activation and that's why it didn't work.

However, now that I have enabled this plugin's functionality in NVDA, it prevents me from scrolling through almost all text or lines.

I know that the plugin only supports 2023.1 as a minimum version, so I will have to look for an older version of this plugin to make it compatible with 2022.4

[titet11]

@rmcpantoja

Despite having installed the previous versions of the plugin you recommended, they did not work at all with NVDA 2022.4.

So with no other alternatives, I'll wait for David to update the IBMTTS plugin.

[ultrasound1372]

It certainly wouldn't be the first ECI bug we've fixed, like those for the date parser, not to mention the litany of anti-crash expressions. Unsure how you would fix something like that though, does making it two spaces instead of one help?

[titet11]

@ultrasound1372
Yes, adding 2 spaces makes it pronounced correctly