PLEASE READ CAREFULLY

A major change in version 0.2.8 is the handling of tab characters (\t, #09). 
The Tab Width setting is a user preference, but tab characters on disk (or on 
the Windows clipboard) should adhere to the de facto standard (of 8). Edita 
now performs proper conversion on file load and save (and cut/paste), unlike 
previous versions, which stored tab characters incorrectly. The remainder of
this text explains a hopefully reasonable solution to this "legacy error".

Legacy tab character handling uses a simple cut-off date and time method: files
saved before this are assumed to contain tabs stored in a non-standard fashion. 
This should be correct for the majority of files stored by a previous version 
of Edita. Note however that some files which pre-date the cut-off, such as 
C:\Euphoria\include\database.e, but were never actually saved by Edita, are 
likely to load incorrectly. Such files were being loaded incorrectly by versions 
<=0.2.7, with this option checked they may still load incorrectly albeit in a 
slightly different way, by default, see next. If no prior version of Edita has 
been installed on this machine, you should just disable (uncheck) legacy tab 
character handling. Note that if the 'Replace tabs with spaces' option has 
always been checked, the problem with older files is lessened, but they may
still contain incorrectly stored tab characters within comments. I have also
found that some other popular editors (eg Crimson, Code Genie) can also store
tabs incorrectly so they do not open correctly in Notepad, Wordpad, etc.
AFAIK, most Linux editors adhere to the tab-8 standard.

The ReOpen option (Ctrl CSM or right click on a file tab) allows explicit 
choice of tab handling on individual files, provided that Tab Width!=8. 
Open as tab 8 is the new/proper handling, as tab 4[eg] is legacy handling.
When using ReOpen to correct mangled tabs, if legacy tab handling is enabled,
then "as tab 8" is normally the one wanted, if it is disabled, normally use 
the other one. If in doubt, try both, and pick whichever looks best to you.
To prevent this happening on a particular file again, once you are happy with
the way the file has been loaded, perform any null edit such as X <backspace> 
followed by Ctrl S.

Once all, or at least most files on your system are properly stored in tab-8 
format, ie the indentation looks the same when opened in a different editor, 
legacy tab handling should be disabled. Unfortunately there is no better tool
for judging whether a file has previously been wrongly stored in (say) tab-4
than a pair of human eyes. In fact two humans might often disagree over the
way some text should appear, so no program looking at bytes can be right in 
both their eyes. However, there is a counter on the (new) ReOpen pop-up to 
guide you a little bit. It will of course not include possibly hundreds of 
files on your system not opened in this edit session.

The Tools/Re-Indent option can also be used to correct mangled whitespace 
and indentation, but it is quite likely to leave some comments affected, 
especially any comments that contain tab characters.

Any affected program should continue to run as before, except perhaps for a 
few exceptionally rare cases (eg assuming that \t should be converted to 4
spaces, or that line[3] is the first non-blank) which could also have been 
triggered by using any other editor such as Crimson/Code genie/Notepad, etc.

This change is necessary to allow Edita to be used on open source projects 
and otherwise share source code between users and their different editors.

If you delete ltchelp.txt, the Help buttons on Options/Edit and ReOpen should
disappear, ie this is not a mandatory file, and in fact I plan to discontinue
shipping it in maybe 6 months or so.
