Re: JAWS Scripts - Are they interpreted or compiled?

Roger Newell

In addition to what Matthew has said, Freedom Scientific uses many,
many folders across your PC to store files, many of which may be
referenced at any time. Having files whose version does not match
other files has the potential to break JAWS functionality when JAWS
receives updates throughout the year.

On 11/29/18, Matthew Horspool <> wrote:
Hi Isaac,

I'm afraid I'm not convinced that this is necessary or even appropriate.
Freedom Scientific scripts could change at any time, even from minor JAWS
version to minor JAWS version. If you restore from a personal backup of the
Freedom Scientific stock scripts you could well end up restoring an earlier
version which re-introduces problems which have subsequently been fixed.

A JAWS repair is a perfectly adequate way of restoring stock scripts if they
do go missing somehow. If you're particularly paranoid you could keep a
backup copy of the JAWS installer.


-----Original Message-----
From: [] On Behalf Of Isaac
Sent: 29 November 2018 10:28
Subject: Re: JAWS Scripts - Are they interpreted or compiled?

Yes, but also backup the freedomscientific scripts as well so you always
have a clean copy if you need it.

----- Original Message -----

From: "Roger Newell"

To: <<>>

Sent: Thursday, November 29, 2018 3:31 AM

Subject: Re: JAWS Scripts - Are they interpreted or compiled?

Back up your user scripts folder, because this is where script files you
modify are saved to, so that they do not become mixed with the scripts
Freedom Scientific provides. The location of your user scripts folder is the
one I provided in step 4 of Part a of my instructions.

On 11/29/18, Isaac <<>>

also to add to what you just said, after a new install copy the
default scripts folder some place else so you have a backup so in the
future if you
are modifying scripts you don't have to uninstall jaws and reinstall
as there might be other scripts you have modified and would lose. The
point is
hear, backup, backup, backup. Always backup.
----- Original Message -----
From: "Roger Newell"
To: <<>>
Sent: Thursday, November 29, 2018 12:43 AM
Subject: Re: JAWS Scripts - Are they interpreted or compiled?
Those instructions are incorrect. You should never modify default.jss
or default.jsb files. There are other ways that Freedom Scientific has
designed for you to create or modify JAWS behavior.
What you need to do is this:
Part A: Check your default.jss and default.jsb file 1. Open Script
Manager and press CTRL+SHIFT+D to load the default file.
2. See if your punctuation script is in the file. If it is, keep
following these instructions. If not, skip to Part B.
3. You need to get a clean copy of these files. The way I would
recommend is to completely remove JAWS 2019 from your system. Then
install JAWS 2019 again, but do not migrate any settings because then
you will be back where you started.
4. Check before using JAWS that this folder is completely empty:
Part B: Adding your punctuation script 1. Open Script Manager.
2. Press CTRL+O to open the Open dialog.
3. Navigate to this location: C:\ProgramData\Freedom
4. Open the file MyExtensions.jss.
5. Write your script at the bottom of this file, and press CTRL+S to
On 11/29/18, Tom <<>> wrote:
Following is the punctuation script and where it is available along
with installation instructions.
Maybe it does needs compiling again under Jaws 2019 and so I’ll try
that solution.
Follow these steps to insert the code required to set up a hot key to
toggle the Jaws punctuation level.
press insert 0 (on the number row).
press control shift D
You should hear jaws script manage default.jss.
Hit control+end this will take you to the bottom of the file.
Hit enter twice, to insert a couple of blank lines.
paste in the following lines for the script:
Script TogglePunctuation ()
Say (PunctuationToggle (false), ot_no_disable) EndScript
Place your cursor on the line that says Say (PunctuationToggle
(false), ot_no_disable).
Hit control+d.
Hit tab this will put you on the "can be attached to key" check box,
this should be checked, if it is not hit "space bar" to check it.
Hit tab this will take you to the "synopsis" where you can put in a
short description if you want.
Tab to the "assign short cut key" field and press the keystroke you
want to use for the script. Such as Control+Shift+P.
Tab to the okay button and enter. This will take you back to the
script editor.
Press control+S to compile your changes.
Press Alt-F4 to close the script editor
-----Original Message-----
[] On Behalf Of
Roger Newell
Sent: Wednesday, 28 November 2018 7:07 PM
Subject: Re: JAWS Scripts - Are they interpreted or compiled?
I haven't heard of this particular script.
Just to verify, is this a third-party script for which you were
provided with the .jsb file? If so, please make sure you can locate
the file in the following location:
Scientific\JAWS\2019\Settings\enu If you have the .jss and/or .jsh
file, you should probably show it to someone who knows how to read it
to verify that it's not calling on a particular script or function or
something that's been moved around in JAWS 2019.
On 11/28/18, Tom <<>>
Using: W10 64 bit and Jaws 2019.
I have experienced a problem with the punctuation script since
upgrading from Jaws 2018 to 2019.
Under 2018, the script could be run from anywhere on the system but
since changing to 2019, the only place the script works is when it
is run from the desktop. If I am in a folder on another drive say,
hitting shift control P, Jaws says, "unknown script call to".
If I still wish to change the punctuation level then it is a trip
back to the Desktop and try again.

Join to automatically receive all group messages.