416-621-9348 cgreaves@chrisgreaves.com
Home	Tweet

CURRENT BETA VERSION

INDXR	FAQ	Quick Start	Next Steps
Installation (And TroubleShooting)	Compatible Systems	Features	The Rules Table
Videos	Testimonials	Acknowledgements	Case Studies
User Guide	Companion Applications	What-FAQ	Timing
The Interesting Words Engine	Software Development Kit (SDK)	Macros	CURRENT BETA VERSION

Free Download of the CURRENT BETA VERSION of the 1-Click Indexer.

If you want the current operating version, use the link at the foot of this page, but if you are brave enough to test the beta version, use the link above.

If you have been waiting for a fix to a problem or are experienced in using Indexer and want to check out these new features, please do so. The BETA version is always in use on my own systems; that is, it’s the version I’m running day-in day-out.

What’s in Version 222

2009/10/24	CG	4956: ref #6912 The {XE} entry containing the string}}XE "like “It’s alright, Daddy’s here!”."{{ caused the "like" to appear as a single word. CG: quick fix is probably to replace all the double-quotes with a single quote in GenerateConcordanceEntry	222
2011/04/23	CG	6474: Need to resolve the issue of repeated {Index} 1. Word does a good job of replacing the existing {Index}	222
2011/04/23	CG	6474: ref #6914 Need to resolve the issue of repeated {Index} 2. I seem to be adding an extra section break each call	222
2011/04/23	CG	6474: Need to resolve the issue of repeated {Index} 3. Option to purge all existing {XE} prior to re-scanning the document body. CG: Check box on GUI form	222
2011/08/20	CG	6914: ref #6474 Indexer adds a new section break at each run. Inhibit this.	222
2011/08/20	CG	6919: If there exists an empty document, use it as the Indxr.059 receptacle. CG see function “docGetNewDocument”	222
2011/08/20	CG	6917: We should not ignore a paragraph just because it has a {TOC}{HYPERLINK}{INDEX} CG: Trial fix using prg.Range.Text in “blnInitialiseArrays”	222
2011/08/22	CG	6925: Why does RemoveIndexEntries run so slowly? CG: rewrote using Edit.Find instead of field looping	222

The issue of quotes in an {XE} is not resolved. Microsoft Word uses a single quote within the field for its own purposes and so inhibits any end-user use of a single quote; I am currently looking at a workaround as part of #6912.

Inhibited the extra section break that was appearing on each run of Indexer.

New check box on the form GUIEnvironment: “remove XE entries”, if checked ON will automatically purge ALL {XE} from your document prior to rebuilding the index.

Trail code: If I detect a field code in a paragraph, I process the entire paragraph rather than breaking it down into sentences. This makes the IK and IL array generation a little slower.

Remove Index Entries: I was motivated by the auto-remove (#6474) to rewrite the code. It runs about 8 times faster.

What’s in Version 221

2011/08/21	CG	6921: I am not stripping hard-spaces (asc(160)) when collecting words for strIK2. Possibly other ^w too.	221
2011/08/21	CG	6922: I am collecting words separated only by a comma e.g. “ALIASES,alias”	221

The GUIEnvironment form is updated with a switch and a string for the generic Index Entry code. The text box is an interim measure. For the time being it expects and assumes a self-delimiting string; that is, a string in which the FIRST character is the delimiter. You can use comma, semi-colon, colon, or whatever you like as a delimiter, but your delimiter must announce itself as the first character of the string.

I found a logic error in my “generic” word processing, and in rewriting that code discovered two anomalies in my code that extracts word-strings from the text.

Here is an extract from my test report:

	Case Sensitive	NOT Case Sensitive
Generic	611 words 10 seconds GenericCase.doc	600 words 10 seconds GenericNOTCase.doc
NOT Generic	635 words 10 seconds NOTGenericCase.doc	635 words 10 seconds NOTGenericNOTCase.doc

The smallest index (600 words) is that for a generic case-Insensitive index; we expect this because a generic index economizes on words, as does forcing all comparisons into a common case.

The largest index (635 words) is that for a NON-generic index regardless of case; we expect this because a NON-generic index refuses to economize on words, regardless of case.

The intermediate index (611 words) has made some economy on generic words(“alias” and “aliases”), but refuses to economize on “alias” and “ALIAS”.

I note with some satisfaction that processing time is greatly reduced, and that I am processing a 76-page document in 10 seconds. This run generated 980 {XE} fields, so if you think in the long run you could manage one per minute, that’s about 15 hours work reduced to ten seconds.

What’s in Version 220

2011/08/19	SJ	6909: Process SJ’s file for aliases. CG: Reduced to one column; Forced into lower-case; Sorted in ascending sequence alphabetically; Duplicate words removed; John Gray: I would simply call them "index entries", unless you are referring to the example you give, which should all have been included under the single entry "Alias(es)".	220
2011/08/20	CG	6920: New macros “ResetAbbreviations”, “ResetMonths ”, “ResetNoise”, “ResetPlaces” and “ResetINI”	220
2011/08/20	SJ	6912: I use a lot of I’ve, Don’t, Can’t etc….  namely the use of apostrophe. Can Indexer ignore the apostrophe trail? For example if Can is ignored, it should ignore Can’t. CG: An interim solution. Indexer creates a noise file “Abbreviations1.txt” with 91 entries if it detects that no Rules table is present.	220

This version brings the long-awaited “generic index entry” facility with the GUIEnvironment macro’s switch “Generic”. If this is checked ON then “contact”, “contacted” and “contacts” will appear under the single heading “contact”. If case-sensitive is checked OFF then “contact”, “contacted”, “contacts” “Contact”, “Contacted” and “Contacts” will appear under the single heading “contact”.

Two quick fixes for the apostrophe problem, mainly the provision of an abbreviations noise file which will allow you, at the very least, to ignore 91 standard abbreviations that use apostrophes.

What’s in Version 218

2011/08/19	SJ	6908: Introduce a means to ignore case when comparing words. CG If CaseSensitiveIndex is set FALSE, we use the first-found word as the index entry and map all other case-permutations to that word..	218
2011/08/20	CG	6918: Introduce our standard typOptions	218

Version 218 was not released publicly, but is available on request.

I began an internal upgrade in my use of parameters. Fifteen years ago I didn’t use TYPE structures; now I do. Over the next few versions I will be migrating the run-time parameters into a structure which should reduce errors in coding as I make changes.

I finally implemented the switch “Case Sensitive” on the GUIEnvironment macro’s form. If the checkbox is checked ON then “jaguar”, “Jaguar” and “JAGUAR” will appear as separate entries in the Index. If the checkbox is checked OFF then “jaguar”, “Jaguar” and “JAGUAR” will appear as a single entry in the Index, and the entry used will be the first one to be found – “jaguar” in my example here.

What’s in Version 217

2009/09/29	CG	4882: Implement a command to edit a Rules table directly from the GUI form	217
2009/10/22	CG	4938: Tooltip captions for all GUI controls	217
2011/08/19	SJ	6910: Identify EVERY MsgBox with the name of its immediate host procedure	217
2011/08/20	CG	6916: Cleaned 215 in preparation for updates; Sorted; Stripped to 217	217

Version 217 was not released publicly, but is available on request.

I used my “Proje”ct application to clean and sort code and to eliminate some dead-wood procedures orphaned from previous versions. This reduced template bloat and reduced the possibility of corruption.

Every one of my pop-up message boxes now includes the name of its host procedure in the title bar, so regardless of what the message says, I’ll have a good idea of whereabouts in the program we were at the time the message appeared.

Checked every user control in every GUI form and instituted a ToolTip caption where one was missing; also fixed up a few typos. If you spot a missing caption, or don’t understand the current one, please let me know by email

Implemented a new command button on the GUIEnvironment macro’s form. You can now select a rules table and ask to edit it. Indexer will shell out to a new copy of Microsoft Word and present the selected rules table for editing. Don’t forget to SAVE your changes if you want the edited rules table to take effect.

Free Download of the 1-Click Indexer

Loading

Toronto and Mississauga, Monday, August 22, 2011 10:18 AM

Copyright © 1996-2011 Chris Greaves. All Rights Reserved.