Skip to content
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

eSpeak Hungarian: when arrowing through virtual buffers or querying title bars, NVDA seems to glue the last two words on the line together (i.e. speaks them as if there were no spaces between them) #1879

Closed
nvaccessAuto opened this issue Nov 1, 2011 · 8 comments

Comments

@nvaccessAuto
Copy link

Reported by Palacee_hun on 2011-11-01 18:10
OS: Windows XP Home SP3 Hungarian lang., using Espeak synth
[produce the error and its peculiarities, you can do the following:
[[br]([br]]
To)]

  1. Bring up Gmail in a browser window or tab ang log in in case you are not logged in automatically.[use Firefox 3.6.23 to do this test, but IE does the same. My Gmail interface is English basic HTML for this test.[[br]([br]]
    I)]
  2. Press Ctrl+Home then a down arrow to listen to the second line of the Gmail Inbox webpage which is a 2nd level heading and reads "Account Options". But NVDA through Espeak announces it as "Accountoptions" so like there were no spaces between the two words.[Ascertain that NVDA indeed sees the space by pressing NVDA+up arrow twice quickly to spell the line. And yes the space is of course there after the "t".[[br]([br]]
    3.)]
  3. Now access the same heading by quicknaw: Ctrl-Home then "h". Surprise, this will be read out correctly this time with the space, the two words are distinct.[For another example, arrow down till you find the "Compose Mail" link. It will be again read out without the space between the two words after NVDA has announced its keyboard shortcut: Alt+Shift+C. Do the spelling test on this line too (step 3.) and the space is there of course. Finally locate this link with quicknaw: Ctrl-Home then press "k" until you hear it. And this time, it's correct again this way.[[br]([br]]
    5.)]
  4. Press NVDA+T to hear the tittle bar which will end in "Mozilla Firefox", but these two words also get glued together.[[br]]
    This behaviour was definitely not present in snapshot R4695, but 2011.3 beta1 has it. Punctuation level does not matter, nor does the state of the autolanguage switch. Arrowing through an edit field on a webpage also displays this behaviour.
@nvaccessAuto
Copy link
Author

Comment 1 by Ahiiron on 2011-11-01 18:26
Can't confirm here on XP SP3 using NVDA2011.3 beta1, IE8, using eSpeak. Could this be perhaps a Hungarian localization bug?
I did a few tests using eSpeak, but typing "accountoptions" reads exactly (or very similar to) how it sounds as "account options." Of course, camel case like "AccountOptions" sounds just fine, as NVDA's builtin dictionary handles this.

@nvaccessAuto
Copy link
Author

Comment 2 by Palacee_hun (in reply to comment 1) on 2011-11-01 18:56
I note that I think the gap between two separate words is longer in the Hungarian voice of Espeak than in the English voice and it seems to be so for every version of Espeak I have ever used as part of NVDA. So it's much easier to decide whether two words are separated with spaces or not using the Hungarian voice. The described behaviour was instantly noticeable in 2011.3 beta1 after installing it, it was so remarkable. I only wanted to test it thoroughly before reporting, that's why I delayed reporting it till now. I am not aware of any Hungarian language related changes since R4695.
[to [comment:1 Ahiiron]([br]]
Replying):

Can't confirm here on XP SP3 using NVDA2011.3 beta1, IE8, using eSpeak. Could this be perhaps a Hungarian localization bug?

I did a few tests using eSpeak, but typing "accountoptions" reads exactly (or very similar to) how it sounds as "account options." Of course, camel case like "AccountOptions" sounds just fine, as NVDA's builtin dictionary handles this.

@nvaccessAuto
Copy link
Author

Comment 3 by jonsd on 2011-11-01 19:16
Which version of eSpeak is this using?

This may be due to a change which I made for the Hungarian language in eSpeak development version 1.45.46. eSpeak version 1.45.47 contains an improved version of this change, so if version 1.45.46 is currently being used then version 1.45.47 may fix the problem.

This change to the eSpeak Hungarian voice was requested by Hammer Attila hammera@pickup.hu who uses eSpeak on Linux rather than with NVDA on Windows.

The purpose was to improve the intonation of personal names. If it causes problems in other places then perhaps I should remove it.

The rule is this (for the Hungarian voice only): If the final two words of a sentence or clause (i.e. before punctuation) both have capital letters, then the second of these words is not stressed. For example, using the command-line version of eSpeak 1.45.47 compare:

espeak -v hu "Hammer Attila"
espeak -v hu "Hammer Attila."

The bug in eSpeak 1.45.46 was that the rule was applied even if there was no punctuation after the two words.

@nvaccessAuto
Copy link
Author

Comment 4 by briang1 on 2011-11-01 19:24
Well using the English version I cannot get the effect here on the same page, though Google are fooling about with the standard html a bit of late, but I cannot see they could affect this.

@nvaccessAuto
Copy link
Author

Comment 5 by Palacee_hun (in reply to comment 3) on 2011-11-01 20:43
You've just pinpointed the cause of the reported issue, thanks!!! [beta1 contains 1.45.46, while R4695 ran on 1.45.45. Your description of this special rule seems to explain everything. So this is Hungarian-specific.[[br]([br]]
2011.3)]
Now I think the next step would be for NVDA to require 1.45.47, which change of course would need further testing from users in order to find accidental bugs, and I am not sure whether the developers would undertake this in this phase of the 2011.3 release cycle (we are in beta1!)[to [comment:3 jonsd]([br]]
Replying):

Which version of eSpeak is this using?

This may be due to a change which I made for the Hungarian language in eSpeak development version 1.45.46. eSpeak version 1.45.47 contains an improved version of this change, so if version 1.45.46 is currently being used then version 1.45.47 may fix the problem.

This change to the eSpeak Hungarian voice was requested by Hammer Attila hammera@pickup.hu who uses eSpeak on Linux rather than with NVDA on Windows.

The purpose was to improve the intonation of personal names. If it causes problems in other places then perhaps I should remove it.

The rule is this (for the Hungarian voice only): If the final two words of a sentence or clause (i.e. before punctuation) both have capital letters, then the second of these words is not stressed. For example, using the command-line version of eSpeak 1.45.47 compare:

espeak -v hu "Hammer Attila"

espeak -v hu "Hammer Attila."

The bug in eSpeak 1.45.46 was that the rule was applied even if there was no punctuation after the two words.

@nvaccessAuto
Copy link
Author

Comment 6 by jteh on 2011-11-03 02:34
084a037 requires eSpeak >= 1.45.47 and the build server has been updated accordingly. Please test a snapshot (once it becomes available) and close this ticket if it is fixed.
Changes:
Changed title from "Regression in 2011.3 beta1: when arrowing through virtual buffers or querying tittle bars, NVDA seems to glue the last two words on the line together (i.e. speaks them as if there were no spaces between them)" to "eSpeak Hungarian: when arrowing through virtual buffers or querying title bars, NVDA seems to glue the last two words on the line together (i.e. speaks them as if there were no spaces between them)"
Milestone changed from None to 2011.3

@nvaccessAuto
Copy link
Author

Comment 7 by erion (in reply to comment 6) on 2011-11-03 11:53
Replying to jteh:

084a037 requires eSpeak >= 1.45.47 and the build server has been updated accordingly. Please test a snapshot (once it becomes available) and close this ticket if it is fixed.

Tested using main-4773. When two words next to each other begin with a capital letter they are properly stressed, however when they are followed by any punctuation mark the stress moves to the first word.
It is difficult to say whether this is fixed, as some may prefer this way when reading proper nouns, though it sounds horrible when there are phrases such as: Mozilla Thunderbird, Portable Edition.

I think the rule should also be ignored if two capitalized words are followed by a punctuation symbol other than a comma.

@nvaccessAuto
Copy link
Author

Comment 8 by Palacee_hun on 2011-11-09 13:23
After testing release-branch snapshot 4762 with Espeak 1.45.47 for a few days, I consider the situation satisfactory, and no other problems with the new Espeak version popped up.
[[br]]
I note that the Espeak rule described above about the stressing of adjoining capitalised words is highly subject to personal preference, not an inherent part of Hungarian phonetics. I personally feel the stressing much more unnatural when applying the new rule, the proposer probably felt the other way round. But the fixed rule restricts its application to such few cases that it doesn't cause much trouble to me any more. Should that bother me in the future, I'll just remove the rule myself and recompile the rule file by a command line version of Espeak.
Changes:
State: closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant