Question about CTRL+Right navigation in text window
Posted: Sat Aug 09, 2008 7:58 am
Hello, Akelpad developers,
I'm Kostadin Kolev from Bulgaria.
First, let me say, that Akelpad is one of the most easiest, lightweight and accessible text editors around! I said "accessible" not occasionally. I'm a visually impaired PC user and due to that I'm using screen reading software to help my self while using the PC. At the moment I use JAWS for Windows and the open-source NVDA screen readers and both work very good with AkelPad.
And now to my questions: I've noticed that in the text window of AkelPad when pressing CTRL+Right to navigate to next word, the cursor doesn't go to the beginning of the next word. Instead, it goes to the end of the same word. This is not very good for us - visually impaired users - because the screen readers (at least JAWS and NVDA) use CTRL+Left/Right to go (and read) the previous/next word in text fields. And since the command is not working correctly in AkelPad, the screen readers can't read the next word in AkelPad's text window. Note that only the CTRL+Right command (next word) is not working as it should - the CTRL+Left (previous word) is working normally - the cursor goes at the beginning of the previous word and the screen readers read the word as it should happen. I've noticed that when I disable the option "Words delimiters:", the CTRL+Right command starts working almost correctly. But why doesn't work correctly when the option "Words delimiters:" is enabled?
And some kind of feature request: It's related to my first question. Can you make it possible that while pressing CTRL+Left/Right to go to previous/next word, the cursor will stop not only on words, but also to punctuation signs (e.g.: dash, comma, period, left and right bracket/parenthesis, colon etc)?
Thank you for your help in advance!
Best wishes!
I'm Kostadin Kolev from Bulgaria.
First, let me say, that Akelpad is one of the most easiest, lightweight and accessible text editors around! I said "accessible" not occasionally. I'm a visually impaired PC user and due to that I'm using screen reading software to help my self while using the PC. At the moment I use JAWS for Windows and the open-source NVDA screen readers and both work very good with AkelPad.
And now to my questions: I've noticed that in the text window of AkelPad when pressing CTRL+Right to navigate to next word, the cursor doesn't go to the beginning of the next word. Instead, it goes to the end of the same word. This is not very good for us - visually impaired users - because the screen readers (at least JAWS and NVDA) use CTRL+Left/Right to go (and read) the previous/next word in text fields. And since the command is not working correctly in AkelPad, the screen readers can't read the next word in AkelPad's text window. Note that only the CTRL+Right command (next word) is not working as it should - the CTRL+Left (previous word) is working normally - the cursor goes at the beginning of the previous word and the screen readers read the word as it should happen. I've noticed that when I disable the option "Words delimiters:", the CTRL+Right command starts working almost correctly. But why doesn't work correctly when the option "Words delimiters:" is enabled?
And some kind of feature request: It's related to my first question. Can you make it possible that while pressing CTRL+Left/Right to go to previous/next word, the cursor will stop not only on words, but also to punctuation signs (e.g.: dash, comma, period, left and right bracket/parenthesis, colon etc)?
Thank you for your help in advance!
Best wishes!