Framework for describing characters #55

Closed
nvaccessAuto opened this Issue Jan 1, 2010 · 14 comments

2 participants

@nvaccessAuto

Reported by allan on 2008-03-26 21:47
Read phonetic representation and ASCII value is quite important and should add into NVDA future release.
Blocking #635

@nvaccessAuto

Comment 1 by jteh on 2008-03-26 23:31
The problem with reading phonetic representation is that it presents localisation issues. While we can certainly allow for phonetic reading of the English alphabet, providing similar functionality for all languages is extremely difficult. Furthermore, it is dependent on the synth language in use, not necessarily the NVDA language. We have very similar problems with the current punctuation support.

@nvaccessAuto

Comment 2 by aleksey_s on 2008-07-30 08:53
at least reading ascii representation of the character was done by me and you can press numpad2 three times to hear this one as well as hex.

@nvaccessAuto

Comment 3 by bernd Dorer on 2008-08-03 12:25
Alexey_s wrote:

at least reading ascii representation of the character was done by me and you can >press numpad2

three times to hear this one as well as hex.

You mean:
You can press numpad2 twice to hear this one as well as hex.

I have tryed it on two systems and you don't have to press numpad2 three times.
I think this fixes this ticket.
Changes:
State: closed

@nvaccessAuto

Comment 4 by jteh on 2008-08-04 02:17
No, this ticket is only partially implemented. The reporter requested both reading of phonetic representation (alpha, bravo, etc.) as well as ASCII value. The latter has been implemented, but the former has not. (These should probably have been filed as separate tickets, but no matter.)
Changes:
State: reopened

@nvaccessAuto

Comment 6 by Bernd on 2010-08-20 23:51
I think for now, it would be better if we could implement it for each language. If we find a method to bind it to the synthesizers voice we can do this then.

@nvaccessAuto

Comment 7 by mdcurran on 2011-01-21 00:25
Changes:
Milestone changed from None to near-term

@nvaccessAuto

Comment 8 by jteh on 2011-03-31 06:49
We've determined that this will be done separately from symbol/punctuation handling, though probably in the same module (characterProcessing).
Changes:
Changed title from "Read phonetic representation and ASCII value" to "Framework for describing characters"

@nvaccessAuto

Comment 10 by mdcurran on 2011-04-05 03:49
Work is underway in branch: http://bzr.nvaccess.org/nvda/characterDescriptions/
In this branch it is now possible to get the description (examples) for a character by using particular review cursor commands:
review current character (numpad2) pressed twice will speak the description for the current character.
Review current word (numpad5) and review current line (numpad8) pressed 3 times, will spell the word/line using these descriptions.
A locale should provide a characterDescriptions.dic file inside their locale directory. English and traditional Chinese (Taiwan) have already been provided.
The english one uses the standard English phonetic alphabet (alfa, bravo, charley etc). The traditional Chinese one provides examples from the libchewingdata project: http://libchewingdata.openfoundry.org/

This means that for Traditional Chinese, it is now possible for an NVDA user to identify the meaning of a given traditional chinese character.

At this point in time, the characterDescriptions.dic that is used is based on NVDA's configured locale. It would be nice to use the synth's reported voice language, but it seems that a lot of synths incorrectly report this.

@nvaccessAuto

Comment 11 by mdcurran on 2011-04-05 03:50
Changes:
Milestone changed from near-term to 2011.2

@nvaccessAuto

Comment 12 by m11chen on 2011-04-05 05:37
Hi,

I am trying to call the character description function with the laptop keyboard layout, but pressing NVDA+, twice does not speak anything. Does the gesture map need to be updated to reflect the recent implementation?

Thanks

@nvaccessAuto

Comment 13 by m11chen (in reply to comment 1) on 2011-04-05 05:52
Replying to jteh:

The problem with reading phonetic representation is that it presents localisation issues. While we can certainly allow for phonetic reading of the English alphabet, providing similar functionality for all languages is extremely difficult. Furthermore, it is dependent on the synth language in use, not necessarily the NVDA language. We have very similar problems with the current punctuation support.

Hi,

Sorry, didn't mean to change the type to task.

@nvaccessAuto

Comment 14 by mdcurran on 2011-04-05 06:10
At this point in time your NVDA locale must be either en or zh_TW.
Is it one of these?
What characters were you trying this on?
Do you get any errors, debugwarnings in your log?
In Python console, what output do you get for:
import characterProcessing; characterProcessing.getCharacterDescription('en','d')

You should get the word 'delta'.

Do characterDescriptions.dic files appear in your locale/en and locale/zh_TW directories?

@nvaccessAuto

Comment 15 by m11chen on 2011-04-05 06:53
Oops, I was testing by running the distribution build from the source. Everything works fine when running the original source tree.

@nvaccessAuto

Comment 16 by jteh on 2011-04-20 01:52
Merged in 6147de6 with some subsequent fixes.
Changes:
State: closed

@nvaccessAuto nvaccessAuto added this to the 2011.2 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment