[jawsscripts] Re: Simple question regarding sayString, in thevoice you want?
- From: Hugh Brackett <hugh@xxxxxxxxxxxx>
- To: jawsscripts@xxxxxxxxxxxxx
- Date: Sat, 31 Jan 2009 19:45:35 -0500
Geoff:
It's a common programming convention to have the names of constants that
are defined in header files in uppercase. They are very different from
the variables in the program--They don't even exist at runtime; the
compiler replaces them with the value. JAWS scripting language isn't
case sensitive, so there's no technical reason you shouldn't use mixed
case. It's purely a convention, and it's aimed at sighted programmers.
That said, if you're sending scripts to other people, they probably
expect uppercase. It shouldn't be too hard to write a program that fixes
constants to match the capitalization in the header file. Going the
other way to make scripts sound better is trickier. The program would
need a dictionary file to know how to write the constants. The
dictionary would initially only need a few dozen entries to handle
commonly used constants. Users could add any others they use and share
them on the wiki. If enough people are interested I'll take a stab at
it.
On Sat, 2009-01-31 at 10:46 +1100, Geoff Chapman wrote:
> woooo! Jackie and David! thank you thank you!
> I'm sooo sorry! how could I have not seen this before! so obvious now eh.
> <grin.>
>
> Thanks for pointing out to the dumbster this function. I never knew this
> existed! ok, so maybe I need tips on using the fsdn.chm properly.
>
> like I've now typed "say" into the search box of that help file, and looked
> down the list of all the SayOptions! my goodness there's a heapofem in
> there eh.
> Some I'd certanily never new existed! so this will be enormously helpful for
> me across the board I'd say.
>
> Thanks again to both of you for pointing out this one.
> one other note: it appears to me as though these constants, in the hjConst
> file, are all upper case. Yet it seems to work quite happily, I've just
> tested it, if their split up using normative Upper and Lower Case letters to
> make stuff speak good. like vctx_PcCursor and VCTX_JawsCursor, rather than
> VTX_PCCURSOR, which doesn't speak so good. So, is there some magical
> methodological reason why they've put them all in upper case in this file?
> and do we need bother with whatever reason that might be, if they work
> equally well with mixed case?
>
> thanks again for the great tip on this one.
> that'll be heaps helpful for me now that I know that.
> geoff c.
>
> ----- Original Message -----
> From: "David Farough" <David.Farough@xxxxxxxxxxxxx>
> To: <jawsscripts@xxxxxxxxxxxxx>
> Sent: Saturday, January 31, 2009 3:20 AM
> Subject: [jawsscripts] Re: Simple question regarding sayString, in thevoice
> you want?
>
>
> > Hi Jeff:
> > How about SayUsingVoice?
> >
> > Here is the fsdn entry.
> >
> > Function: SayUsingVoice
> > Description
> > Speak a string of text using a specific synthisizer voice.
> >
> > Returns
> > Type: Void
> >
> >
> > Parameters
> > Param 1:
> > Type: String
> > Description: Type in the constant representing the voice to be used.
> > These constants are defined in the file hjconst.jsh and are listed
> > below: VCTX_GLOBAL, VCTX_MESSAGE, VCTX_KEYBOARD, VCTX_SCREEN,
> > VCTX_PCCURSOR, VCTX_JAWSCURSOR
> > Include: Required
> >
> >
> > Param 2:
> > Type: String
> > Description: Type the text that is to be spoken, or specify a variable
> > name or script function that can provide the required text string. Text
> > strings that are typed must be enclosed within quotation marks.
> > Include: Required
> >
> >
> > Param 3:
> > Type: Int
> > Description: Type in one of the following constants that represent the
> > output mode to be used: OT_STRING, OT_LINE, OT_WORD, OT_CHAR, OT_FIELD,
> > OT_CHUNK, OT_SAYALL, OT_SPELL, OT_PHONEMIC, OT_APP_NAME, OT_DIALOG_NAME,
> > OT_CONTROL_NAME, OT_MDI_NAME, OT_WINDOW_NAME, OT_GRAPHIC, OT_HELP,
> > OT_STATUS, OT_SELECTED, OT_TEXT, OT_POSITION, OT_STATIC, OT_FONT,
> > OT_KEYBOARD, OT_CURSOR, OT_DEBUG.
> > Include: Required
> >
> >
> > Param 4:
> > Type: Int
> > Description: Not available yet
> > Include: Optional
> >
> >
> > Version
> > This function is available in the following releases:
> >
> > PAC Mate 1.10 and later
> > JAWS 4.51 and later
> > Magic 10.5 and later
> >
> > David Farough
> > Application Accessibility Coordinator/coordonateur de l'accessibilité
> > Information Technology Services Directorate /
> > Direction des services d'information technologiques
> > Public Service Commission / Commission de la fonction publique
> > Email / Courriel: David.Farough@xxxxxxxxxxxxx
> > Tel. / Tél: (613) 992-2779
> > __________
> > Visit and contribute to The JAWS Script Repository http://jawsscripts.com
> >
> > View the list's information and change your settings at
> > //www.freelists.org/list/jawsscripts
> >
>
> __________
> Visit and contribute to The JAWS Script Repository http://jawsscripts.com
>
> View the list's information and change your settings at
> //www.freelists.org/list/jawsscripts
>
__________�
Visit and contribute to The JAWS Script Repository http://jawsscripts.com
View the list's information and change your settings at
//www.freelists.org/list/jawsscripts
Other related posts:
