File Compare Utility Release Notes
----------------------------------


Build 1.00.006
--------------

1.	This release corrects several minor but annoying problems with inserting
	and deleting lines in the editor.
	
Build 1.00.008
--------------

1.	Trying to compare two files when either or both of them starts with a
	blank line no longer causes a General Protection fault.
	
2.	The last line of a file that doesn't end in a new-line character no
	longer looks funny. FCOMPARE now adds a \r\n sequence to such a file
	because the Microsoft compiler (at least) expects that, as do many
	editors based on Windows edit controls.
	
3.	FCOMPARE now uses long filenames when running under Windows 95.

4.	The comparison algorithm has been improved to better handle files that
	are badly mismatched.
	
5.	The capacity of the directory window has been increased, as has the
	line-count capacity of the editor. The file-size capacity of the editor has
	always been essentially unlimited and remains so.
	
6.	When running under Windows NT version 3.5, the Register choice will now
	be grayed to indicate that it isn't possible to complete registration in
	that environment. Please consult the online help for a method of recording
	registration information after booting MS-DOS instead of NT.
	
Build 1.00.009
--------------

1.	This release corrects many problems introduced by the Windows 95 long
	name support in release 008:
	
	a.	File dates and times appear correctly under Windows 3.x once again.
    
	b.	Directories will no longer appear in the lists of files in the main dialog.
		Consequently, you'll no longer get a GP fault if you try to edit one.

	c.	File name comparisons in the two directory panes are now case insensitive.
	
	d.	File saving and copying work with files having long names. Previously, you
		could only navigate and compare using long names.

2.	Everybody's favorite change: the About box no longer appears when you
	start a registered copy.
	
3.	Everybody's second favorite change: you can now edit any two files in
	the side-by-side difference format. Choose "Compare" from the system menu
    and enter the names of the two files you want to compare.
	
4.	White space no longer affects the parsing of file types.
	
5.	Inserting a character at the beginning of a line no longer crashes the
	editor.
	
6.	Copying just part of a single line to the clipboard now works correctly.

7.	"Merging" a block of deleted lines (with the Copy Source or Copy Master
	commands) now works correctly.


Build 1.10.010
--------------

1.	Characters you type once again correctly replace the current selection
	instead of causing a fault.

2.	A Preferences dialog now lets you control the treatment of white space
	in the comparison of lines. You can elect (a) to ignore all white space,
	(b) to ignore white space at the beginning and end of lines, or (c) to treat
	all white space as significant. The default is (b), which prevents mere
	indenting changes from showing up as differences. Choose (a) to prevent
	changes in tab settings from showing up as differences. Previously, the
	behavior described by (b) was always in effect.

3.	Double-clicking a filename in a Browse dialog attached to the Compare
	dialog no longer generates a spurious complaint about memory being
	insufficient for the operation.
	

Build 1.10.011
--------------

1.	The preferences dialog now allows you to add, delete, and edit the file
	type filters that appear in the File(s) and Files of Type controls on the
	main dialog.
		

Build 1.10.012
--------------

1.	The preferences dialog now allows you to select whether files in the main
	display of directories will be considered different if (a) their dates,
	times, or sizes are different or (b) their sizes or contents are different.
	Option (a) corresponds to the current behavior, whereby two files will
	appear different in the side-by-side directory display even if the only
	difference is in their timestamps. Option (b) treats files different only
	if they have different sizes or if a binary compare makes them different.
	Choose the new option (b) if you suspect you're dealing with a directory
	in which only timestamps have actually been changed.
	