it, and there was no known reason it shouldn't work -- I disabled it
only because WW 1.0 was supposed to not work on 95, but Than wasn't
sure why. WB confirms that it works on W95. Also enabled NT 4.x
(which should work if 95 does).
Changed name of Setup file to use an underscore rather than space, to
make Than's web script happy.
the spec now mandates use of the PUA, which can be accessed with \u
normally).
Clarify warning about bug in typing Sanskrit.
Document autocorrect bug.
Remove references to "2.0b1" (anticipating release of 2.0b2).
Slight clarification of template attachment.
all of these working except for ones noted in SF. I was very short on sleep
then, and apparently I hadn't. Two of the failing test cases were bogus
(not valid Tibetan or Sanskrit), and I've moved them to the appropriate
part of the file.
Two are genuine bugs I didn't know about. Aaargh.
Commented out (but did not remove) the Startup installation feature (because,
due to Word bugs, WW doesn't work right when loaded from Startup).
Removed some code that was supposed to deal with the "sara->sra" bug
(#800153 in SourceForge) but didn't. The code was not actually called
(because I knew it didn't work) but I had left it in on the theory that
it might be fixable (but it probably isn't; a different approach is required).
Added comment to code about ga.yarma problem.
Updated the EWTS URL in the Tibetan menu for new thdl.org organization.
On the Italian keyboard layout, there is simply no way to get a backquote,
so VkKeyScan returns -1, which was causing four different pieces of code to
blow up. Fixed to check this case. (For an unnamed friend of Werner Bruns.)
Improve success message for phonetics testing.
problems seen by other people but not me. Specifically:
Added "Microsoft Scripting Runtime" to VBA References. This might fix Werner
Bruns's problem with "object not found" error during installation.
Eliminated use of SendKeys in CapsLock translation, on the theory that it was
responsible for DG's CapsLock problem.
Changed all instances of Application. to Word.Application., which shouldn't
be necessary according to the documentation, but seems to be more robust.
Type-declared all Function return values (in attempt to avoid stupid run-time
errors when loading from Startup folder; apparently code run from there is
executed differently from that loaded from the templates folder, in a mode that
is more sensitive to missing type declarations).
