Case sensitivity/insensitivity

[Mike Fletcher]

I use voice recognition (Dragon) exclusively for my Python coding (have for
over a year now). It has never caused a problem with case sensitivity.
Text-to-speech is something I've not tried on code.  It could be there will
need to be a mode created for it where you get "\Cap token \No-Space \Cap
header" output (i.e. the inverse of speech-to-text).  More intelligent would
be to allow both types of systems to easily, interactively, create
per-document vocabularies such that I could say "Say that as 'Cap token
header'" to have the text-to-speech system create a shorthand when reading
(and something similar for the dictating, as well, of course).

Enjoy,
Mike

-----Original Message-----
From: Francis Glassborow [mailto:francis at robinton.demon.co.uk]
Sent: Saturday, May 20, 2000 6:57 PM
To: python-list at python.org
Subject: Re: Case sensitivity/insensitivity


In article <8g742q$2jv3$1 at thoth.cts.com>, Will Rose <cwr at crash.cts.com>
writes
>Some
>people just do see the tokens 'token' and 'Token' as being identical,
>and are very irate if their behaviour differs; others, like me, see
>them as different and hate the additional complexity of trying to
>memorise possible matches.

There is a largish minority for whom using case sensitive tokens is a
menace -- those that rely on text-speech because their eyesight is
severely impaired.

Another problem that will become more visible over the next half dozen
years are the problems of those using voice recognition systems. Of
course these are only issues in the context of identifiers only being
disambiguated by the use of uppercase/lowercase.


Francis Glassborow      Association of C & C++ Users
64 Southfield Rd
Oxford OX4 1PA          +44(0)1865 246490
All opinions are mine and do not represent those of any organisation
-- 
http://www.python.org/mailman/listinfo/python-list