2016-06-26 18:03:44

Hey folks,

Was wondering if anyone else has had this problem. So, I recently upgraded from Jaws 16 to Jaws 17. Yay, great, wonderful, right? Except for one problem... I had an extensive pronounciation dictionary that I used in Jaws 16, and alas, I cannot seem to be able to transfer it over. Jaws 17 crashes whenever I try to do so. I've heard this is due to a new format that 17 uses... But if so, surely there must be some new way to upgrade my dictionary file or something? I'd copy it over by hand, but we're talking hundreds of entries... Not at all fun to even contemplate, let alone do. Any thoughts?

Best, Albano.

I am Locutus of Borg. Resistance, is futile. Your life, as it has been, is over. From this time forward, you will service---us.

2016-06-27 03:20:02

I thought downwards compatibility would be the problem, not the other way around. When making script files (.jss) in JAWS 17 with the intention of letting them work in 16 and below, you must insert the following line. Hopefully, it will also work in .jdf files.

;#pragma usePoFile 0

2016-06-27 12:16:53

I thought it was going from 16 to 17 not from 17 to 16. Abyway, I am not to sure of anyway for you to do this.

All that is gold does not glitter, Not all those who wander are lost; The old that is strong does not wither, Deep roots are not reached by the frost. From the ashes a fire shall be woken, A light from the shadows shall spring; Renewed shall be blade that was broken, The crownless again shall be king.
DropBox Referral

2016-06-27 12:22:18

Try making one new dictionary entry in 17. Then open the .jdf file in Notepad, ensuring that you open the one with the entry that you just made. Check and see if the format for the entry appears the same as in the file from 16, which you should also open in Notepad. I'm no technical support specialist, but one thing that JAWS may be struggling with is if the format for the dictionary entries, e.g. sections of the file, commas, etc. is different.