03-04-2002, 09:11 PM
|
|
Contributing Editor Emeritus
Join Date: Aug 2006
Posts: 8,228
|
|
Microsoft Pocket PC dev team seeks input on Transcriber
Derek Brown is looking for feedback and comments on Transcriber on the Pocket PC.
"The Product Manager for handwriting input (i.e. Transcriber) asked Beth and I for customer feedback on improving the product � and I thought I�d come get this straight from the source. If you have suggestions, wishes, problems, etc. I�d be interested in hearing them. Go ahead and discuss on this thread and I�ll make sure the PM sees all of this."
So, post away. We'll gather everything here and make sure he sees it. :-)
|
| |
|
|
|
03-04-2002, 09:23 PM
|
|
Neophyte
Join Date: Mar 2002
Posts: 2
|
|
Left-handed support
Transcriber's algorithms appear to favor right-handed users. Additional left-handed support would help me out greatly (and if Transcriber could move the right-hand scroll bar to the left side when entering text, that would be great too!)
|
| |
|
|
|
03-04-2002, 09:27 PM
|
|
Ponderer
Join Date: Mar 2002
Posts: 56
|
|
Better recognition
I've been frustrated when trying to input a "1" with a straight downward stroke, only to get an "I". In Shape Selector, that's part of input options for "1", but not for "I", yet Transcriber/Calligrapher still recognizes that as an "I". Also, better recognition between "o" and "0". Perhaps try to recognize that zeros are narrower than "O"s. Otherwise, it's pretty good software.
|
| |
|
|
|
03-04-2002, 09:30 PM
|
|
Intellectual
Join Date: Feb 2002
Posts: 147
|
|
1s, Is and ls
:x
Better differentiation between the number "1", lower case "l"s and "I"s.
Please!
|
| |
|
|
|
03-04-2002, 09:31 PM
|
|
Intellectual
Join Date: Dec 2004
Posts: 117
|
|
There are three major things I can think of for improving Transcriber: user defined letter selections, cleaning up stupid recognition errors, and improving performance.
I'd like to be able to define some of my own letter types. I write a lower case 'd' in a slightly odd manner which almost always makes it recognized as a ']'. If I could define my own 'd', things might work better.
The stupid recognition errors would include the 'd' thing - why would I want to write a bracket in the middle of the word 'middle'? - but also differentiating between a lower case 'k' and and upper case one (epecially at the ends of words), and the annoying problem of recognizing the word 'is' as the number 13.
Performance needs to take a huge step up. There are instances, such as using the Find function, where it can take literally 30 to 60 seconds for input to be recognized. It seems to happen most when I haven't inputted any words in a while. I'd say these lags are my number one concern about the program.
Oh, and they should really fix the problem where you can't use Transcriber at all to input a word when looking up a definition in the Reader dictionary.
Jeff
|
| |
|
|
|
03-04-2002, 09:36 PM
|
|
Thinker
Join Date: Feb 2002
Posts: 360
|
|
Transcriber
Over all I think it just needs to be a little smarter IE. follow some of the rules that Word does, like no Caps in the middle of sentences and what not. Other wise I think it works very well and I truly like having it as an input method.
Personnaly speaking though I will never be happy until we have intelligent Speach input!
|
| |
|
|
|
03-04-2002, 09:42 PM
|
|
Pupil
Join Date: Feb 2002
Posts: 21
|
|
Have support for other languages then Englisch. Eq Dutch !!
|
| |
|
|
|
03-04-2002, 09:50 PM
|
|
Ponderer
Join Date: Mar 2004
Posts: 64
|
|
8's
More often than not, my 8's show up as two o's... I don't make the artsy figure 8 style 8's, I'm an engineer!
Also, as someone previously mentioned, there is very few cases where you'd ever want punctuation in the middle of a word, why would transcriber ever think that's what you meant?
It also seems to have a lot of trouble when entering acronyms that are all upper case capitals... especially E's and F's or H's that have multiple strokes...
|
| |
|
|
|
03-04-2002, 09:53 PM
|
|
Neophyte
Join Date: Mar 2002
Posts: 6
|
|
Support multiple input methods simultaneously
One thing that has always bugged me is that it's either Transcriber OR the keyboard... Block Recognizer OR keyboard, etc. This is extremely inconvenient... the keyboard is very handy when entering passwords, but is cumbersome when entering URLs -- seems to me you should be able to do both without flipping modes.
With the keyboard active, I think Transcriber should still be able to read input from the upper 2/3 of the screen, and possibly differentiate between unistroke block recognition and Transcriber style recognition on the fly.
|
| |
|
|
|
03-04-2002, 10:03 PM
|
|
Ponderer
Join Date: Mar 2004
Posts: 88
|
|
User defined styles
I vote for adding the ability to define how you write your characters. As someone else pointed out, I write several letters and numbers differently from what Transcriber defines.
|
| |
|
|
|
|
|
|
Linear Mode
