F       The HTML versions of this document has, of course, been producedD       using AscToHTM itself, no post-processing has been done to theI       HTML pages produced.  The contents list, the navigation bar and all F       the hyperlinks have been generated from a single source documentO       A2HDOCO.TXT (approaching 5,000 lines and *still* growing) and a few small E       configuration files.  See section 6.1 of this document to see a (       list of the actual files involved.  G       Any RTF version has been generated by the new text-to-RTF program D       (name yet to be chosen) which uses the same analysis engine as       AscToHTM.   G       This document describes AscToHTM V3.0, which will be available in L       early August 1998, and which will introduce a re-vamped user interface(       in the Windows version (see 4.1.2)   1     Introduction ------------------  G       AscToHTM is an ASCII to HTML conversion tool.  It has, of course, B       been used to generate the HTML version of this document fromM       the text file A2HDOCO.TXT (see 6.1 for more details).  The HTML version J       of this document is presented "as is".  That is, *no post-productionH       of the HTML has occurred*.  This should give you a flavour of what       AscToHTM is capable of.   C       AscToHTM is made available for download via the Internet from        [download location].  " 1.1   AscToHTM's design objectives         -	Intelligent analysis.   L       	AscToHTM is designed to analyse a document to determine its structureL       	and layout.  This analysis allows AscToHTM to decide how best to markF       	up the HTML so as to accurately represent the author's original       	meaning.   @       	It also helps AscToHTM to reduce errors by allowing it toN       	spot anomalies in the document source.  This is important in minimising8         the amount of any post-production work required.         -	Human-readable HTML   I       	AscToHTM tries to create HTML that can be easily read and modified E       	in an editor.  This is useful if corrections are necessary, or '       	further development is required.          	For example AscToHTM   =       	a) produces short (usually <80 character) output lines   G         b) attempts to indent the HTML to match the output indentation.   B       	c) adds comments to the HTML to indicate include files etc.  I       	d) uses <BLOCKQUOTE> tags for indentation, rather than placing the 1            whole file in <TABLE>...</TABLE> tags.          - Simple user input   K       	Inevitably users have supply additional information to tell AscToHTM J       	where its analysis has gone wrong and to add additional informationG       	such as a document title etc.  AscToHTM offers a large number of D         options (also known as "policies") that the user can modify.  <         Broadly speaking, these policies fall into two camps  V       	- Analysis policies (see 6.2).  These policies affect the way AscToHTM analysesI           your file, and can be used to disabled searches for things like G           bullets, or to specify whether or not underlined headings are            to be expected.   P         - Output policies (see 6.3).  These policies influence the types of HTMLL           markup that are produced.  They also allow you add colour, headersA           footers, background images and much more to your pages.   H         AscToHTM can save your policies to a file, so that next time youI         run it you can load this information back from the "policy" file.   4         Policies are described fully in [section 6].  I         You can further refine the conversion by placing special lines in D         your source file.  These are known as pre-processor commands         (see [section 7]).  K       	To help users formulate and modify their document's policy, AscToHTM H 	can be made to create an output policy file (see 4.2.2.5 and 6.3.3.11);F         Users can then simply edit this file and feed it back into theH         conversion process.  A summary of the recognised policy lines is         given in the [PolDict].      1.2   Expected uses of AscToHTM   +       - Migration of "legacy" text to HTML.   G         Large amounts of unconverted text exist.  As people plan to put M       	this information on the Web, conversion to HTML will become necessary.   L       	This can be a tedious and time-consuming task.  AscToHTM will do much       	of the work for you.   B       	AscToHTM is priced to be worth an hour of two of your time.(       	Check [Reg location] for details.  N       	This means that the "pay back" time is negligible (we only mention thisI       	in case you have bean-counters to convince :).  If you don't think D         AscToHTM will save you hours, then by all means don't by it.  3       - Facilitate mastering of HTML pages in ASCII   M       	The HTML created by AscToHTM may not be as pretty or as clever as that -       	generated by a full blown HTML editor.   
       	But...   H       	It'll be easier to write, edit and spell-check, and it may have a% 	hyperlinked contents list generated.          - Automated conversions   I         AscToHTM can be used to automatically convert text documents that G         you receive.  For this we usually recommend the console version B         which is better suited for calling from within batch jobs.     1.3   Other uses of AscToHTM         - Convert Word documents  F       	AscToHTM was never intended to handle Word documents.  We fullyD       	expect HTML export and import filters to appear (they have inE       	Word '97), and we would advise anyone whose master document is ?       	in Word to search out these filters and give them a try.   D       	That said... a lot of people seem unhappy with what's alreadyJ         available, and AscToHTM does a reasonable job if you save the fileM       	as text with line breaks, though obviously tables and figures will get C       	lost (in the case of tables, because Word throws them away).   G       	The main problem is that Word produces lousy looking text.  This 6       	is one area where AscToHTM does a little better&         than "garbage in, garbage out"  ,       - Pre-process text for import to Word.  8       	(This is a bit cheeky, but possibly worth a try).  G       	Use AscToHTM to convert text to HTML, then import this into your J       	word processing package.  We haven't tried this, but we're guessingC       	that this will give better results than importing from text.   >       	That's because AscToHTM's analysis engine is *smarter*.  E 	NOTE: In the near future the author plans to use the analysis engine N               to generate a text-to-RTF convertor more suited to this purpose.  %       - Pre-process text for printing   E       	Use AscToHTM to convert text to HTML, then print the file from G       	within Netscape or whatever.  The result is a much nicer looking #       	document with fonts'n'stuff.   0       - Add hyperlinks to fairly ordinary pages.  H         AscToHTM has a "link dictionary" feature that can be used to add5         hyperlinks to any word or phrase (see 6.3.8).   D       	This can greatly enhance an otherwise dull set of text pages.     2     Installation ------------------  F       The shareware version of AscToHTM is made available over the webG       from [Download location].  Once you register you can download the J       full version (no nags, no limits), and are entitled to free upgradesJ       for an arbitrary (equals "my decision is final") period of time.  SoM       far I've never requested payment for any updates, which currently occur        roughly every 2 months.   H       Installation will vary according to the type of install kit you'veC       downloaded, but in each case you first download the .ZIP file +       appropriate to your system and unzip.      2.1   VMS installation         Unzip the files.  7       If you've taken an executable version, that's it.   J       If you've taken an object library version, execute the build command       file.   F       You might want to define a foreign command to get better use out       of the program.   '       Have a cup of coffee and relax :)      2.2   Windows installation  ?       The current version of the software makes updates to your B       Registry.  See the Install notes that come with the software6       for a description of the registry settings used.  I       The Windows version requires the following .DLLs to be installed on        your machine         		MFC42.DLL        		MSVCRT.DLL       		MSVCIRT.DLL   L       You may well already have these.  If not, you can use an InstallShield:       download kit that includes them. Failing that, visit  -       		http://babeard.simplenet.com/dll.html   1       to pick up the .DLL files that are missing.      2.2.1   InstallShield version   O       If you've taken an installshield version, unzip the file and then run the I       Setup program.  This will move the files to a directory, and create        all icons etc.  D       Note:	The program is written in C++ and will therefore require=       		that you have the correct run-time libraries for your D       		system installed (see 2.2 above).  The installshield program8       		will detect this and install the necessary .DLLs  H       Once installed, InstallShield will also offer an uninstall option.B       You can access this via Control Panel | Add/remove software.  F       The InstallShield version is substantially larger (around 1.5Mb)J       than the manual install versions.  This means some people experience$       problems downloading the file.  N       For this reason smaller kits without the .DLLs and without InstallShieldK       are available.  This reduces the download size by a factor of 2 and 6        respectively.      2.2.2 Simple .ZIP file version  D       This version should be used by anyone who anticipates problemsE       with the InstallShield version, or who simply wishes to upgrade        an existing version.  J       It's about 6 times smaller than the InstallShield version with .DLLs       in it.  L       Once you've unzipped the files, move them to your preferred directory.  P       There will be no uninstall command in this case (unless you are overlaying$       an earlier installed version).     2.2.3 Console application   K       Originally AscToHTM was only available as a console application.  Now I       it is available as a fully-windowed application.  Consequently this )       version is not so widely available.   M       The console version will be made available to registered users who wish O       it, as it is more suited for automated conversions inside batch jobs etc.   J       The conversion engine is identical in each case, it's just GUI-less.  M       Please note, this is *not* the same as any DOS version that we produce, +       and will require a Win32 environment.   H       Note:  It's likely that future versions of AscToHTM will merge theL              console and Windowed interfaces into a single program, at which=              point the console version will become redundant.      3     How AscToHTM works ------------------------   3.1   The big assumption  *       AscToHTM makes one big assumption :-  ?       		Each text file has been laid out in a consistent manner D       		by its author in a way that makes it easy for a human reader       		to understand.  H       Given this, AscToHTM tries to read the text file and mark it up inJ       HTML accordingly.  This is achieved by making two passes through theH       document, an analysis pass (see 3.2) and an output pass (see 3.3).  8       Note:     Sadly this assumption is not always true     3.2   The analysis pass   K       During the analysis pass AscToHTM gathers together all the statistics D       that it needs to analyse how the author has laid out the file.  I       For example, the distribution of line indentations and line lengths I       is observed, together with the number and types of bullets, section '       headings and lots of other stuff.   J       Once this has been done, the program uses this data to determine howJ       the author has structured the document.  For example are the sectionL       headings underlined, capitalised or numbered?  If numbered, what styleK       of numbering is used, and at what level of indentation is the heading 
       placed?   I       This information is then used to set the analysis polices (see 6.2) F       which may then be overridden by the user, or by loading a policy!       file with different values.      3.3   The output pass   %       During the output pass AscToHTM   A       - Generates HTML (there's nothing like stating the obvious) ?       - (optionally) creates a suite of inter-linked HTML pages .       - (optionally) generates a contents list/       - (optionally) generates a directory page      3.3.1 Generating HTML   N       The HTML generated depends only on the original document, the calculated6       document policy, and any user policies supplied.  ?       [Section 5] describes the markup produced in more detail.       3.3.2 Generating a contents list  I       AscToHTM can detect the presence of a contents list in the original A       document.  Alternatively you can choose (see 6.3.4) to have E       AscToHTM to generate a contents list for you, in which case any =       original list is omitted from the output HTML document.   L       Regardless of whether the original or generated contents list is used,I       AscToHTM will turn the contents list into hyperlinks that will take 0       you to the correct HTML file and location.  L       There is a fuller discussion of contents lists in 5.6.2.  The policiesI       that influence contents list production are listed in 6.3.4, whilst 8       the pre-processor commands are described in 7.1.3.    1 3.3.3 Splitting the document into many HTML pages   M       By default AscToHTM creates a single .HTML file.  However, through file B       organisation document policies (see 6.3.3) it is possible to  O       a) Split the document into a number of smaller .HTML files (see 6.3.3.8).   J       b) Insert standard JavaScript into the <HEAD> ... </HEAD> section of           each page (see 6.3.1.6)  L       c) Add a HTML "header" to the top of each generated file (see 6.3.1.7)  H       d) Add a navigation bar at the foot of each page with links to theG          Next/Previous .HTML page and the contents list (see 6.3.3.10).   L       e) Add a HTML "footer" to the end of each generated page (see 6.3.1.8)     4     Running AscToHTM ----------------------   4.1   Windows version    4.1.1 Launching the program    4.1.1.1 Normal activation   J       Just run the program as you would any other Windows program, i.e. by<       clicking on it's icon, or launching it the Start menu.    % 4.1.1.2 Execution from a command line   %       From a DOS command you can type          	C:> AscToHTM          or  (         C:> AscToHTM <file1> <file2> ...  =       In the first case, AscToHTM will be launched as normal.   K       In the second case AscToHTM will convert the specified files, briefly F       displaying a status window, and then exiting.  In this case, one3       of the named files can be a .pol policy file.   E       NOTE:	There is also a console version of AscToHTM that can only O                 run from the DOS prompt.  This version has a slightly different L                 command syntax, and in particular is better suited for batch$                 processing (see 4.2)  ;       		Later versions of AscToHTM will probably merge the  *       		functionality of the two versions.     4.1.1.3 Drag'n'Drop execution   H       Create an Icon for AscToHTM, and simple drag'n'drop files onto it.F       The results will be identical to those obtained by typing in the(       filenames as described in 4.1.1.2.  D       One useful suggestion is to add AscToHTM to your "SendTo" menu-       (shown when you right-click on a file).   1       See the Windows help file for more details.     ! 4.1.2 Using the Windows Interface          *Section added in V3.0*   I       The Windows interface has been re-vamped in V3.0.  The main changes 	       are   E       	- Introduction of a Windows Menu to replace the old button bar "       	- More options on this menuJ       	- The policy property sheets no longer have to be closed when doing           a conversion.o    * 4.1.2.1 Doing a straightforward conversion         *Section added in V3.0*   I       To do a simple conversion, simply enter the name of the file to be  N       converted or use the "Browse" button to locate the file to be converted.  .       Then press the "Convert file(s)" button.  M       A status screen will be displayed whilst the conversion is in progress.oK       For small files this may flash up so fast you can't actually read it.hM       (If you want to see what it said go to the View...Messages menu option)c  L       To view the HTML, press the "View results" button.  This should launchH       your preferred HTML viewer to display the newly created HTML page.     4.1.2.2 The File menu          *New in V3.0*-  .       The File menu has the following options:         - *Convert*I  K       	Initiates the conversion.  If you already have a file selected, thisnM         file will be converted.  If you don't, then a browse window will opene0       	allowing you to choose a file to convert.  G       	This option is identical to pressing the "Convert files" button.o           - *Exit*         	Exits the program    # 4.1.2.3 The Conversion options menua         *New in V3.0*i  J       AscToHTM offers the advanced user a large number of program options.K       These are called policies, and may be saved in policy files for lateraH       re-use.  Policy files are described in detail in Chapter 6 of this       document.o  +       Policies broadly come in two sorts.  T  M       Analysis policies represent a description of what the source file does  G       and does not contain.  These policies are usually set to default nG       values and/or calculated by analysing the source document.  They  C       should only ever need to be manually adjusted if you wish to d@       correct the analysis, or override the detection of certain       typographical features.i  I       Output policies represent styling and other options that cannot be rJ       inferred from the source document.  These include styling and markupG       options, and allow the user to "add value" to the HTML generated.o  9       The Conversion Options menu has the following itemsc          - *Edit analysis policies*  O       	This option allows you to edit the programs analysis policies (see 6.2).tO       	This opens a tabbed property sheet with the various policy values shown.iL       	These values will change each time a document is converted to reflectO       	the results of analysing the document.  Policies that have been manuallyl=       	set (or loaded from file) will not change in this way.f  O       	You should only need to change these if you suspect AscToHTM has wronglyn!       	analysed your source file.g  K       	The analysis policies are listed in 11.1 and described fully in 6.2.T           - *Edit output policies*  M       	This option allows you to edit the programs output policies (see 6.3).lO       	This opens a tabbed property sheet with the various policy values shown.   D       	For the most part these values will *not* change each time a        	document is converted.   N       	You can use these policies to tailor the document conversion to produce;       	HTML files as near as possible to how you like them.p  I       	The output policies are listed in 11.2 and described fully in 6.3.e           - *Re-analyse the file*h  K       	This option forces AscToHTM to re-analyse the current source file tof,       	(re-)calculate the analysis policies.           - *Reset to defaults*g  M       	This option forces all policies back to their AscToHTM defaults.  ThisoN       	will negate the effect of any manually set policies, or policies loaded       	from a policy file.    !       - *Load policies from file*t  K       	This option allows you to load a set of policies previously saved toiN       	a policy file.  This allows a conversion to be repeatedly done the sameE       	way, or a set of conversions to be done the same way (see 6.4)   G       	Note, you can set a policy file to be used by default see 4.1.3.          - *Save policies to file*t  N       	This option allows you to save your current set of policies to a policyK       	file for later re-use.  It is recommended that only a partial set of-M       	policies (i.e. any loaded policies and manually set policies) be savedAN         to allow the program maximum flexibility when converting future files.  4       	See section 6.4 and the discussion in 6.4.2.1     4.1.2.4 The Settings menul         *New in V3.0*i         - *Edit*  H       	This option opens up a dialog to allow you to change the program        	settings (see 4.1.3).     4.1.2.5 The View menui         *New in V3.0*L         - *Messages*  M       	This option allows you to re-view the Messages window displayed during I       	file conversion.  On small files this window can sometime be shownl(       	too briefly to view the messages.           - *Last conversion*d       G       	This option will launch the preferred browser for the last file cK       	converted.  If a wildcard conversion was done, the last file in the .I       	group will be shown.  This option has the same effect as the "Viewe       	results" button.      4.1.2.6 The Help menu          *New in V3.0*M         - *Contents*  I       	This option brings up the Windows help file.  This offers a lot of G       	context-sensitive help which can usually be accessed by pressingv,       	F1 or "Help" anywhere in the program.  L       	Over time the Windows Help file has adopted a secondary role compared!       	to the HTML documentation.d         - *HTML doco (offline)*w  J       	This option launches the copy of the HTML documentation on your ownL       	computer inside the preferred browser.  Each installation of AscToHTMI       	comes complete with HTML documentation.  Should you decide to move H       	this documentation, you'll need to alter the settings (see 4.1.3)           - *HTML doco (online)*  L       	This option launches the *online* copy of the HTML documentation fromO       	the Web.  As such you will need to be online for this to work.  Normally H       	this documentation will be identical to that held locally on yourF       	own computer.  However, should you wish to look for updates or D         download a fresh version of the documentation you can do so.  ?       	Currently this is http://www.yrl.co.uk/~jaf/doCo/A2H.HTMa           - *Register (online)*T  L         In the shareware version of AscToHTM this will launch your preferredO       	browser to take you to a web site which gives details of how to register-       	your copy of AscToHTM.   C       	Currently this is http://www.yrl.co.uk/~jaf/a2hregisTer.html            - *About*o  I       	This option launches the About screen. This gives program version nL       	information, shows your registration status, and provides a couple ofB       	buttons to access the home page and other pages on the Web.     4.1.3 Program settings         *Section added in V3.0*   K       This Dialog allows you to set a few program settings.  These settingsnI       allow you to customize the program's behaviour to a limited extend.i         Setting include:-r         - *Default policy file*   J       	This is the name of any policy file to be used as default each timeM       	the program is run.  This is not normally desirable, but if you alwaysnJ       	use the same policy file, this will save you having to load it each        	time you run the program.    )       - *Browser command to view results*n  K       	This is the browser command used to view the HTML files created.  BynH       	default AscToHTM should detect the browser that is configured forK       	your machine, but should you wish to check your results look okay in 2       	some other browser, you can change it here.    (       - *Location of HTML documentation*  J       	This is the location of the HTML documentation on your machine.  ByM       	default this is installed in the same directory as the program itself.eO       	However, should you wish to move these file, you can adjust this settingnA       	so that the Help menu option can still locate these files.S            - *Drag'n'drop properties*  H       	These settings govern the behaviour of the program when files areF       	dragged onto the program's icon.  The options include switchingL       	off the Messages display during conversion, and automatically viewingL       	the results of the conversion in the preferred browser on completion.    * 4.2   VMS and console application versions  M       The VMS version and windows console version behave identically in termsc(       of their use of command arguments.     4.2.1 Command line arguments  ,       The command line should be of the form  @             	AscToHTM <filespec> [<policy_file>] [</qualifiers>]         Wheret  ;       	Filespec	Any valid file specification for the system	3       			you're using.  As of V2.3 this can includei       			wildcards.h  7       			In the Windows version, this can also be spacem!       			separated lists of filess    E       	Policy_file	The name of any policy file (see [Section 6]) you s;       			want to use for the conversion.  Policy files are i?       			recognised by having a .pol file extension.  For this /6       			reason you cannot convert .pol files to HTML.  F       	Qualifiers	Extra commands that may be passed in via the command?       			line.  In most cases these are equivalent to policies,t<       			they're just made available on the command line for       			your convenience.  	       			v 4.2.2 Command line qualifiersl  F       Certain aspects of AscToHTM's behaviour can be changed by addingJ       qualifiers to the command line.  Qualifiers begin with the slash (/)J       character and should be entirely upper or lower case, i.e. they must3       not be mixed case, and must not be shortened.o     4.2.2.1 The /CONTENTS qualifieri  F       This has exactly the same effect as the add contents policy line       described in 6.3.4.1     4.2.2.2 The /DEBUG qualifier  M       This qualifier causes AscToHTM to generate some diagnostic files, whichr       have extensions   .       	.LIS1		an analysis before policy is set,       	.LIS		an analysis after policy is set  !         .STATS		a statistics files  K       These files are neither pretty, nor easy to read, but they can assiste7       diagnosing faults should you wish to report them.a     4.2.2.3 The /DOS qualifier  M       This has exactly the same effect as the "use DOS filenames" policy lines       described in 6.3.3.5.n     4.2.2.4 The /SIMPLE qualifieri  J       This has exactly the same effect as the "Keep it simple" policy line       described in 6.2.1.10      4.2.2.5 The /POLICY qualifiert  N       This has exactly the same effect as the "Output Policy file" policy line       described in 6.3.3.11e     4.2.2.6 The /INDEX qualifier  J       This has exactly the same effect as the "Make Directory" policy line       described in 6.3.9.1    $ 4.3   Getting the most from AscToHTM   4.3.1 Making your first attempto   4.3.1.1 From the command linea  !       To run AscToHTM simply typeo          		AscToHTM Input_file.name         at the command line.          This will create a file :-         - input_file.HTMLs  E       	An output file which will have the same file name with a .HTMLr         extensionh  D       The program may display a number of status messages indicatingL       source lines that it rejects because they "fail policy".  Source linesH       that fail policy are usually simply copied to the output file withG       no markup applied.  These messages are largely informational, and H       can be ignored if the conversion worked okay.  If it didn't, theseC       messages may give a clue as to where the analysis went wrong.o     4.3.1.2 From Windows  K       Enter the name of the file to be converted in the text field.  If you I       wish, use the browse button to search for the file to be converted.h  K       Once you've chosen the file, the output filename and input and output G       directories are inferred from the filename.  If you wish, you mayy-       edit the output filename and directory.e  L       Press the *Convert* button.  The Messages window will briefly display.O       If you wish to view these messages later, press the Show Messages button.n  M       To view the last file converted, press the *View results* button.  This K       should launch your default browser for the file types (.htm or .html)aL       just created.  If you get the message "cannot detect default browser",O       use the *Settings* menu to set up the path to the browser you wish to uset       and try again.     4.3.2 Refining your results   I       If all goes well the resultant HTML will be satisfactory and all inoN       one file.  You can change all that by creating your own document policy.  F       In the Windows version, this is done by editing policies via theI       *Options* button, which is fully described in the context-sensitiver0       Windows Help file (press F1 at any point).  N       However, in all versions the policies can be saved to a text policy fileK       and it is the format of that file that is shown and discussed in thisi       document.p     4.3.2.1 Using a policy filed  M       If your initial results are a little strange, then re-issue the commandw  (       		AscToHTM Input_file.name /policy  J       This time in addition to the .HTML file, you will now have an outputK       policy file "input_file.POL" which describes the document policy filetL       calculated by AscToHTM (see 3.2) and used by it during the conversion.  K       Review the contents of this file, looking for any policies that don'tiL       look right.  Create a new .POL file containing only those policies you<       think are wrong, and edit them to have correct values.  3       You'll need to review [Section 6] to do this.c  A       Once you've produced your new input policy file, re-run the)"       conversion using the command  7       		AscToHTM Input_file.name Input_policy_file.name.  M       The program will now override aspects of the calculated document policy.,       with the input policy you've supplied.  F       Each document policy file consists of a number of lines of data.       Each line has the form  '       		Keywords     :    Data value(s)n  K       For clarity a number of section headers are added.  These are ignored-M       in the input policy, as are any lines whose keywords are not recognised        or not yet supported.u  D       A sample fragment from a calculate policy file looks like this           		[Hyperlinks]       		------------,                 Create hyperlinks        Yes$       		Create mailto links      Yes$       		Create NEWS links        Yes       		         		[Added HTML]       		------------.       	        Document Title           (none)         		I       These are all default values used by AscToHTM.  If, for example yourH       want to add a title to your page and prevent email addresses beingH       turned into hyperlinks, simply create a policy file containing the       lines            		[Hyperlinks]       		------------#       		Create mailto links      No.       		         		[Added HTML]       		------------=       		Document Title           Title text for the HTML page     6       (The insertion of section headings is optional).  F       By refining the input policy file, you can greatly influence the$       output that AscToHTM generates     4.3.2.2 Using a link dictionaryA  E       In addition to adding hyperlinks for all URLs, email addresses, I       section references and contents list entries, AscToHTM allows usersiC       to specify key phrases that should be turned into hyperlinks."  F       This is achieved by adding lines to the input policy of the form           [Link Dictionary]e       -----------------nJ       Link definition    :   "[AV]" = "AltaVista" + "Using_AltaVista.html"           The syntax used here is     K       Link definition    :   "match phrase" = "replacement phrase" + "link"o    C       In this case the string "[AV]" is replaced by a link to a web-N       page "Using_AltaVista.html" with the text "AltaVista" being highlighted.  D       The link dictionary used for this documentation can be seen in       the file A2HLINKS.DAT.    # 4.3.2.3 Using multiple policy files   H       If you wish to use AscToHTM to support several text files e.g. forL       a set of Intranet documentation, it may be useful to share some commonJ       document policies, e.g. colour, headers and footers and particularly       the link dictionary.  F       To support this AscToHTM allows two special types of line in the       policy file.         a) Include files  1       		include file      :   Link_Dictionary.dat   F       	If a line of this type is encountered, the contents of the fileI       	Link_dictionary.dat are included in the current policy file.  This C       	is the best way of sharing data across many converted files.n         b) "daisy-chain" files  3       		switch to file    :   Other_policy_file.date  C       	If a line of this type is encountered, the processing of the @       	current file terminates, and continues in the named file.  D       	This is a way of "daisy-chaining" policy files together whichM       	may be useful if you wish to group files together at different levels.o    % 4.3.2.4 Creating DOS-compatible files0  F       Occasionally it may be necessary to create files consistent withN       the DOS nnnnnnnn.nnn naming convention.  This can happen when working onM       a DOS or windows 3.n machine, or via a network that has this limitation        e.g. Pathworks.   J       AscToHTM supports this.  There are two ways to achieve this.  Either       use the commandh  )       		AscToHTM   input_file.name   /DOSa  )       Alternatively, simply add the linest           		[File generation]t       		-----------------d#       		Use DOS filenames       Yesv#       		DOS filename root       A2Hu    H       to your policy file.  AscToHTM will then create a base file called       (in this case) A2H.HTM.   L       If you're splitting a large document into many files, subsequent files       have the form   ,       		<filename_root>_<section number>.HTM  N       When this name becomes two long, AscToHTM will create a name of the form         		AAANNNNN.HTM  M       Where AAA comes from the file root, and NNNNN is a 5-digit code derivedi%       from the rest of the file name.s    ( 4.3.3   Processing several files at once   4.3.3.1 Using wildcards   I       You can convert multiple files at one time by specifying a wildcardtN       describing the files to be converted.  The wildcard has to be meaningfulD       to the operating system you are using, and will be expanded in       alphabetical order.s  J       At present we recommend that wildcards are only used on the contents       of a single directory.  N       Note, the same policies will apply to all files being converted.  If youQ       wish different policies to apply, use a steering command file (see 4.3.3.2)o  F       Note:	In the shareware version, wildcard conversions are limited       		to only 5 filest    % 4.3.3.2 Using a steering command fileF  N       In console version you can convert several files at the same time in theD       order and manner of your choosing.  To do this use the command  - 		AscToHTM  @List.file [rest of command line]   L       Where the file "list.file" is a steering file which contains a list ofI       AscToHTM command, and the "@" in front indicates it is a list file, )       rather than a file to be converted.e  *       An example list file might look like  
 $_$_BEGIN_PREs 		! this is the main documentt 		DOCO.TXT   	IN_DOCO.POL /DOS 		#r  		# These are the other chapters 		CHAPTER2.TXT 		CHAPTER3.TXT	/SIMPLE $_$_END_PRE     H       Note the use of "!" or "#" at the start of a line signifies it's a!       comment line to be ignored.e  G       Any qualifiers used on the original AscToHTM line will be used asvK       defaults for each conversion, but will be overridden by any listed in K       the list file.  In this way it would be possible to specify a default45       policy file for a bunch of similar conversions.   C       Note:	In the shareware version, batch conversions are limitedi       		to only 5 filesv     4.4   Other tips and tricks   
 4.4.1 Generalf  K       -	If you can, try to use as much white space as possible, e.g. beforelC        	paragraphs and new sections and at the end of the document.   L       	This makes it easier for AscToHTM to place things in context, reducesK       	ambiguity and increases the chances of correct HTML being generated.n  L       - Ensure you have consistency in your use of indentation, bullets etc.  G       	On the output pass AscToHTM rejects lines that "fail policy", so.D       	any inconsistencies are liable to lead to errors in the HTML.  J       - Try to avoid lines that may confuse AscToHTM.  For example numbersE       	at the start of a line of text may be interpreted as a sectioniE       	heading.  If the number is out of sequence, or at an incorrectsL       	indentation this will "fail policy".  However, it may cause confusion-       	and is best avoided wherever possible.d  D       	Where a number has to be at the start of a line, try using anG       	indentation level that doesn't match that used by your headings.t   4.4.2 Link dictionaryp  C       -	Try to avoid using match words that are substrings of otheri         match words.  B       	If you can't avoid this, then list the longer entries first  I       -	Try to ensure you match words will only match the places you want        	them to match.   4       	This means avoiding overly short match words.  I       -	If you can bracket your match words or phrases [like this].  ThiswI       	makes for less mistakes, and makes it clearer in the original thato.       	you expect a link adding at that point.     4.4.3 Contents List detection   I       Contents list detection is tricky at the best of times.  It becomes        even trickier if         a) There isn't one  <       b) The list only contains chapters and no sub-sections  L       If the program wrongly determines that there is/isn't a contents list,#       use the following policy linen  !       		Expect Contents List : No   D       to tell AscToHTM how it has gone wrong.  The usual error is to8       decide there is a contents list where none exists.    & 4.4.4 Using "Send to" in Windows 95/NT  I       Although AscToHTM is currently a console program, it can be invoked.3       (without policy file) from windows as followsn  <       	- Drag and drop you text file onto the AscToHTM icon.  D       	- Create a shortcut in your "SendTo" folder in Windows.  ThisF       	  is under C:/WINDOWS or C:/WINNT/PROFILES/<USERNAME> dependingL       	  which system you're using.  Once this has been done, right-clickingH       	  on a file in explorer brings up the "Send to" menu, and you can9           now "send" your text file to AscToHTM directly.t  H       Better still, create a .BAT file to invoke AscToHTM with a defaultO       policy file - e.g. with your favourite colour scheme (6.3.1.10), and some K       standard link definitions (6.3.8) - and add this the "SendTo" folder.gD       In this way you can easily convert text files in any number of       pre-defined manners.     4.4.5 Tables  K       AscToHTM does a reasonable job of detecting and analysing Tables, bute'       the following tips can be useful.m  J       - If the extent of the table is wrongly calculated, mark it up using7         TABLE pre-processor commands described in 7.1.2h  K       - If AscToHTM places a code fragment or diagram in TABLE markup, marksF         the source using CODE or DIAGRAM pre-processor commands (7.1.5         and 7.1.6)  L       - Avoid mixing tabs and spaces.  This makes spotting column alignments!         positions more difficult.   G       - If you want the heading in bold, try drawing a line all the wayr+         across, separating header from datao  G       - If AscToHTM creates too many columns, adjust the "Minimum TABLE.H         column separation" to be greater than 1, and ensure there are atN         least two spaces between columns (see 6.2.4.2 and 7.4).  AlternativelyN         "break formation" by inserting a space at the start of every second or         third line.'  I       - If AscToHTM puts lines in tables when they shouldn't be, increase H         the "Minimum automatic <PRE> size" (see 6.2.4.1) value.  This isF         a common problem in email digests with people's .sigs in them.  J       - If you wish to fine-tune a particular table, use the pre-processor"         commands described in 7.4.     5     HTML markup produced --------------------------   5.1   Text layouto   5.1.1 Indentationi  I       AscToHTM performs statistical analysis on the document to determinegJ       at what character positions indentations occur.  This information isI       used on the output pass to determine the indentation level for eachl       source line.  C       AscToHTM attempts to indent the HTML code to match the output 3       indentation level, to make it easier to read. 9       The indentations themselves will be marked up usingd*       <BLOCKQUOTE> ... </BLOCKQUOTE> tags.     5.1.2 Hanging paragraph indentsn  N       Some documents, especially ones dumped from Word, have hanging paragraphN       indents.  That is, each paragraph starts at an offset to the rest of the       paragraph.  M       AscToHTM struggles heroically with this, and tries not to treat this ascG       text at two indent levels, but it does occasionally get confused.   P       If writing a text file from scratch with AscToHTM in mind, then it is best       to avoid this practice.n     5.1.3   Bullets   =       AscToHTM detects and supports several types of bullets.d   5.1.3.1 Bullet chars  (       Bullet chars are lines of the type  
 $_$_BEGIN_PRE        	- this is a bullet line  #       	- this is a bullet paragraph %       	  because it carries over ontoe       	  more lines. $_$_END_PREE  H       That is, a single character followed by the bullet line.  AscToHTMN       can determine via statistical analysis which character, if any, is beingE       used in this way.  Special attention is paid to the '-' and 'o'h       characters.t  F       Bullets of this type are given a <UL> ... <LI> ... </UL> markup.     5.1.3.2 Numbered bullets  J       AscToHTM can spot numbered bullets.  These can sometimes be confusedF       with section headings in some documents.  This is one area whereG       the use of a document policy really pays dividends in sorting theh       sheep from the goats.   I       Numbered bullets are given a <OL TYPE=1 START=N> ... <LI> ... </OL>.
       markup.u  B       Note:	Not all browsers support this type of markup.  In such?       		cases, it's possible that the numbering of bullets willP=       		get reset to 1 every so often.  However, this isn't ah:       		problem with either Netscape or Internet Explorer.   5.1.3.3 Alphabetic bullets  J       AscToHTM detects upper and lower case alphabetic bullets.  These are3       marked up like numbered bullets, with TYPE=a.n   5.1.3.4 Roman Numeral bullets   M       AscToHTM detects upper and lower case roman numeral bullets.  These areo3       marked up like numbered bullets, with TYPE=a.      5.1.4 Centred text  L       AscToHTM can attempt to spot chunks of centred text.  However, becauseD       this can easily go wrong this option is normally switched off.  K       Centering is only switched on for single isolated lines, or any groupaD       of at least two lines.  <CENTER> ... </CENTER> markup is used.       5.1.5 Definitionsf   5.1.5.1 Definition lines  D       A definition line is a single line that appears to be definingF       something.  Usually this is a line with either a colon (:) or an)       equals sign (=) in it.  For example   
 $_$_BEGIN_PRE "       	IMHO = In my humble opinion  -         Address : Somewhere over the rainbow.  $_$_END_PREh  H       AscToHTM attempts to determine what definition characters are usedE       and whether they are strong (only ever used in a definition) or 1       weak (only sometimes used in a definition).o  L       AscToHTM marks up definition lines by placing a <BR> on the end of theK       line to preserve the original line structure.  Where this decision is <       made incorrectly unexpected breaks can appear in text.  E       AscToHTM offers the option of marking up the definition term in 7       bold.  This is not the default behaviour however.s     5.1.5.2 Definition paragraphsl  D       AscToHTM also recognises the use of definition paragraphs such       as :-I  
 $_$_BEGIN_PREs<       Note:	This is a definition paragraph whereby the whole?       		paragraph is defining the term shown on the first line.n?       		Unfortunately AscToHTM currently only copes with singlee?       		paragraphs (i.e. not with continuation paragraphs), and *       		only with single word definitions. $_$_END_PREo  L       This gets marked up in a <DL> <DT>...</DT> <DD>...</DD> </DL> sequence  <       Note:	This is a "definition" paragraph, i.e. the whole;       		paragraph defines the term shown on the first line.y?       		Unfortunately AscToHTM currently only copes with singlev?       		paragraphs (i.e. not with continuation paragraphs), and *       		only with single word definitions.     5.2   Text formattingn   5.2.1 Quoted lines  C       AscToHTM recognises that, especially in Internet files, it ismJ       increasingly common to quote from other text sources such as e-mail.F       The convention used in such cases is to insert a quote character*       such as > at the start of each line.  H       Consequently, AscToHTM adds a <BR> tag at the end of such lines to2       preserve the line structure of the original.     5.2.2 Emphasis  K       AscToHTM can look for text emphasised by placing asterisks (*) eitherlN       side of it, or underscores (_).  AscToHTM will convert the enclosed text*       to *bold* and _italic_ respectively.  I       The emphasised word or phrase should span no more than a few lines.uH       If the phrase is longer, or if AsctoHTM fails to match opening andB       closing emphasis marks, the characters are left unconverted.  @       Tests are made to ignore double asterisks and underscores.     5.3   Added hyperlinks   5.3.1 Contents List lineso  L       Contents list lines are marked up in bold, and turned into a hyperlinkI       pointing at the section referenced.  The text is sized according tod@       heading type in the range +/- 1 font size from normal (3).     5.3.2 Cross-references  M       AscToHTM can convert cross-references to other sections into hyperlinksmK       to those sections.  Unfortunately this is currently only possible for-O       second, third, fourth... level numeric headings (n.n, n.n.n, n.n.n.n etc)i  O       This is because the error rate becomes too high on single numbers/letters]@       or roman numerals.  This may be refined in later releases.    
 5.3.3 URLs  H       AscToHTM can convert any URLs in the document to hyperlinks.  ThisE       includes http and ftp URLs and any web addresses beginning withi
       www.     5.3.4 Usenet Newsgroupsc  J       AscToHTM can convert any newsgroup names is spots into hyperlinks toK       those newsgroups.  Because this is prone to error, AscToHTM currently	B       only converts newsgroups in known USENET hierarchies such as       rec.gardens by default.   %       This can be overcome either by n  ?       	a) placing "news:" in front of the newsgroup name (e.g. n+       	   news:this.is.a.newsgroup.honest) TE       	b) relaxing this condition via a document policy (see 6.3.2.4)oG       	c) specifying the newsgroup hierarchy as recognised via a policye       	   (see 6.3.2.5)e     5.3.5 E-mail addresses  L       AscToHTM can convert any email addresses into hypertext mailto: links.     5.3.6 User-specified keywordst  M       AscToHTM can convert use-specified keywords into hyperlinks.  The words-H       or phrase to be converted must lie on a single line in the source I       document.  Care should be taken to ensure keywords are unambiguous. L       Normally I mark my keywords in [] brackets if authoring for conversion       by AscToHTMl  F       See the discussions on "link dictionaries" in 4.3.2.2 and 4.4.2.     5.4   Section headings  M       AscToHTM recognises various types of headers.  Where headers are found, N       and deemed to be consistent with the prevailing document policy (correctL       indentation, right type, in numerical sequence etc), AscToHTM will use)       the standard <Hn> ... </Hn> markup.s  K       In addition to this, AscToHTM will insert a named Anchor tag (<A> ... K       </A>) to allow hyperlink jumps to this point.  These anchors are usedlJ       for example in the contents list and cross-reference hyperlinks that       AscToHTM generates.i     5.4.1 Numbered headers  L       This is the preferred heading type and the type that AscToHTM has mostK       success with.  Sections of type N.N.N can be checked for consistency, J       and references to them can be spotted and converted into hyperlinks.  G       At present more exotic numbering schemes using roman numerals andaG       letters of the alphabet are not fully supported.  This is planned =       to be implemented soon, possibly via user policy files.l     5.4.2 Capitalised headersd  F       AscToHTM can treat wholly capitalised lines as headers.  It alsoC       allows for such headers to be spread over more than one line.g     5.4.3 Underlined headers  H       AscToHTM can recognise underlined text, and optionally promote the,       preceding line to be a section header.     5.4.4 Numbered paragraphs   J       Some types of documents use what look like section numbers to number:       paragraphs (e.g. legal documents, or sets of rules).  D       AscToHTM can recognise this, and mark up such lines by placingJ       the number in bold, and not using <Hn> ... </Hn> markup on the whole       line.        5.5   Pre-formatted text   5.5.1 Lines and form feeds  I       Lines are interpreted in context.  If they appear to be underliningoI       text, or part of some pre-formatted structure such as a table, then        they are treated as such.y  H       Otherwise they become horizontal rules (<HR>).  Form feeds or page&       breaks also become <HR> markups.    % 5.5.2 User defined pre-formatted texte  J       AscToHTM normally ignores any HTML markup in the original text.  TheG       sole exceptions are any preprocessor tags which a user may insertc1       into their text document (see [section 7]).s         For example :-  
 $_$_BEGIN_PRE K       The use of BEGIN_PRE and END_PRE preprocessor commands (see 7.1.7) innI       the text documents tells AscToHTM that this portion of the documentdB       has been formatted by the user and should be left unchanged. $_$_END_PRE,    / 5.5.3 Automatically detected pre-formatted text   K       AscToHTM attempts to spot chunks of preformatted text.  This can vary J       from a single line (e.g. a line with a page number on the right-hand*       margin) to a complete table of data.  L       Where such text is detected AscToHTM analyses the section to determine=       what type of pre-formatted text it is.  Options includet         	- Tables        	- Code sampless       	- Ascii Art and diagrams #         - some other formatted textt  I       You can adjust the sensitivity of AscToHTM to pre-formatted text bynM       setting the minimum number of lines required for a pre-formatted region        (see 6.2.4.1).     5.5.3.1 Tables  N       Tables are marked out by their use of white space, and a regular patternJ       of gaps or vertical bars being spotted on each lines.  AscToHTM willN       attempt to spot the table, its columns, its headings, its cell alignment5       and entries that span multiple columns or rows.   K       Should AscToHTM wrongly detect the extent of a table, you can mark upN>       a section of text by using the BEGIN_TABLE ... END_TABLE)       pre-processor commands (see 7.1.2).   L       You can alter the characteristics of all tables via the table policies       (see 6.3.7).  K       You can alter the characteristics of all or individual tables via thei-       table pre-processor commands (see 7.4).p  C       Of you can suppress the whole thing altogether (see 6.3.7.1).      5.5.3.2 Code samples  K       AscToHTM attempts to recognise code fragments in technical documents..H       The code is assumed to be "C++" or "Java"-like, and key indicatorsK       are, for example, the presence of ";" characters on the end of lines.w  K       Should AscToHTM wrongly detect the extent of a code fragment, you cansD       mark up a section of text by using the BEGIN_CODE ... END_CODE)       pre-processor commands (see 7.1.5).r  F       You can choose what type of markup is used for the code fragment       (see 6.3.6.11).O  D       Of you can suppress the whole thing altogether (see 6.2.1.13).     5.5.3.3 Ascii art and diagrams  I       AscToHTM attempts to recognise Ascii art and diagrams in documents.TI       Key indicators include large numbers of non-alphanumeric characterst!       and the use of white space.i  D       However, some diagrams use the same mix of line and alphabetic>       characters as tables, so the two sometimes get confused.  E       Should AscToHTM wrongly detect the extent or type of a diagram, R       you can mark up a section of text by using the BEGIN_DIAGRAM ... END_DIAGRAM)       pre-processor commands (see 7.1.6)..     5.5.3.4 Other formatted text  H       If AscToHTM detects formatted text, but decides that is is neitherK       table, code or art (and it knows what it likes), then the text may be <       put out "as normal", but with <BR> added to each line.       5.6   Added value markup   5.6.1 Document Title  J       AscToHTM can calculate - or be told - the title of a document.  ThisJ       will be placed in <TITLE>...</TITLE> markup in the <HEAD> section of       each HTML page produced.  I       The Title is calculated as in the order shown below.  If the first	eA       algorithm returns a value, the subsequent ones are ignored.t  J       1) If a $_$_TITLE pre-processor command (see 7.2.1) is placed in the(          source text, that value is used  G       2) If the "Use first header as title" policy is set (see 6.3.1.2)'J          then the first heading (if any) encountered is used as the title.  J       	 Note: 	Depending on your document structure, this is prone to giveD          	bland tiles like "Introduction: , "Overview" and "Summary"  E       3) If the "Use first line as title" policy is set (see 6.3.1.3)s>          then the first line in the file is used as the title.  L       4) If the "Document title" policy is set (see 6.3.1.1) then this value          is used.o  G       	 Note:  If this is the value you want, ensure the other policies &          	outlined above are disabled.    A       5) Finally, if none of the above result in a title the textc,       	 "Converted from <filename>" is used.     5.6.2 Contents lists  I       AscToHTM can detect the presence of a contents list in the originaloL       document, or it can generate a contents list for you from the headingsM       that it observes.  There are a number of policies that give you control(B       over how and where a contents list is generated (see 6.3.4).  J       There are three different situations in which contents lists may, or)       may not be generated.  These are :-a         	- Default conversions.   5       	- Conversion to a single file, using policies.   8       	- conversion to a multiple files, using policies.  G       Note:	In this release it's possible that generated contents lists E       		do not exactly match the actual headings.  This will be fixedc       		in the next release.    - 5.6.2.1 Contents lists in default conversionse  M       By default AscToHTM will not generate a contents list for a file unless        it already has one.c  I       If it should detect a contents list in the document, then that list M       will be changed into hyperlinks to the named sections.  In such a case, G       only those headings shown in the contents list are converted into I       links, and the link text is that in the original contents list, and D       not the text in the actual heading (often they are different).  I       Note:	AsctoHTM currently only detected numbered contents lists, andnA       		is occasionally prone to error when they are present.  Ifr@       		you experience problems, either delete the contents list@       		and get AscToHTM to generate one for you, or mark up the?       		existing list using the contents pre-processor commandsi       		(see 7.1.3)s    ; 5.6.2.2 Contents lists in conversions to a single HTML filel  I       As described in 5.6.2.1, AscToHTM will not generate a contents listm+       by default unless it already has one.   "       _Requesting a contents list_  K       However, you can request that a contents list is always generated, bygI       using the "add contents list" policy (see 6.3.4.1).  In this case as"       contents list will be either  1       a) made from the existing contents list, ore  I       b) generated from the observed headings.  in this case the contents B          list will only be as good as the detection of headings in*          the rest of the document permits.  )       _Forcing a generated contents list_.  I       You can force a generated list to be used by disabling the "Use anye3       existing contents list" policy (see 6.3.4.3).e  J       If an existing contents list is present, it will be deleted from theK       output.  Normally it's best to either use the existing contents list,rH       or to delete it from the source text and request a generated list.          _Contents lists placement_  J       By default the contents list will be placed at the top of the outputI       file.  In earlier versions of AscToHTM the contents list was always         placed in a separate file.    5       _Generating a contents list in a separate file_e  N       If you select the "Generate external contents list" policy (see 6.3.4.4)J       the contents list will be placed in a separate file, and a hyperlinkJ       to that file called "Contents List" is placed at the top of the HTML'       page generated form the document.i  F       You can choose the name of the external file using the "ExternalI       contents list filename" policy (see 6.3.4.5).  If omitted, the fileuK       will be called "Contents_<filename>", where <filename> is the name ofu#       the document being converted.s    < 5.6.2.3 Contents lists in conversions to multiple HTML files  K       AscToHTM can be made to split the output into many files.  At presentaI       this is only possible at numbered section headings.  Each generatedeH       page usually has a navigation bar, which includes a hyperlink back4       to the following section in any contents list.  ?       The behaviour is identical to that in 5.6.2.2 expect thato  4       a) the output is now split into several files.  H       b) the options to generate an external contents list in a separate&          file are no longer available.  I       c) if the contents list is being generated, it is now placed at theb;       	 foot of the first document, rather than at the top.t  H       	 This is usually *before* the first heading (which now starts the<       	 second document), and *after* any document preamble.  I       Note:	Where the original contents list is used when splitting files F       		it is possible that not every file will be directly accessibleG       		from the contents list, and that the back links to the contents A       		list may not function as expected.  In such cases you can B       		go from the contents list to a major section, and then useA       		the navigation bars to page through to the minor section.      5.6.3 Directory page  M       When converting several files at once, AscToHTM can be made to generate K       a "Directory Page".  This is an HTML index of all the files converted        and their contents.I  F       The policies available for controlling generation of a directory"       page are explained in 6.3.9.  J       The directory page will consist of an entry for each file converted,M       in the order that files are converted (usually alphabetic).  Each entryu"       will (optionally) contain :-  H       - A link to the file being converted.  The link will either be theI         converted file's HTML title, or failing that, the filename itself          (see 6.3.9.3)c  G       - Links to each of the sections of the converted file as detectedn       	by AscToHTM.e    % 5.6.4 Headers, footers and JavaScriptt  L       AscToHTM can be made to add standard header, footers and JavaScript toK       each page generated.  It does this by allowing you to specify includeRK       files to be copied into the generated HTML.  These include files can a&       contain any valid HTML commands.  7       The program supports three types of such files :-   K       i) Header files.  These contain any HTML you want placing immediately '          after the output's <BODY> tag.i  H       	 A good example might be a standard header, with a logo and links       	 back to the home page.  L       ii) Footer files.  These contain any HTML you want placing immediately(          before the closing </BODY> tag.         	tH       iii) Script files,  These contain any HTML you want placing insideJ       	   the <HEAD> ... </HEAD> portion of the generated file.  Such tags#            are not usually visible.n  D       	You should place in here any JavaScript you want, although itB       	will be difficult to make this apply to the converted text.    O       You can specify include files for the converted files, as well as for anyaN       directory page (see 5.6.3) that you create.  If you don't specify valuesN       for the directory page, then it will use the same files as the generated       files.     $_$_TABLE_WIDTH 60%   ! 6     Using Document Policy fileso! ---------------------------------s  L       Document policy files are ordinary text files that list the "policies"H       that AscToHTM should implement when converting your document.  TheN       file can have added comment lines (starting with a "!" or "#" character)       and headings for clarity.l  I       A summary of the recognised policy lines is given in the [PolDict].   L       In most cases recognised policy lines are identical to those listed inK       the generated policy file (see 4.1).  This is usually a good place tol(       start when making your own policy.  G       Only those lines that are recognised policies will be acted upon.s  H       To use a policy file, simply list it on the command line after the5       name of the file being converted (see 4.2.2.1).c  ,       Document policies have two main uses :  K       a) To correct any failure of analysis that AscToHTM makes.  HopefullypL          this won't be needed too much as the core analysis engine improves.  F       	 Examples include page width, whether or not underlined section#          headings are expected etc.r  K       b) To tell the program how to produce better HTML end product in ways C          that couldn't possibly be inferred from the original text.   F       	 Examples include adding colour and titles to the page, as wellG       	 as requesting a large document is split into several pages, andw!          a contents list created.k       6.1   An example conversionu  G       This documentation has itself been converted using AscToHTM.  Theu       files used werea  I       - A2HDOCO.TXT.  This is the text version of the documentation.  TheeG       	text version is kept as the master copy and updated as required..$         It's then converted to HTML.  P       - IN_A2HDOCO.POL.  This is the policy file used to create the HTML versionK       	of this document.  Only those policies that differ from the defaults          have been added.  D       	This policy file "includes" the link dictionary A2HLINKS.DAT.  J       - A2HDOCOH.TXT.  This is the header HTML added as the bottom of each       	generated HTML page.i  K       - A2HDOCOS.TXT.  This is the JavaScript HTML added into the <HEAD>...tK       	</HEAD> portion of the generated HTML page.  This particular exampleoC         toggles the logo when the mouse is over it (only if you use &       	Netscape V3.0 or above though).  I       - A2HLINKS.DAT.  This is the link dictionary used for this document <         and is used to add hyperlinks to the main text file.  J       - A2HDOCOF.TXT.  This is the footer HTML added as the bottom of each       	generated HTML page.t  D       These files are included in the distribution kit as an example       set of documentation.c  I       You can, of course, use AscToHTM to convert this doco into whatevero'       format, colour etc that you wish.n     6.2   Analysis policies>  N       These policies are generated during the analysis of the source document.K       They should only normally need changing when AscToHTM's analysis goesg        wrong in some way or other     6.2.1 General Analysis policiese   Example:     	[General Analysis] 1         -----------------------------------------./       	Indent position(s)                (none)e-         Search for Definitions            Yeso) 	Definition Char                   (none)c) 	Hanging paragraph position(s)     (none)a% 	Page width                        76 +         TAB size                          8b' 	Text Justification                Lefti& 	Expect blank lines between paras  Yes) 	New Paragraph Offset              (none)a% 	Keep it simple                    No $ 	Min chapter size                  8) 	Short line length                 (none)n% 	Expect code samples               Noi     6.2.1.1 "Indent position(s)"  I       These are the positions of the major indent levels in the document.dJ       This should be a list of ascending space-separated numbers, with "0"$       usually being the first value.    ! 6.2.1.2 "Search for Definitions"           *New in V3.0*g  P       This policy can be used to disable the search for definitions (see 5.1.5).N       Use this whenever your file contains no definitions, but AscToHTM thinks       it does.     6.2.1.3 "Definition Char"   #       See the discussion in 5.1.5.1p    ' 6.2.1.4	"Hanging paragraph position(s)"f  J       These refer to the indentation levels at which definition paragraphs!       are expected (see 5.1.5.2).c     6.2.1.5	"Page width"  E       This value can be used to influence short line and centred text I       detection.  It also helps to determine if the definition charactersLI       ':' and '-' (see 5.1.5.1) are to be regarded as "strong" or "weak".s     6.2.1.6 "TAB size"         *New in V3.0*e  H       This value can be used to specify the size of TABs in your source M       document.  AscToHTM converts all tabs to space assuming using this tab nN       size.  This becomes important only when comparing lines that use tabs toJ       lines that use spaces for alignment.  If problems occur you may findA       indentations appear strange, or tables are not quite right.s  J       Note, text that is all tabs or all spaces should experience no such        problems.(  P       If you know your source file uses a different TAB size (e.g. Notepad files3       use a value of 4), try adjusting this policy.M     6.2.1.7	"Text justification"  ?       This policy is important in detecting pre-formatted text.   E       The possible values are "left", "center" (i.e. left and right), I       "right" and "none".  If text is centered then padding spaces may beiG       added.  This has to be ignored when detecting pre-formatted text.r    * 6.2.1.8	"Expect blank lines between paras"  N       Paragraphs are normally expected to have blank lines before them.  WhereF       this isn't true (e.g. on a text file dumped from Word) different0       algorithms can be applied more rigorously.     6.2.1.9	"New paragraph offset"  F       This policy refers to any hanging indent.  Again, this is a Word       for Windows favourite.     6.2.1.10 "Keep it simple"t  C       This policy tells AscToHTM to suppress much of its search forgK       global structure.  This should be used when converting documents that K       don't really have numbered sections, but which might look to AscToHTM M       as though they do (e.g. because they contain addresses, lists or tablesu       of consecutive numbers)   M       An example might be an email digest which consists of a series of smalllM       documents collected together.  This is quite likely to confuse AscToHTMoK       because it violates the one assumption (see 3.1) that AscToHTM makes.      6.2.1.11 "Min chapter size"e  L       This policy allows you to specify the minimum chapter size expected inL       the document (in numbers of lines).  AscToHTM will ignore any apparent6       Chapter headings that appear too close together.     6.2.1.12 "Short line length"  I       This policy determines what constitutes a short line.  AscToHTM mayk2       add a <BR> to any line it deems to be short.  F       If omitted, a "short" line is determined as some fraction of theG       calculated page width.  The fraction varies from 50-75% accordingg/       to the conversion type being carried out.      6.2.1.13 "Expect code samples"  K       This policy indicates that the document is liable to contain sectionsoE       of programming code.  AscToHTM will attempt to detect such coderC       fragments, and preserve their layout so that the code remainsA       comprehensible.t  F       Pre-processor commands now allow you to mark up sections of your+       document as code samples (see 7.1.5).   B       You can choose how code fragments are marked up by using the8       "Use <CODE>..</CODE> markup" policy (see 6.3.6.11)     6.2.2 Bullet policies   L       AscToHTM has the following bullet point policies that will normally be2       correctly calculated on the analysis pass :-    
 	[Bullets]         --------- (       	Expect Numbered bullets       Yes! 	Expect alphabetic bullets     Nol! 	Expect Roman Numeral bullets  Nob  " 	Bullet Char                   '-'" 	Bullet Char                   'o'" 	Bullet Char                   '*'    J       AscToHTM tries hard not to get confused by the "1", "a" and "I" thatH       happen to end up at the start of lines by random.  These could get!       mistaken for bullet points.1    ! 6.2.2.1 "Expect Numbered bullets"t  J       This indicates that numerical bullets are expected (but you probably       guessed that).    # 6.2.2.2 "Expect alphabetic bullets"c  6       This does likewise for alphabetic bullet points.  K       AscToHTM recognises (and distinguishes between) upper and lower case	"       variants.O    & 6.2.2.3 "Expect Roman Numeral bullets"  H       This does likewise for roman numerals.  Again upper and lower case       variants are recognised.     6.2.2.4 "Bullet Char"   M       These policy lines indicate character(s) that can occur at the start of G       a line to represent a bullet point.  Special attention is paid to 8       '-' and 'o' characters, but any character will do.  #       Use one line per bullet char.t       6.2.3 Headings  O       AscToHTM has the following section heading policies that will normally bec2       correctly calculated on the analysis pass :-   	[Headings]o  	----------+         First Section Number              1 % 	Expect Numbered Headings          Noe& 	Expect Underlined Headings        Yes% 	Expect Capitalised Headings       Non% 	Expect Second Word Headings       No ( 	Smallest possible section number  1.1.0( 	Largest  possible section number  2.4.9  K       Section headers are far and away the most complex things the analysis-G       pass has to detect, and the most likely area for errors to occur.a  I       AscToHTM will also document to a policy file the headings it finds. A       This is still to be finalised, but currently has the formatt  
 $_$_BEGIN_PREi$       We have 4  recognised headings,           Heading level 0 = "" N at indent 0.           Heading level 1 = "" N.N at indent 0-           Contents level 0 = "" N at indent 0 /           Contents level 1 = "" N.N at indent 2d $_$_END_PREt  L       AscToHTM will read in such lines from a policy text file, but does notG       yet fully supported editing these via the Windows interface.  ThewM       syntax is explained in 6.2.3.8, but this will probably change in futureh       releases.l     6.2.3.1 "First Section Number"  =       This policy indicates what the first section number is.oK       Normally this starts at 1, but if it starts higher, then AscToHTM maysM       reject headers as being out of sequence, and fail to detect to presencee-       or absence of contents lists correctly.     " 6.2.3.2 "Expect Numbered Headings"  I       This indicates whether or not numbered sections are to be expected.c    $ 6.2.3.3 "Expect Underlined Headings"  J       This indicates whether or not underlined headers are to be expected.I       AscToHTM normally promotes any underlined lines to section headers.l;       This policy can be used to switch that behaviour off._    % 6.2.3.4 "Expect Capitalised Headings"o  L       This indicates whether or not a line that is wholly capitalised should'       be regarded as a section heading.o    % 6.2.3.5 "Expect Second Word Headings"          *Reserved*    * 6.2.3.6 "Smallest possible section number"         *Reserved*    ) 6.2.3.7 "Largest possible section number"o         *Reserved*    + 6.2.3.8 "xxxx level 1 = "" N.N at indent 2"t  '       *Note, this is not finalised yet*n  M       These lines describe in readable text form part of the headings policy.bK       You can edit these lines in your policy file, but not yet through the         policy options in Windows.  3       The lines are currently structured as followsN     $_$_BEGIN_TABLEe       	Line component		Value3       	--------------------------------------------a6       	xxxx			Either "Heading" or "Contents" accordingI                                 to the part of the policy being described   H         Level n                 Level number, starting at 0 for chapters;                                 1 for level 1 headings etc.r  M         "Some_word"             Any text that may be expected to occur beforexP                                 the heading number.  E.g. "Chapter" or "Section"A                                 or "[".  The case is unimportant.n  K         N.Nx                    The style of the heading number.  This willuF                                 ultimately (in later versions) be readF                                 as a series of number/separator pairs.  6                                 The proposed format is.                                   "N" = numberL                                   "i" / "I" = lower/upper case roman numeralO                                 with an 'x' at the end signalling that trailing I                                 letters may be expected (e.g. 5.6a, 5.6b)e  M         at indent n             The indentation that this heading is expectedkN                                 at.  This is important in helping to eliminate1                                 false candidates. 
 $_$_END_TABLEs     6.2.4 Pre-formatted text  O       AscToHTM has the following section heading policies that will normally be 2       correctly calculated on the analysis pass :-         	[Pre-formatted text]d,       	-------------------------------------) 	Minimum automatic <PRE> size      (none)     & 6.2.4.1 "Minimum automatic <PRE> size"  H       This policy specifies the minimum number of lines that must appearD       pre-formatted before they can be placed in their own <PRE> ...       </PRE> sections.  J       This is sometimes desirable, so is set to 1 by default.  For exampleI       if you have lines with page numbers at the top of each page in your F       document.  Of course... this makes no sense in an HTML document.  H       Note:  Only values in the range 1-20 are likely to have an effect.E       	     Values above 20 are likely to simply disable this featurea@       	     entirely.  This limitation is due to the size of the+       	     readahead buffer AscToHTM uses.     ) 6.2.4.2 "Minimum TABLE column separation"e  P       This policy specifies the minimum number of spaces that may be interpreted'       as a column separator in a table.a  K       The default value is 1, but in small tables this can lead to too manylM       "columns" being detected.  If you experience this problem increase this        value to 2 or higher.i  K       Note, if the value becomes too large, you may experience the oppositel5       problem, i.e. too *few* columns being detected.      6.2.4.3 "Expect sparse tables"           *New in V3.0*   J       This policy specifies that tables within the source document may be O       sparse.  This fact will then be used to adjust the analysis of any tablesn       detected  I       Columns which appear to have little or no data in them are usually eF       eliminated by merging them with their more populated neighbours.  P       If you set this policy, this process is relaxed, meaning that you will getA       more, emptier, columns rather than fewer, more filled ones.   L       This policy can be toggled for individual tables via the pre-processor,       command TABLE_MAY_BE_SPARSE (see 7.4).     6.2.5 Contents List policies  H       There is only one analysis contents policy ("Expect contents list"       see 6.3.4.2).e  K       This is described together with all the output contents list policies/K       in 6.3.4.  For more information on content list generation see 5.6.2.w     6.3 Output policies   H       These policies allow you to fine tune the conversion, and are used        during the output to HTML.     6.3.1 Added HTML details  N       AscToHTM has the following HTML policies that will only ever take effect*       if supplied in a user policy file :-  
 	[Added HTML]i       	------------ ?       	Document title               AscToHTM user documentation '         Use first heading as title   No '         Use first line as title      Nol4 	Document keywords            text, html, conversionE 	Document description         Part of the AscToHTM user documentation-* 	HTML Script file             a2hdocos.txt* 	HTML header file             a2hdocoh.txt* 	HTML footer file             a2hdocof.txt$ 	Background Image             (none)$ 	Background Colour            E0D0E0! 	Text Colour                  Red $ 	Unvisited Link Colour        (none)$ 	Visited Link Colour          (none)$ 	Active Link Colour           (none)  N       These "polices" allow you to start "adding value" to the HTML generated.L       That is, they allow to specify things that cannot be inferred from the       original text.  H       You can also add HTML to your files by using the HTML preprocessor       command (see 7.1.4)n     6.3.1.1 "Document Title"  N       This identifies the text to be placed in the <TITLE> ... </TITLE> markup       in the document header.   H       If omitted, the default title will be "Converted from <filename>".K       We did consider defaulting to the first line of text, but that rarely        works.  L       The title can also be specified via a preprocessor command (see 7.2.1)I       placed in the source document, which will override this policy when        present.  P       To fully understand how titles are calculated, see the discussion in 5.6.1    $ 6.3.1.2 "Use first heading as title"  I       This policy specifies that the first heading in the document may bes7       considered as a candidate for the document title.   M       In the current version (V2.3) there may be implementation problems that L       cause the wrong line to occasionally be selected as the first heading.  P       To fully understand how titles are calculated, see the discussion in 5.6.1    ! 6.3.1.3 "Use first line as title"   N       This policy specifies that the first meaningful line in the document mayH       be considered as a candidate for the document title.  "Meaningful"K       in this context means more that 2 characters long once trimmed of alle'       leading and trailing white space.   P       To fully understand how titles are calculated, see the discussion in 5.6.1     6.3.1.4 "Document keywords"a  D       This policy allows you to specify keywords that are added to a=       META tag inserted into the <HEAD> section of the outputt       page(s) as follows :-h  =       	<META NAME="keywords" CONTENT="your list or keywords">   L       This tag is often used by search engines when indexing your HTML page.I       You should add here any relevant keywords possibly not contained in        the text itself.  J       The presence of a KEYWORDS pre-processor command will overrides this       policy (see 7.2.3).d     6.3.1.5 "Document description"  F       This policy allows you to specify a description of your documentI       that is added to a META tag inserted into the <HEAD> section of the "       output page(s) as follows :-  ;       	<META NAME="description" CONTENT="your description">   J       This tag is often used by search engines (e.g. AltaVista) as a briefI       description of the contents of your page.  If omitted the first fewnC       lines may be shown instead, which is often less satisfactory..  K       The presence of a DESCRIPTION pre-processor command will override any-9       description specified in a policy file (see 7.2.2).i     6.3.1.6 "HTML Script file"  L       This identifies the name of a text include file to be transcribed into@       the <HEAD> ... </HEAD> portion of the generated HTML page.  K       This allows you to place JavaScript in your pages (though you'll be a /       little limited as to what it can act on).   H       Recently HTML has introduced style sheets (see 6.3.6.1 and 7.2.4).     6.3.1.7 "HTML header"   L       This identifies the name of a text include file to be transcribed intoG       the HTML file at the top of the <BODY> ... </BODY> portion of thei       generated HTML page.  K       This can be used to add standard headers, logos, contact addresses toaJ       your HTML pages, and is especially useful to give a consistent "lookG       and feel" when breaking your document up into a number of smaller3       HTML files.p     6.3.1.8 "HTML footer"e  L       This identifies the name of a text include file to be transcribed intoJ       the HTML file at the bottom of the <BODY> ... </BODY> portion of the       generated HTML page.  F       This can be used to add "return to home page" links, and contactK       addresses to your HTML pages.  Again, this helps to give a consistent M       "look and feel" when breaking your document up into a number of smallerc       HTML files.e     6.3.1.9 "Background Image"  I       This identifies the URL of any image to be placed in the BACKGROUND "       attribute of the <BODY> tag.      6.3.1.10 Various colour policies  G       These policies identifies the colours to be placed in the various J       attributes of the <BODY> tag.  You can enter any value acceptable toL       HTML.  Normally a value is expressed as a 6-digit hexadecimal value inJ       the range 000000 (black) to FFFFFF (white), but certain colours suchM       as "white", "blue", "red" etc may also be recognised by HTML.  AscToHTMa9       simply transcribes your value into the output file.e  M       The various policies control the colours of the foreground Text (TEXT), O       the background (BGCOLOR), unvisited hyperlinks (LINK), visited hyperlinks ,       (VLINK) and active hyperlinks (ALINK).  H       A value of "none" signals the defaults are to be used.  By defaultK       AscToHTM changes the background colour to be white, and omits all then"       other <BODY> tag attributes.       6.3.2 Hyperlinks  F       AscToHTM has the following hyperlink policies set as defaults :-  
 	[Hyperlinks]e       	------------e%         Create hyperlinks          Noe 	Create mailto links        Yesa 	Create NEWS links          Yesk 	Only use known groups      Yes +         Recognised USENET groups   uk demonr 	Cross-refs at level        2i  J       Hyperlinks can also be added by using a link dictionary (see 4.3.2.2       and 4.4.2).e     6.3.2.1 "Create hyperlinks"   C       This policy really means that all http, www and ftp URLs willp"       get converted to hyperlinks.     6.3.2.2 "Create mailto links"   H       This indicates that probable email addresses such as jaf@yrl.co.uk1       are to be converted into mailto hyperlinks.b     6.3.2.3 "Create NEWS links"   ?       This indicates that probable newsgroup references such as =       alt.games.mornington.cresent (sic) are to be converted.m     6.3.2.4 "Only use known groups"s  J       This indicates whether or not only newsgroups from known hierarchies0       should be converted into news: hyperlinks.  G       AscToHTM can detect possible newsgroups by looking for words likepG       "something.like.this" and "news.answers".  However assuming these +       are newsgroups often leads to errors.e  K       Consequently if this policy is set to "Yes" then candidate newsgroupspI       have to belong to either a standard USENET hierarchy such as "alt",lN       "comp", "sci" etc, or to a user-specified USENET hierarchy (see 6.3.2.5)  D       If set to no, then "something.like.this" will be turned into a       news: hyperlink.  G       This policy only takes effect if conversion of news hyperlinks isc       selected.o         The defaults is "Yes"i    " 6.3.2.5 "Recognised USENET groups"  K       This policy allows you to specify USENET hierarchies that you wish toiM       recognise in addition to the standard hierarchies. The value is a space K       separated list of the top level hierarchy names.  So, for example, topC       ensure that uk.telecom and demon.ip.support are recognised as C       valid newsgroup hyperlinks, set the policy value as follows:-   0             	Recognised USENET groups : uk demon  L       This has, of course, been used on the HTML version of this file to get!       the above links to work :-)h     6.3.2.6 "Cross-refs at level"i  C       This indicates the section level at which and above which alls9       cross-references are to be converted to hyperlinks.b  F       For example a value of 2 means all n.n, n.n.n etc references areG       converted.  A value of "1" might seem desirable, but is liable to -       give many false references (see 5.3.2).   7       This behaviour may be improved in later versions.     % 6.3.2.7 "Add <BR> to lines with URLs"t         *New in V3.0*f  O       This policy indicates that lines that are detected as having URLs in them L       should have <BR> markup added to the end.  This is useful in documentsJ       that have a list of URLs, one per line, as the URLs usually make theM       lines quite long (avoiding short line detection), and you would want to "       preserve the line structure.  G       However, this is less useful where URLs occur in the middle of a  H       paragraph of text, as it inserts a <BR>, and breaks the paragraph.  M       Prior to V3.0 this was default behaviour, but now it is switched off byr       default.    I       In later versions we may attempt to make this policy auto-detected.i     6.3.3 File generationi  N       AscToHTM has the following HTML policies that will only ever take effect*       if supplied in a user policy file :-   	[File generation]       	-----------------)       	Input directory             (none)h# 	Output directory            (none)  	Use .HTM extension          No-(         Output file extension	    (none) 	Use DOS filenames           No # 	DOS filename root           (none)N# 	Split level                 (none) # 	Min HTML File size          (none) &         Minimise HTML file size     No 	Add navigation bar          Non  	Output policy file          Yes# 	Output policy filename      (none)o 	Generate diagnostics files  Nos%         Error reporting level       5a  G       These policies how your document is divided into one or more HTMLsI       files, and how those files are to be named and linked together withh       hyperlinks.i     6.3.3.1 "Input directory"f         *Reserved for future use*h  I       This policy will allow the source directory to be specified.  It is J       not yet implemented, but currently the input directory is written toG       any output policy file created, indicating where the source files_/       where found relative to the run location.o  7       A value of blank indicates the current directory.e     6.3.3.2 "Output directory"  .       *Not available in the shareware version*  K       This policy allows you to specify which directory you want your filesF       output to.  M       If an output policy file is created, this indicates where the generatedl6       files where placed relative to the run location.  7       A value of blank indicates the current directory.d     6.3.3.3 "Use .HTM extension"  O       This policy specifies whether or not the generated HTML files should have J       a .HTM extension.  The default is to use a ".html" extension, unless)       DOS-compatible files are requested.      6.3.3.4 "Output file extension"          *New in V3.0*t  O       This policy specifies an alternative extension to be used for the createdaL       files.  For example you may want the program to create ".shtml" files.  7       If present, this policy overrides that in 6.3.3.3w     6.3.3.5 "Use DOS filenames"l  H       This policy allows you to specify that the HTML file names must be       DOS compatible.d  H       If selected the filenames will all have a ".HTM" extension, and be       given upper case names.   G       Any file name whose root exceeds 8 character will be shortened byeH       keeping the first 3 characters, and adding a unique 5-digit number#       derived from the longer name.b  $       See the discussion in 4.2.2.4.     6.3.3.6 "DOS filename root"s  H       Where DOS filenames are used this allows you to specify an up-to-5B       character root to which any section numbers will be appended       (see 6.3.3.8).  M       If splitting a document at 2 levels we normally recommend a 3-character        filename root.  I       Thus MYDOC.TXT given a root of MYD would produce MYD.HTM, MTD_1.HTMtF       MYD_1_1.HTM etc... which are all less than 8 characters and thus        maintain some readability.  B       If no root were specified, MYDOC_1_1.HTM would be renamed toC       MYDnnnnn.HTM where "nnnnn" would be a generated 5-digit code.x  $       See the discussion in 4.2.2.4.    ! 6.3.3.7 "Minimise HTML file size"o         *New in V3.0*   J       This policy may be used to reduce the size of the created HTML file.H       By default AscToHTM attempts to layout the created HTML code in anL       easy-to-read manner.  This was done so that the created HTML would be -       easier to manually edit after creation.   M       To make the code easier to read, AscToHTM inserts white space to indent L       the code to match the output indentation levels.  It also outputs each&       cell of a TABLE on its own line.  D       All this white space adds up, particularly the indentation of I       largely-empty cells in TABLES.  If you select this option, all the t&       extra white space is eliminated.  O       Depending on the file contents, this can make the file 5-20% smaller (andt:       hence faster to download), at a cost of readability.     6.3.3.8 "Split level"A  J       This identifies the heading level at which the generated HTML should"       be split into smaller files.  <       A value of "none" will put all the HTML into one file.  L       A value of "1" will create a new HTML file for each new major section.J       A value of "2" will create a new HTML file for each new n.n section,J       whilst "3" creates a new document for each n.n.n section, and so on.  N       The first file created normally has a name that matches the source file.K       Subsequent files append the section number, separated by underscores.t  K       This a file called MYDOC.TXT, will generate MYDOC.HTML, MYDOC_1.HTML,g       MYDOC_1_1.HTML etc...O     6.3.3.9 "Min HTML File size"  I       This policy is only relevant when splitting the document into smalloD       output files, i.e. a "split level" is specified (see 6.3.3.8).  I       This policy specifies a minimum output HTML size in lines (although         this is only approximate).  G       This can be useful for documents that have chapters where all the E       content is in the sub-sections.  In such documents you'd end uptG       with a virtually empty chapter heading file if this policy is nots       used.a     6.3.3.10 "Add navigation bar"l  M       This policy is only relevant if you have elected to split your document 8       into a number of smaller HTML files (see 6.3.3.8).  L       In such cases this policy allows you have a navigation bar inserted atF       the foot of each HTML page, before any standard footer is added.  $       The navigation bar consists of  =       -	A "Previous" link, to take to the previous HTML page.r5       -	A "Next" link, to take to the next HTML page. J       -	A "Contents" link, to take to the start of the next section in the         contents list.     6.3.3.11 "Output policy file"n  L       This policy allows you to specify that you want AscToHTM to output theH       file policy that is being used.  This will be a combination of theE       policy calculated by AscToHTM during the analysis pass, and anyt!       user-supplied policy lines.e  E       The output policy file will have a .pol extension in the outputo       directory.  G       Note_1:	In earlier versions of AscToHTM the creation of an outputs;                 policy file was the default, now it is not.w  M       Note_2:   This policy has the same effect as the command line qualifier < 		/POLICY (see 4.2.2.5).  An output file will be create when@ 	        either that qualifier is used, or this policy is set to                 yes.    ! 6.3.3.12 "Output policy filename"e  -       **** not supported in this release ****g    % 6.3.3.13 "Generate diagnostics files"e  F       This policy specifies whether or not diagnostics files should beI       produced.  This has exactly the same effect as the /DEBUG qualifiero1       has in command line versions (see 4.2.2.2).       6.3.3.14 "Error reporting level"         *New in V3.0*   G       This policy specifies the level of reporting you want during the HI       conversion.  AscToHTM can generate a variety of messages of varyingeH       severity to inform you of the decisions it's made.  These messagesJ       can be useful in explaining why a conversion has gone wrong, but are&       less interesting at other times.  J       Whilst all of these messages are copied into any .lis files created J       (see 6.3.3.13 and 4.2.2.2) regardless of severity, you can use this M       policy to choose the level of reporting you want to see on your screen.y  O       The value is nominally in the range 1-10 with a value of 1 showing almostoH       all messages, and 10 showing almost none.  The default value is 5.     6.3.4 Contents  K       AscToHTM has the following HTML policies that influence the detection>)       and generation of contents lists :-    	[Contents]        	----------e,       	Add contents list                  No,       	Expect Contents List               No,       	Use any existing contents list     No,       	Generate external contents file    No0       	External contents list filename    (none),       	Hyperlinks on numbers              No  &       See also the discussion in 5.6.2     6.3.4.1 "Add contents list"e  I       This policy specifies that AscToHTM should generate a contents listiG       to match all the section heading that it marks up.  This contentstF       list will consist of hyperlinks to take you to the corresponding       section and HTML file.  K       The placement of the contents list depends on how you have decided toc.       split up your output HTML (see 6.3.3.8).  J       If you decide to convert MYDOC.TXT to a single HTML file MYDOC.HTML,I       AscToHTM will create a separate file called CONTENTS_MYDOC.HTML andhH       add a link to this file at the top of MYDOC.HTML.  You can, if you;       wish, simply cut and paste this file into MYDOC.HTML.i  E       If you decide to convert MYDOC.TXT into several files, then theeH       contents list is placed at the bottom of MYDOC.HTML, and points toE       all the newly created files.  Any text before the first sectionrM       in your document will be placed before the contents list in MYDOC.HTML.   O       Whenever you elect to have a contents list generated, and lines perceivedoK       by AscToHTM as being part of a contents list in the original document        will be discarded.  C       You can enable this option from the command line by using theh'       /CONTENTS qualifier (see 4.2.2.1)n     6.3.4.2	"Expect contents list"  N       This is an analysis policy that indicates whether or not the source file)       contains an existing contents list.n  M       This should be detected automatically, but sometimes the analysis failsoC       in which case you should either set this manually, or mark upc@       the contents list using pre-processor commands (see 7.1.3)  "       See the discussion in 5.6.2.    ( 6.3.4.3 "Use any existing contents list"  P       This policy specifies whether or not you wish to use any existing contentsI       list found in the source document.  If you disable this option, anysK       contents found will be discarded.  A contents list will only be addedoA       if you select the "add contents list" policy (see 6.3.4.1).c  "       See the discussion in 5.6.2.    ) 6.3.4.4 "Generate external contents file"e  P       This policy specifies whether any generated contents list should be placedF       in a separate file, as opposed to at the top of the output file.  G       This option is not always possible, specifically when an existingnI       contents list is being used, or when the source is being split intoa       many files..  "       See the discussion in 5.6.2.    ) 6.3.4.5 "External contents list filename"n  I       This is the name of the external content file generated by AscToHTMn#       should such a file be wanted.   B       By default the file will be called contents_<filename>.html.  F       The contents file should be in the same directory as the created       HTML files.n  "       See the discussion in 5.6.2.     6.3.4.6 "Hyperlinks on numbers"L  H       This policy specifies that where a file has numbered sections, andH       a contents list is being created, whether the hyperlink taking youB       to the section should be on the number or the section title.  A       The default is to place the hyperlink on the section title.c     6.3.5 Preprocessor policiesT  G       AscToHTM has the following policies that can be used to influencehF       the preprocessor (see [section 7]), and hence the HTML output :-   	[Preprocessor]c       	-------------- (       	Use Preprocessor              Yes0       	Include document section(s)   Public_part     6.3.5.1 "Use Preprocessor"  J       This policy tells AscToHTM whether or not the preprocessor should beK       used.  If it isn't used, then all preprocessor directives are ignoredeB       and a straight conversion from input to output files occurs.  C       Note:	If this policy is set to "no", all related preprocessort%       		policies will have no effect."    % 6.3.5.2 "Include document section(s)"n         *Changed in V2.3*   G       This policy tells AscToHTM which section types are to be includeduL       in the conversion (see 7.1.1).  The name(s) supplied should match that       in the SECTION directive.l  L       A value of "all" indicates that all section types should be converted.  M       The value may be a space-separated list of section names.  Each section B       name must be a single word (underscores are allowed though).     6.3.6 StyleB  H       AscToHTM has the following "styling" that can be used to influence       the HTML output :-   	[Style]       	-------1       	Document Style Sheet              text.cssi% 	Highlight Definition Text         No % 	Allow automatic centring          No $ 	Automatic centring tolerance      2$ 	Smallest allowed <Hn> tag         5$ 	Largest allowed <Hn> tag          21         Headings colour                   #ABABAB % 	Ignore multiple blank lines       No & 	Search for emphasis               Yes,       	Allow definitions inside PRE      Yes& 	Use <DL> markup for defn. paras   Yes+       	Use <CODE>..</CODE> markup        No      6.3.6.1 "Document style sheet"  F       This policy allows you to specify the URL of a style sheet file,N       usually with a .css extension.  Style sheet files are a new HTML featureN       that allow you specify fonts and colours to be applied to your document.  J       The resulting HTML is inserted into the <HEAD> section of the output       page(s) as follows :-r  9       	<LINK REL="STYLESHEET" HREF="URL" TYPE="text/css">b  L       The presence of a STYLE_SHEET pre-processor command will overrides any9       style sheet specified in a policy file (see 7.2.4).     # 6.3.6.2 "Highlight definition text"s  9       This policy specifies whether or not the definitionsJ       term (the part marked up in <DT> ... </DT>) should be placed in bold'       for greater emphasis (see 5.1.5).h    ) 6.3.6.3 "Use <DL> markup for defn. paras"t  G       This policy specifies whether or not definition paragraphs should @       be marked up using <DL><DT>..<DT> <DD>..</DD></DL> markup.  #       See the discussion in 5.1.5.2k    " 6.3.6.4	"Allow automatic centring"  M       This policy allows automatic detection of centred text to be performed.   N       This is normally left switched off, as it is prone to give errors.  This1       algorithm may be refined in later versions.a    & 6.3.6.5	"Automatic centring tolerance"  H       This policy specifies the tolerance used (expressed as a number of5       characters offset) when detecting centred text.e  O       Given that the detection of centred text depends on its position relative P       to the calculated page width, which itself may not be accurate, increasingN       this value may give better results.  Equally, if may wrongly detect more       text as centred.  K       The default value is 2, which is also used as a minimum regardless ofh       the value you enter.    C 6.3.6.6 "Largest  allowed <Hn> tag" and "Smallest allowed <Hn> tag"2  J       These policies control the output heading sizes.  By default <H2> isL       used for main level headings, with each subsequent heading level being8       one size smaller, down to <H3> (normal text size).  ;       In the contents list, entries are shown down to <H4>.N  N       The software will ignore these values if out of range, or if the largestO       value represents a smaller heading (larger Hn) that the "smallest" value.n     6.3.6.7 "Headings colour"i         *New in V3.0*e   H       This policy tells AscToHTM what colour to use for all the Headers.$       Not all browsers support this.  I       The value must be a proper HTML colour (see discussion in 6.3.1.10)L    % 6.3.6.8 "Ignore multiple blank lines"p  I       This policy specifies whether or not multiple white lines should beV       ignored.  L       Normally HTML ignores white space, but if this policy is selected then6       additional blank lines will be marked us as <BR>  H       If you wish to eliminate white space from your output, switch thisM       off.  You should also review the "Use <P> markup for paragraphs" policyl       (see 6.3.6.12).o  ,       This policy is switched on by default.     6.3.6.9 "Search for emphasis"i  N       This policy specifies whether or not AscToHTM should look for emphasisedH       text.  Text can be emphasised by placing asterisks (*) either sideI       of it, or underscores (_).  AscToHTM will convert the enclosed textz&       to bold and italic respectively.    ' 6.3.6.10 "Allow definitions inside PRE"   L       This policy specifies whether or not AscToHTM should detect definitionI       terms inside a pre-formatted section of text.  Only really relevant F       if the "Highlight definition text" policy is selected (6.3.6.2).    % 6.3.6.11 "Use <CODE>..</CODE> markup"e  K       This policy specifies that where a code fragment has been detected oro9       marked up, what sort of HTML markup should be used.c  H       HTML provides a special <CODE> .. </CODE> markup that is suited toK       variables being quoted in text, but is not well suited for marking uppH       several lines.  In particular, you have to add non-breaking spacesK       and <BR> markup if you wish to correctly lay out several lines.  Thist>       makes the resultant HTML harder to read and much larger.  K       For this reason, AscToHTM defaults to <PRE> .. </PRE> markup for code K       fragments.  The only reason for reversing this might be if you needed A       the <CODE> tag for a particular style sheet to take effect.h    ( 6.3.6.12 "Use <P> markup for paragraphs"  I       This policy specifies whether <P> or <BR> markup should be used for H       paragraphs.  In most browsers <P> markup produces more white spaceG       with apparently a "blank line" placed between paragraphs.  A <BR>h       doesn't have this effect.-  J       You should use this policy if you wish to reduce the amount of whiteI       space in your output document, in which case you should also review =       the "ignore multiple blank lines" policy (see 6.3.6.8).t  ,       This policy is switched on by default.     6.3.7 Table Generation  G       AscToHTM has the following policies that can be used to influencecF       whether or not AscToHTM will attempt to detect and generate HTML9       tables, and the attributes of any tables generated.   J       Tables may be tailored individually by adding pre-processor commands#       to your source text (see 7.4)          	[Table generation]n,       	-------------------------------------,       	Attempt TABLE generation          Yes*       	Default TABLE border size         2/       	Default TABLE header rows         (none)r/       	Default TABLE header cols         (none)f*       	Default TABLE cell spacing        2*       	Default TABLE cell padding        2/       	Default TABLE colour              (none)t-       	Default TABLE border colour       Blue /       	Default TABLE caption             (none)n,         Convert TABLE X-refs to links     No    " 6.3.7.1 "Attempt TABLE generation"  K       This policy disables automatic table generation.  AscToHTM will stillfG       look for pre-formatted text, but will default to outputting it inn6       <PRE> ... </PRE> markup as it did prior to v2.2.    # 6.3.7.2 "Default TABLE border size"   N       This policy sets the default value for the BORDER attribute.  A value of       0 means "no border".    # 6.3.7.3 "Default TABLE header rows"f  K       This policy tells AscToHTM how many lines should be treated as headerd/       lines and placed in <TH> .. </TH> markup.w  J       AscToHTM will a small number of lines of text above a line as header       automatically.  4       If set, this value will apply to *all* tables.    # 6.3.7.4 "Default TABLE header cols"t  I       This policy tells AscToHTM how many columns in each table should bewJ       highlighted as "header" columns using <B> ... </B> markup inside the       table cells.    $ 6.3.7.5 "Default TABLE cell spacing"  P       This policy tells AscToHTM what value to use for the CELLSPACING attributeM       of the table.  Browsers that support this will add space *between* eache       cell.   "       A value of "0" means "none".    $ 6.3.7.6 "Default TABLE cell padding"  P       This policy tells AscToHTM what value to use for the CELLPADDING attributeL       of the table.  Browsers that support this will add space *inside* each       cell.f  "       A value of "0" means "none".     6.3.7.7 "Default TABLE colour"  N       This policy tells AscToHTM what colour to use for the background to each+       cell.  Not all browsers support this.e  ;       The value must be a proper HTML colour (see 6.3.1.10)     % 6.3.7.8 "Default TABLE border colour"r  I       This policy tells AscToHTM what colour to use for the table border.r$       Not all browsers support this.  ;       The value must be a proper HTML colour (see 6.3.1.10)      6.3.7.9 "Default TABLE caption"p         *Reserved*     6.3.7.10 "Default TABLE width"  J       This policy tells AscToHTM what value to use for the WIDTH attribute       of the table.   N       The WIDTH is specified either as a number (of pixels) or as a percentageM       (of screen width).  Thus "400" and "75%" are both valid values (withoutu       the quotes)h  A       Note:	If you use this policy, *all* your tables will be theg?       		same width.  If you wish to switch it on for individuali@       		tables, place $_$_TABLE_WIDTH commands (see 7.4) in your       		source file instead.    ( 6.3.7.11 "Convert TABLE X-refs to links"         *New in V3.0*s  P       AscToHTM can convert cross-references to numbered sections into hyperlinksJ       to those sections.  Unfortunately, the program cannot differentiate O       between section references and ordinary numbers in the source text.  Thise!       leads to occasional errors.t  L       This problem proved to be particularly acute inside tables of numbers.K       For that reason this policy was introduced to allow the conversion ofnF       section numbers to hyperlinks inside a TABLE to be switched off 2       independently form the rest of the document.  H       By default this policy is disabled.  Users should only switch thisI       behaviour on if they have a table of section numbers (such as this  %       document has in 11.1 and 11.2).e    % 6.3.7.12 Other table related policies   H       Also relevant to table production are policies which influence the(       detection of pre-formatted text :-  4       - "Minimum automatic <PRE> size" (see 6.2.4.1)?       - "Minimum TABLE column separation" (see 6.2.4.2 and 7.4).4       - "Expect sparse tables" (see 6.2.4.3 and 7.4)     6.3.8 Link Dictionaryt  +       Link definitions appear as follows :-      	[Link Dictionary]       	-----------------S       	Link definition       :  "A2HDOCO.TXT" = "Source text" + "/~jaf/A2HDOCO.TXT"     K       That is, the text to be matched, the text to be used in its placed asdN       the highlighted text, and the URL this link is to point to (in this case       a relative URL).  /       See the discussions in 4.3.2.2 and 4.4.2.      6.3.9 Directory Page  G       AscToHTM has the following policies that can be used to influence G       whether or not AscToHTM will attempt to generate a Directory page J       for the files being converted.  This is really only appropriate when7       converting more that one file at once (see 4.3.3)n  D       The Directory Page will consist of entries for each file beingH       converted (in order of conversion), and can have hyperlinks to theM       files, and to recognised headings in the files.  This makes it suitableoG       for use as a master index to a set of files converted in a singlea       directory.         	[Directory]:       	---------------------------------------------------+       	Make Directory                   Yes .       	Directory filename               (none)+       	Show file titles in Directory    Yeso+       	Indent headings in Directory     Yes 5       	Directory title                  List of filest.       	Directory keywords               (none)C       	Directory description            Directory index of my fileso7       	Directory return hyperlink text  Return to indext*       	Directory Script file      	 (none).       	Directory header file            (none).       	Directory footer file            (none)   6.3.9.1 "Make Directory"  K       This policy specifies whether or not you want a Directory page built.o     6.3.9.2 "Directory filename"  J       This policy specifies the name of the Directory page html file to be       created.  K       If omitted, this will default to "index.html" in the output directoryi    ' 6.3.9.3 "Show file titles in Directory"   I       This policy specifies whether or not there should be a hyperlink toDI       the top of each file converted (as opposed to just their contents).r  G       If selected, the HTML file's title (see 5.6.1) will be shown as atH       hyperlink. If the file has no title, then the original filename is       shown instead.    & 6.3.9.4 "Indent headings in Directory"  J       This policy specifies whether or not the contents lists of each fileK       should be shown at multiple indent levels, with sub-sections indentedb       relative to sections etc.n  N       If disabled, all the contents hyperlinks will be at the same indentation5       level, one level in from any file titles shown.      6.3.9.5 "Directory title"o  K       This specifies the text to be used as the HTML title of the Directoryi       page.        6.3.9.6 "Directory keywords"  D       This policy allows you to specify keywords that are added to aE       META tag inserted into the <HEAD> section of the Directory pagey       as follows :-e  =       	<META NAME="keywords" CONTENT="your list or keywords">t  L       This tag is often used by search engines when indexing your HTML page.I       You should add here any relevant keywords possibly not contained in        the text itself.     6.3.9.7 "Directory description".  F       This policy allows you to specify a description of your documentI       that is added to a META tag inserted into the <HEAD> section of thea%       Directory page(s) as follows :-i  ;       	<META NAME="description" CONTENT="your description">   J       This tag is often used by search engines (e.g. AltaVista) as a briefI       description of the contents of your page.  If omitted the first fewhC       lines may be shown instead, which is often less satisfactory.e    ) 6.3.9.8 "Directory return hyperlink text"e  I       This policy specifies the text to be shown on the hyperlink linking 0       each HTML page back to the Directory page.  &       The default value is "Directory"     6.3.9.9 "Directory Script file"s  L       This identifies the name of a text include file to be transcribed into@       the <HEAD> ... </HEAD> portion of the generated HTML page.  K       This allows you to place JavaScript in your pages (though you'll be ay/       little limited as to what it can act on).   J       If omitted, this will default to any script file used in the rest ofK       the HTML pages as set by the "HTML Script file" policy (see 6.3.1.6).f      6.3.9.10 "Directory header file"  L       This identifies the name of a text include file to be transcribed intoG       the HTML file at the top of the <BODY> ... </BODY> portion of thec       Directory page.e  J       If omitted, this will default to any header file used in the rest ofK       the HTML pages as set by the "HTML header file" policy (see 6.3.1.7).       6.3.9.11 "Directory footer file"  L       This identifies the name of a text include file to be transcribed intoJ       the HTML file at the bottom of the <BODY> ... </BODY> portion of the       generated HTML page.  F       This can be used to add "return to home page" links, and contact#       addresses to your HTML pages.e  J       If omitted, this will default to any header file used in the rest ofK       the HTML pages as set by the "HTML header file" policy (see 6.3.1.8).e    % 6.4   Saving and loading policy filess   6.4.1 Overview u  H       AscToHTM allows you to save policies to file so that you can laterC       reload them.  This allows you to easily define different waysIF       of doing conversions, either for different types of files, or to(       produce different types of output.  G       The policy files have a .pol extension by default, and are simpleiF       text files, with one policy on each line.  You can, if you wish,F       edit these policies in a text editor... this is sometimes easier8       that using all the dialogs in the Windows version.  I       When editing policies, it is important not to change the key phraseuM       (the bit before the ":" character), as this needs to be matched exactlye       by AscToHTM.  G       For best results, it is advisable to put in your policy file only H       those policies you want to fix.  This leaves AscToHTM to calculateH       document-by-document policies that suit the files being converted.  F       Note:	Avoid using "full" policy file for your conversions.  Such?       		files prevent the program from adjusting to each sourcet0       		file, often leading to unwanted results.    / 6.4.2 Generating policy files for your document   K       The normal way to create a policy file is by setting options and themrK       saving them using the "save policy file" dialog.  This will offer yousH       the choice of creating a partial policy file or a full policy file        (see 6.4.2.1 and 6.4.2.2).       O       Alternatively, you can set the "Output policy file" policy (see 6.3.3.11)dH       which will generate a full policy file resulting from the analysis        of the converted document.  K       Once a file is generated you can either edit them in a text editor -  M       deleting policies that are of little interest to you, and editing thosetL       that are - or reload them into the program, change them and save them        again.     6.4.2.1 Partial policy files  I       Partial policy files are files which have values for some, not all,>       policies.d  I       These are recommended, because the unstated policies can be set by kI       AscToHTM, allowing it to adapt to the details of the document beingo       concerned.  K       For example, you should only set the indentation policy if you *know*eM       what indents you are using, or if you want to override those calculatedhF       by AscToHTM.  Normally it is best to omit this policy, and allow%       AscToHTM to work it out itself.o  M       When you save a policy file from inside AscToHTM, a partial policy file        will contain  B       	- all policies loaded from the current policy file (if any)M       	- all policies changed in AscToHTM during the current session (if any)n     6.4.2.2 Full policy files   F       A "full" policy file contains a value for every possible policy.G       Such files are usually only useful for documentation and analysisiJ       reasons, and should almost never be expected to be reloaded as inputJ       into a conversion, as this would totally fix the conversion details.          6.4.3 Naming policy files   I       Whenever the "Output policy file" policy is set (see 6.3.3.11), thes4       generated "full" policy file is usually called         	<filename>.pol   H       where <filename> is the name of the file being created.  When thisA       happens any existing file of that name will be overwritten.t  K       For this reason we *strongly* advise you adopt a naming convention of        the form  +       	in_<filename>.pol or i<filename>.polf  K       or place your input policies in a different directory and ensure theya       are backed up.     $_$_TABLE_WIDTHr   7     Using the preprocessor ----------------------------  I       The preprocessor is introduced in version V1.05.  It is intended toiI       allow users more flexibility in the HTML they generate, and as such.I       moves AscToHTM towards being a HTML authoring tool, as opposed to afG       simple text conversion or migration tool.  This wasn't AscToHTM's I       original purpose, and so - as yet - it's a little functionally poor        in this area.l  K       Likely future additions include the insertion of embedded HTML in theo=       output code.  This would allow pictures to be embedded.t  J       The preprocessor looks for lines that begin with a special characterL       sequence.  Presently this is "$_$_", but this will become configurable       in later versions.  G       Preprocessor lines are not normally output to the HTML generated.eO       Instead they are used to modify AscToHTM's behaviour in a number of ways..    ! 7.1   Marking up sections of textx  M       The pre-processor can be used to mark sections in your document so thate-       AscToHTM will process them as you wish.r  B       Note:	AscToHTM does attempt to spot such user-formatted text@       		automatically, but this is a difficult area and prone to@       		error.  Hence the use of these directives can reduce the%       		error rate on such occasions.h     7.1.1 User SECTIONSw  I       This directive is used to divide the document up into named sectionLJ       types.  Section type names can be repeated through the document, andE       by default text is assumed to belong to a section called "all",nD       indicating that this text is always copied to the output file.  5       Section type names must contain no white space.   J       This has no effect unless the user supplies a policy file indicatingE       that they wish to select only certain section types for output.o  7       For example, if the text document looks like thisg  
 $_$_BEGIN_PREr@       		Some text that'll always get copied, because it is in an&       		"all" section type by default.         	$_$_SECTION Private  B       		Some text that will be copied either when the preprocessorA       		is switched off, or when the user's policy file indicatess8       		that "private" section types are to be included.         	$_$_SECTION Other  2       		Likewise, this is an "other" section type.         	$_$_SECTION Private  ,       		And here's some more "private" text.         	$_$_SECTION all  F       		Some text that will always get copied because it is explicitly!       		in an "all" section type.e $_$_END_PRE   I       If the user then supplies a document policy file which includes the        lines (see 6.3.5)l         	[Preprocessor]b       	-------------- )       	Use Preprocessor             : Yes   J       then the two section types marked "private" won't be copied into the$       converted file unless the line    /       	Include document section     :   Private     G       is added to the policy file.  Similarly with the "other" section.-  G       Note_1:	Strictly speaking the "use preprocessor" line above isn't C       		needed as this is set to "yes" by default.  This means thateB       		any $_$_SECTION lines will cause text to be omitted unless.       		you supply an appropriate policy file.  F       Note_2:	Be aware that any sections omitted are also omitted from?       		the analysis pass.  This may have unexpected results asu>       		AscToHTM responds only to the input text that is to be       		included in the output.o     7.1.2 TABLE sections  D       The BEGIN_TABLE ... END_TABLE directives are used to bracket aK       table in the source text.  AscToHTM will then attempt to analyse thiso       table as best it can.E  4       This is explained more in the [AscToTab Doco].  H       Inside this section you can use other TABLE pre-processor commands-       to tailor the HTML generated (see 7.4).e  C       The presence of this directive overrides any value set in thes5       "Attempt table generation" policy (see 6.3.7.1)      7.1.3 CONTENT sections  J       The BEGIN_CONTENTS ... END_CONTENTS directives are used to bracket a!       contents list in the source K       document.  AscToHTM will attempt to automatically detect the presence J       and location of any contents list in the document, but the algorithm       can be problematic.l  J       Use this markup only when the document contains a contents list that)       AscToHTM fails to detect correctly.   "       See the discussion in 5.6.2.     7.1.4 HTML sectionsM   $_$_BEGIN_HTML>       <IMG SRC="a2hdoco1.jpg" NAME="home" BORDER=0 ALIGN=RIGHT+        HEIGHT=160 WIDTH=160 ALT="AscToHTM">e $_$_END_HTML  G       The BEGIN_HTML ... END_HTML directives are used to bracket actuald"       HTML in the source document.L       The bracketed HTML will be transcribed to the output file unconverted.  G       This device will allow you to embed images, tables and other HTML 4       constructs not normally generated by AscToHTM.  8       This is how the image to the right has been added.  G       If you simply wish to insert a single line of HTML, the HTML_LINEs5       command (see 7.3.2) offers a more compact form.      7.1.5 CODE sectionsD  H       The BEGIN_CODE ... END_CODE directives are used to bracket a piece(       of sample code in the source text.  D       AscToHTM will either render this in <PRE> ... </PRE> markup orF       <CODE> ... </CODE> markup (see 6.3.6.11).  For reasons discussed(       in 6.3.6.11 the former is default.     7.1.6 DIAGRAM sections  N       The BEGIN_DIAGRAM ... END_DIAGRAM directives are used to bracket a piece6       of Ascii art or text diagram in the source text.  ;       AscToHTM will render this in <PRE> ... </PRE> markup.a    ' 7.1.7 PRE (pre-formatted text) sectionst  F       The BEGIN_PRE ... END_PRE directives are largely replaced by theL       TABLE, CODE and DIAGRAM directives.  They are maintained for backwardsE       compatability, and have the same effect as the DIAGRAM commandsf       (see 7.1.6).    ; 7.2   Commands that influence the <HEAD>..</HEAD> of a file    7.2.1 The TITLE commandc  P       This directive allows you to specify the <TITLE>...</TITLE> to be insertedL       into the <HEAD> section of the output page.  This title will appear inL       the browser's frame title whenever the page is viewed, and will be the+       text shown in your browser's history.t  F       The presence of a TITLE command overrides any title specified in7       a policy file (see 6.3.1.1, 6.3.1.2 and 6.3.1.3).o  P       To fully understand how titles are calculated, see the discussion in 5.6.1     7.2.2 The DESCRIPTION command   I       This directive allows you to specify a description of your documentaI       that is added to a META tag inserted into the <HEAD> section of theu"       output page(s) as follows :-  ;       	<META NAME="description" CONTENT="your description">t  J       This tag is often used by search engines (e.g. AltaVista) as a briefI       description of the contents of your page.  If omitted the first few C       lines may be shown instead, which is often less satisfactory.E  G       The presence of a DESCRIPTION pre-processor command overrides any ;       description specified in a policy file (see 6.3.1.5).n     7.2.3 The KEYWORDS command  G       This directive allows you to specify keywords that are added to aO=       META tag inserted into the <HEAD> section of the outputo       page(s) as follows :-   =       	<META NAME="keywords" CONTENT="your list or keywords">n  L       This tag is often used by search engines when indexing your HTML page.I       You should add here any relevant keywords possibly not contained ine       the text itself.  M       The presence of a KEYWORDS pre-processor command overrides any keywords /       specified in a policy file (see 6.3.1.4).e     7.2.4 The STYLE_SHEET commando  I       This directive allows you to specify the URL of a style sheet file,wN       usually with a .css extension.  Style sheet files are a new HTML featureN       that allow you specify fonts and colours to be applied to your document.  J       The resulting HTML is inserted into the <HEAD> section of the output       page(s) as follows :-l  9       	<LINK REL="STYLESHEET" HREF="URL" TYPE="text/css">-  L       The presence of a STYLE_SHEET pre-processor command will overrides any;       style sheet specified in a policy file (see 6.3.6.1).     % 7.3   One line pre-processor commands    7.3.1 The INCLUDE commandr  J       This directive allows you to specify the name of a source file to beL       included at this point.  This is useful if you wish some standard textI       inserted into many related documents, or into the same documents atn       many locations.c  N       The included file will be treated as though it were part of the original6       file during both the analysis and output passes.  G       The include will fail is the fail cannot be found, and a test fori+       recursive include files will be made.f     7.3.2 The HTML_LINE commandc  M       This directive allows you to embed a single line of HTML in your sourceoK       file.  The rest of the line is copied across faithfully to the output.       file.t  L       Essentially this offers the functionality as the HTML section commands.       (see 7.1.4), but in a more compact form.     7.4   The TABLE commands  J       These directives are used to tailor the HTML generated in any tables/       AscToHTM creates.  They are placed eithern  !       a) *At the top of the file*s  J       	Directives placed here become defaults for the whole file, and will;         replace any policies that have been set (see 6.3.7)   5       b) *Inside a BEGIN_TABLE ... END_TABLE section*t  G       	Directives placed here will apply only to the table marked up byb"       	these commands (see 7.1.2).  J       The table commands are described (naturally enough) in the following       table.  5 $_$_CHANGE_POLICY Convert TABLE X-refs to links : Yes  $_$_BEGIN_TABLE  Directive			Value    Effect P --------------------------------------------------------------------------------; TABLE_BORDER            	Number   Size of border.  0 = Nonee  2 TABLE_BORDERCOLOR       	Colour   Colour of border  6 TABLE_BGCOLOR           	Colour   Colour of background  : TABLE_CAPTION			Text     Table caption.  Added centred at 0                                          the top  8 TABLE_CELLSPACING       	Number   Spacing between cells.  : TABLE_CELLPADDING       	Number   Padding inside each cell  O TABLE_CONVERT_XREFS             (none)   If present, indicates that any section J                                          cross-references in the table mayD                                          be converted to hyperlinks 7                                          (see 6.3.7.11)e  ? TABLE_HEADER_ROWS       	Number   Number of header rows.  ThesetO                                          will be placed in <TH> .. </TH> markups  B TABLE_HEADER_COLS               Number   Number of header columns.H                                          These will be marked up in bold  M TABLE_MAY_BE_SPARSE             (none)   If present, indicates that the TABLE D                                          may be sparse (see 6.2.4.3)  J TABLE_MIN_COLUMN_SEPARATION     Number   Number of spaces to be taken as aL                                          column separator when analysing the=                                          table (see 6.2.4.2).g  G TABLE_WIDTH             	Text     The width of the table (see 6.3.7.10)f  
 $_$_END_TABLEl    A       Colours must be in the HTML accepted format (see 6.3.1.10).a     7.5   The CHANGE_POLICY commandy         *New in V3.0*.  U       NOTE: 	*This feature has the potential to cause mayhem, and as such is offered oO       		to users on a "as is" basis.  That is, we offer no support for getting r;       		this feature to have the effect a user may desire*.s  H       This directive allows you change a particular policy in part of a O       document.  This is a potentially powerful feature, allowing you to tailoroJ       the conversion of your file *in different sections of that file*, orN       to embed the policy particular to a file in commands inserted at the top       of the file itself.   '       The syntax of the command line is   &       	$_$_CHANGE_POLICY <Policy Line>  O       where <Policy_line> is a policy line as it would appear in a policy file,hM       and (usually) as it appears in sections 11.1 and 11.2 of this document.   =       For example the following would all be valid directives   
 $_$_BEGIN_PREv0       	$_$_CHANGE_POLICY Background Colour : red:       	$_$_CHANGE_POLICY Ignore multiple blank lines : Yes $_$_END_PREo       M       Although how and when they would take affect will depend on the policy.o  M       For example, the background colour would only take effect if splitting sM       the file up, and only on the next file generation.  This works, BTW, sopM       if anyone wants to split a file into many pages, all different colours,        then be my guest.e       5       There are a *many* caveats to this behaviour :-o  (       - *Not all policies are supported*  K       	Not all policies may be changed in this way.  In particular policies H       	that open other policy files are not supported.  Even if a policyJ       	if "changed", it does not follow that changing the policy will have       	an effect.x         - *analysis policies*u  M       	It is unlikely that this feature can be sensibly used to influence the L       	analysis of file, other than when placed at the top of the file only.H       	If such a manner it is simply an alternative to using a separate        	policy file.n         - *output policies*a  N       	Output policies are referenced at different times.  Only those that areF       	referenced *after* the line is read from the source file may beH       	influenced, thus things like output file name may have no effect.         - *toggleable policies*c  D       	Not all policies once changed, can be changed back.  This is J       	particularly of policies that contain values to be added to a list.@       	This is an issue that may be addresses in later versions.       	e!       - *unpredictable behaviour*   L       	Messing with policies can cause unpredictable behaviour.  For exampleL       	if you alter the section splitting parameters, then the chances of a I       	section cross-reference elsewhere in the document being calculated )       	as a correct hyperlink diminishes.t  7       	*That's why this feature is offered UNSUPPORTED*a         - *readahead buffer*  M       	To further complicate matters, AscToHTM uses a readahead, write behindTJ       	buffer which means that you may need to experiment with the placingI       	of your policy change to within 40 lines (the size of the buffer).y     8     Purchasing AscToHTMy -------------------------t  % 8.1   Why should I purchase AscToHTM?A  ;       You need a reason?  What kind of a skinflint are you?     5       Oh well... here are some reasons to register :-   F       - You'll get a warm glow from supporting the author financially.         Not enough eh?  Okay...d  L       - You'll get support from the author, especially in your early days as       	a new user.  K       - You'll be notified of any upgrades.  To date all upgrades have beeniM         *free* to _registered_ users.  This means people who paid last year'sl;       	price are getting this years software at a discount.s  L       - You'll be able to ask the author for new features.  You won't alwaysN         get them, but you'd be *amazed* at how much of the functionality arose8         directly from _registered_ users party requests.         Finally...  K       - No nag lines at top and bottom of each page, and no nag screen whena!         you start the program up.i  B       - All limitations on the program (file size etc) are removed    I 8.2   What happens if I don't register the shareware version of AscToHTM?o  G       Originally I wanted to produce a fully-featured, but time-limited_H       shareware version.  However, for various reasons we've had to moveO       to move to producing a largely-featured version with a 30 day time limit.T         Sorry 'bout that.o  J       At present the shareware version of the program comes with an expiryL       date (usually 30 days after installation).  Each time the program runsJ       it will tell you how may days left you have.  During this period theK       program inserts a one line reminder to register at the top and bottom "       of each HTML page generated.  L       This line is easily deleted from the output source file, but we expectE       this to become quite tedious if the program is used repeatedly,eH       particularly when large documents are split into a number of smallO       files, or a large number of files are being converted.  *Some people havea*       actually put such pages on the web*.  =       There are other limitations of the shareware version :-.  J       - If you don't register, it will cease to function properly after 30J         days.  Specifically after 30 days any conversions will convert allL         your text to random case.  This will still allow you to evaluate theF         software, but the resulting HTML will be of little use to you.  N       - In the shareware version you're limited to only the first 500 lines ofD         any source file.  After 500 lines a warning is placed in theL         output, and all subsequent lines are converted to random case.  ThisK       	allows you to gain an impression of what the HTML will look like ford       	evaluation purposes.e  B       - In the shareware version, wildcard conversions are limited       	to only 5 files  J       - Certain other policies are not supported in the shareware version.  ;       I don't like limiting the software, but there you go.h    ( 8.3   Can't I get something for nothing?  C       Only if you fall into either of the following two categories:s  H       - You're an FAQ maintainer.  FAQ maintainers add a lot of value toG         the Internet.  As a little "thank you" I'm making this softwareoH         free to anyone who maintains an FAQ.  See the [Reg location] for         more details.n  K       - VMS users.  The software is largely developed and tested under VMS. I         Although the VMS version doesn't have the windowed interface, buti6         does share the underlying conversion software.           *<SOAPBOX>*cN         We VMS users pay too much for software (that's when we can get it), soD         the VMS version of this software is made available for free.         *</SOAPBOX>*  M         If you really want a free copy, buy an OpenVMS system :)  If you finds,       	any for less than $35, let me know :)    1 8.4   I'm convinced.  How to I purchase AscToHTM?e  J       First we recommend you try out the product to convince yourself that       it meets your needs.         You've done that right?   G       Okay, visit the [Reg location] and follow the instructions there.pH       You can buy AscToHTM online using credit cards, or via snail mail.M       Credit cards are processed by a third party who contact us once paymentd       is cleared.l  I       If you experience any problems registering email jaf@yrl.co.uk withhH       details.  Currently most registrations result in an email from Jaf
       anyway..     9     Contacts on the Web  -------------------------e   9.1   The home pagee  K       At time of writing [Yezerski Roper] (whom I work for) have graciouslya0       allowed me to give AscToHTM a [Home page].  A       Yezerski Roper are the most intelligent software house it's	J       ever been my privilege to be associated with.  We're based in the UKA       and offer OpenVMS and Windows NT systems, and are currently E       developing state-of-the-art products which will allow companieseC       to exploit the full communications potential of the Internet.   +       Oh yeah... and they pay me as well :)   K       If you have problems locating the home page and suspect it has moved,s!       go to [AltaVista] and enterT  (       		+"John A Fotheringham" +AscToHTM  "       to locate any new home page.     9.2   E-mail  K       E-mail any feedback to jaf@yrl.co.uk.  Sadly, we cannot guarantee anysM       replies. OTOH, no-one who has ever emailed us has ever waited more than 3       a day for a response (no holidays, you see :)A    
 9.3   Supportt  E       A limited amount of support is available to registered users bysK       emailing jaf@yrl.co.uk.  Any enquiries should be directed to the same        address.  M       Sadly, we cannot guarantee any replies, though we do try to be helpful.e=       Priority is given to people who have registered copies.   H       Over time a user's FAQ may appear.  This will only be available to       registered users.      10     Known problems= ---------------------T  J       We listen to all suggestions, and indeed many of the features added H       have been in direct response to customer feedback.  (You couldn't H       expect us to *invent* all this stuff on our own now, could you? :)     10.1  Bug reports   I       _Registered_ users are free to make bug reports or suggestions for  K       enhancements to jaf@yrl.co.uk.  We try to fix bugs ASAP, and to date  M       have usually shipped fixes to specific problems within 72 hours, but we '       can't promise this response time.O  M       We used to maintain a bug list, but we prefer spending the time fixing a(       them rather than documenting them.     10.2  Features  5       All good software has features (ask Microsoft).r  G       - Links in the link dictionary that have some common text may get E         confused.  The problem generally is that having put some HTML H       	markup into your line, it becomes hard not to search the contents#       	of that markup subsequently.m  E       	This is my problem not yours.  Unless it catches you out when,E4       	of course, it becomes your problem, not mine.  H       - If the program gets confused when splitting a large file, it mayI         accidentally use the same output file name twice, possibly losingr         your data.  J       - Bullet characters inside section headings used to cause confusion.  F       The following are consequences of how the program works, and may       take longer to "fix"  I       - The program currently assumes a structure of contents list and/or F       	main body.  It doesn't (yet) cope with Appendices.  Nor does itG       	cope with several sections all with their own numbering systems.e  J       - Certain algorithms put a <BR> on the end of the line.  Where theseO       	algorithms "misfire" you may find unexpected breaks in large paragraphs.   L       	Over time more of these will be configurable via the document policy,H       	but originally we tried to avoid the need for such micro-control.     10.3   Coming soon... or not.a  G       An on-line [wishlist] is now maintained.  However, it's not kept iM       wonderfully up to date, and a *lot* of features have fast-tracked theirEE       way into the software without ever being mentioned on the list.   N       Many, many features have been added in direct response to (_registered_)E       users requests.  Many, thanks to all those who've come up with s:       suggestions and feedback (you all know who you are).       11 Policy Dictionary --------------------  J Here is a complete list of all the policy phrases that may occur in policy) files, and links to their explanations :-s     11.1 Analysis policies  N These policies influence AscToHTM's analysis.  Usually AscToHTM will calculateI values for each of these policies, or use sensible defaults.  Should the dO analysis be wrong for any reason, you can change these policy values to correctg the conversion.g    < Descriptive text                 Reference            ValuesA -----------------------------------------------------------------sI Bullet Char                      5.1.3.1 and 6.2.2.4  '-'  (one entry perc@                                                       character)B Definition Char                  5.1.5 and 6.2.1.3    '-' (strong)< Expect alphabetic bullets        5.1.3.3 and 6.2.2.2  Yes/No< Expect blank lines between paras 6.2.1.8              Yes/No< Expect Capitalised Headings      5.4.2 and 6.2.3.4    Yes/No= Expect code samples              6.2.1.13, 6.3.6.11    Yes/No *                                  and 7.1.5< Expect Contents List             3.3.2, 4.2.2.1,      Yes/No2                                  4.4.3 and 6.3.4.2< Expect Numbered bullets          5.1.3.2 and 6.2.2.1  Yes/No< Expect Numbered Headings         5.4.1 and 6.2.3.2    Yes/No< Expect Roman Numeral bullets     5.1.3.4 and 6.2.2.3  Yes/No< Expect Second Word Headings      -                    Yes/No< Expect sparse tables             6.2.4.3 and 7.4      Yes/No< Expect Underlined Headings       5.4.3 and 6.2.3.3    Yes/NoG Hanging paragraph position(s)    5.1.2 and 6.2.1.4    List of ascendingbM                                                       space-separated numbersaG Indent position(s)               6.2.1.1              List of ascendingtM                                                       space-separated numbers.< Keep it simple                   4.2.2.4 and 6.2.1.10 Yes/NoE Min chapter size                 6.2.1.11             Number of linesfE Minimum automatic <PRE> size     5.5.3 and 6.2.4.1    Number of lines F Minimum TABLE column separation  6.2.4.2 and 7.4      Number of spaces< Search for Definitions           6.2.1.2              Yes/No< Search for emphasis              6.3.6.9              Yes/NoJ Short line length                6.2.1.12             Number of charactersJ TAB size                         6.2.1.6              Number of charactersG Text Justification               6.2.1.7              left/right/centrei     11.2 Output policies  K These policies are used to shape the HTML generated.  You can change these D? policies to get the HTML generated looking like you want it to.     < Descriptive text                 Reference            ValuesA -----------------------------------------------------------------_A Active Link Colour               6.3.1.10             HTML Colour < Add <BR> to lines with URLs      6.3.2.7              Yes/No< Add contents list                3.3.2, 4.2.2.1       Yes/No0                                  4.4.3 and 6.3.4< Add navigation bar               6.3.3.10             Yes/No< Allow automatic centring         5.3.9 and 6.3.6.4    Yes/No< Allow definitions inside PRE     5.1.5 and 6.3.6.10   Yes/No< Attempt TABLE generation         6.3.7.1              Yes/No@ Automatic centring tolerance	 6.3.6.5	      Number of charactersA Background Colour                6.3.1.10             HTML Colour B Background Image                 6.3.1.9              URL of image< Convert TABLE X-refs to links    6.3.7.11 and 7.4     Yes/No< Create NEWS links                5.3.4 and 6.3.2.3    Yes/No< Create hyperlinks                5.3.3 and 6.3.2.1    Yes/No< Create mailto links              5.3.5 and 6.3.2.2    Yes/NoH Cross-refs at level              5.3.2 and 6.3.2.6    Number. 0 = "none"L DOS filename root                4.2.2.3, 4.3.2.4     up-to-5 character name,                                  and 6.3.3.5A Default TABLE border colour      6.3.7.8 and 7.4      HTML Colour M Default TABLE border size        6.3.7.2 and 7.4      Number. 0 = "automatic" A Default TABLE caption            6.3.7.9 and 7.4      Text String H Default TABLE cell padding       6.3.7.6 and 7.4      Number. 0 = "none"H Default TABLE cell spacing       6.3.7.5 and 7.4      Number. 0 = "none"A Default TABLE colour             6.3.7.7 and 7.4      HTML Colour M Default TABLE header cols        6.3.7.4 and 7.4      Number. 0 = "automatic"oH Default TABLE header rows        6.3.7.5 and 7.4      Number. 0 = "none"K Default TABLE width              6.3.7.10 and 7.4     Table width in pixelshP                                                       or as a percentage of page;                                                       width A Directory description            6.3.9.7              Text String E Directory filename               6.3.9.2              Output filename O Directory footer file            6.3.9.11             File name.  File contains C                                                       HTML commandsrA Directory keywords               6.3.9.6              Text StringeO Directory header file            6.3.9.10             File name.  File containsiC                                                       HTML commandsiA Directory return hyperlink text  6.3.9.8              Text StringnO Directory Script file            6.3.9.9              File name.  File containsoC                                                       HTML commandsRA Directory title                  6.3.9.5              Text StringAM Document Style Sheet             6.3.6.1 and 7.2.4    URL of style sheet fileuA Document description             6.3.1.5 and 7.2.2    Text string J Document keywords                6.3.1.4 and 7.2.3    Comma-separated listA Document title                   6.3.1.1 and 7.2.1    Text stringsJ Error reporting level            6.3.3.14             Number in range 1-10? External contents list filename  6.3.4.5              File namer< Generate diagnostics files       4.2.2.2 and 6.3.3.13 Yes/No< Generate external contents file  6.3.4.4              Yes/NoA Headings colour                  6.3.6.7              HTML ColourrO HTML Script file                 6.3.1.6              File name.  File containsnC                                                       HTML commands O HTML footer file                 6.3.1.8              File name.  File containsiC                                                       HTML commandspO HTML header file                 6.3.1.9              File name.  File containsnC                                                       HTML commandso< Highlight Definition Text        5.1.5.1 and 6.3.6.2  Yes/No< Hyperlinks on numbers            5.3.1 and 6.3.4.6    Yes/No< Ignore multiple blank lines      6.3.6.8              Yes/NoK Include file                     4.3.2.3              Name of a policy fileiD                                                       to be includedM Include document section         6.3.5.2 and 7.1.1    Space-separated list oflC                                                       section names.< Indent headings in Directory     6.3.9.4              Yes/NoD Input directory                  6.3.3.1              Directory name< Make Directory                   6.3.9.1 and 4.2.2.6  Yes/NoE Min HTML File size               6.3.3.9              Number of linesi< Minimise HTML file size          6.3.3.7              Yes/No< Only use known groups            5.3.4 and 6.3.2.4    Yes/NoD Output directory                 6.3.3.2              Directory nameA Output file extension            6.3.3.4              Text Stringt< Output policy file               4.2.2.5 and 6.3.3.11 Yes/No? Output policy filename           6.3.3.12             File name M Recognised USENET groups         6.3.2.5              space-separated list ofhH                                                       USENET hierarchies< Search for emphasis              6.3.6.9              Yes/No< Show file titles in Directory    6.3.9.3              Yes/No< Split level                      3.3.3 and 6.3.3.8    NumberA Text Colour                      6.3.1.10             HTML Colour A Unvisited Link Colour            6.3.1.10             HTML ColourT< Use .HTM extension               6.3.3.3              Yes/No< Use <CODE>..</CODE> markup       6.2.1.13, 6.3.6.11   Yes/No*                                  and 7.1.5< Use <DL> markup for defn. paras  5.1.5.2 and 6.3.6.3  Yes/No< Use <P> markup for paragraphs    6.3.6.12             Yes/No< Use any existing contents list   6.3.4.3              Yes/No< Use DOS filenames                4.3.2.4 and 6.3.3.5  Yes/No< Use first heading as title       6.3.1.2              Yes/No< Use first line as title          6.3.1.3              Yes/No< Use Preprocessor                 6.3.5.1 and          Yes/No,                                  [Section 7]A Visited Link Colour              6.3.1.10             HTML Coloure       12    Change History --------------------   12.1  Version 1.01 (April '97)         New functionso  5       - Added the /CONTENTS qualifiers (see 4.2.2.1).   2       - Added the /SIMPLE qualifier (see 4.2.2.4).  # 12.2  Version 1.04 (early July '97)i   12.2.1 Bug fixes  "       - Fixed lots of memory leaks  H       - Improved cross-reference detection.  These are now range checkedN         against the observed section numbers.  This will reduce the likelyhoodJ         of DirectX 3.0 and Windows 95 becoming links to chapters 3 and 95.  O       - Contents list generation for documents with chapters and no subsectionsb         now works.  )       - Improved Contents list detection.s  H       - Fixed bug that caused links to underlined or capitalised heading/         with very long names to sometimes fail.o   12.2.2 New functions  H       - Added policy "Minimum automatic <PRE> size" (see 6.2.4.1).  This3 	replaces the policy "Allow automatic 1-line <PRE>"n  H       - Added policies "Largest  allowed <Hn> tag" and "Smallest allowedA  	<Hn> tag" (see 6.3.6.6) to allow control over generated headingi 	sizes.t  7       - Added policy "Short line length" (see 6.2.1.12)l  I       - Added Batch processing to allow multiple files to be converted ati$         the same time. (see 4.3.3.2)   12.2.3 Other changes  $       - Created a 16-bit DOS version  .       - VMS version now available as freeware.  B       - Added "SendTo" tips for Windows 95/NT users section to the!         documentation (see 4.4.4)l      ! 12.3 Version 1.05 (late July '97)    12.3.1 Bug fixes  F       - fixed some errors that occur when directory paths are includedM         in the filenames.  Probably still more changes required in this area, G       	particularly with a view to supporting multiple file drag'n'drope       	under Windows.   4       - improved detection of pre-formatted regions.   12.3.2 New functions  F       - Added an "Output directory" policy (see 6.3.3.2).  This allowsD 	redirection of output to a directory different from that containing 	the source files.  1 	Note:	This functionality may not be available inr( 		the shareware version of the software.  H       - Added an "Output policy" policy (see 6.3.3.11).  This allows the5 	suppression of output policy files where not wanted.   K       - Added a "Expect code samples" policy (see 6.2.1.13).  This helps ino;         technical documents that include samples of C code.P  C       - Added preprocessor support to allow variant documents to bec+       	produced (see 6.3.5 and [section 7])i   12.3.3 Other changes  J       - Policies now accept "Yes/No" as well as "True/False".  "Yes/No" is* 	now the default when outputting policies.  M       - shareware version now limited to processing the first 500 lines only.r  K       - Lines with email addresses no longer have <BR>'s forced on the end.eG         Lines with http, ftp and news links still do.  This will becomet-         fully configurable in later versions.f     12.4 Version 1.1 (August '97)    12.4.1 Bug fixes  F       - Several hyperlink parsing errors fixed.  Previously there wereD         problems with punctuation around links, email addresses withC         protocols (e.g. MX%"jaf@yrl.co.uk") and newsgroups with thel0         word "news:" in front e.g. news:uk.jobs.  K       - improved output of pre-formatted text.  "<" characters were getting G         confused, and the pre-formatted lines were being broken in two.    12.4.2 New functions  P       - Added a "Only use known groups" policy (see 6.3.2.4) to improve accuracy(       	of newsgroup hyperlink detection.  :       - Added more document colour policies (see 6.3.1.10)  F       - Added a /POLICY and "Output Policy file" option (see 6.3.3.11 M         and 4.2.2.5) to make the generation of an output policy file optionald  J       - Added preprocessor support for user-formatted sections (see 7.1.7)   12.4.3 Other changes  :       - Indentation is now done using <BLOCKQUOTE> markup.  B       - Changed default background colour to white (see 6.3.1.10).  E       - Generation of a .pol file is no longer default (see 6.3.3.11 H         and 4.2.2.5)  N       - The use of <PRE> ... </PRE> to mark up user-formatted text is replacedJ         by the new preprocessor commands BEGIN_PRE and END_PRE (see 7.1.7)         - re-write of section 4.1a  F       - Improved error reporting.  The .LIS file created if the /DEBUGN         qualifier is used (see 4.2.2.2) now has error and information messages         included in it.k      12.5  Version 2.00 (October '97)  J       Version 2.0 marks the production of the first fully-windowed versionJ       for Windows 95/NT.  This took a few months to be produced, so a fair>       number of other features have been added over this time.   12.5.1 Bug fixes  C       - Loads of bugs in parsing user PRE sections (sorry Dennis!).-  L       - < and > characters inside a PRE section caused characters to be lost         off the end of lines         - URL-parsing improved  L       - Contents list file links back to main file if no other section links
 	generated  2       - Newsgroups in headings no longer converted     12.5.2 New functions  9       - New "Output policy filename" policy (see 6.3.3.1).  5       - New "Use .HTM extension" policy (see 6.3.3.3)e  >       - New "Generate diagnostics files" policy (see 6.3.3.13)  B       - New "External contents list filename" policy (see 6.3.4.5)  B       - New "Use <DL> markup for defn. paras" policy (see 6.3.6.3)  :       - New "Ignore multiple blank lines" policy (6.3.6.8)  6       - New "Search for emphasis" policy (see 6.3.6.9)  @       - New "Allow definitions inside PRE" policy (see 6.3.6.10)  6       - New Pre-processor CONTENTS command (see 7.1.3)  2       - New Pre-processor HTML command (see 7.1.4)  3       - New Pre-processor TITLE command (see 7.2.1)s  5       - New Pre-processor INCLUDE command (see 7.3.1)s     12.5.3 Other changes  E       - White space immediately adjacent to PRE sections now ignored.p  H       - Changed anchor names to contain no spaces (makes URL's easier to 	quote)e  I       - Title defaults to "Converted from filename" instead of "No title"          (see also 7.5)  E       - Introduced some support for use of ctrl-H (backspace) in Unixs. 	documents to underlined and highlighted words  7       - Automated "simple" file detection now attemptedu  8       - Automated "code samples" detection now attempted  5       - Some policies have been renamed as follows :-   3                 Was                             Nowi3                 ---                             --- 9       		Expect Numbered sections	Expect Numbered Headingss'       		HTML header 			HTML header filea'       		HTML footer 			HTML footer file   H       - The policy section headings have been renamed as well.  This mayL         cause "ignored policy line" messages when old policy files are used.    - 12.6 Version 2.10 (never officially released)i  H       V2.1 was never officially released, but much of this functionalityO       "crept out" as the shareware version was updated.  Some of these versionsbI       were shown as V2.01 instead of V2.1.  There's nothing like a bit ofnK       consistency (and yeah, this was *nothing* like a bit of consistency).l   12.6.1 Bug fixes  E       - Fixed "Minimum automatic <PRE> size".  Previously didn't work          at all like advertised.-  N       - Colour samples in Windowed version were being shown as gray on initial         draw and on re-draw.  N       - Anchor points added to generated contents list had their </A> missing.  2       - Fixed occasional "Invalid indent -1" error     12.6.2 New functions  O       - New "Document keywords" policy (see 6.3.1.4) and pre-processor KEYWORDS          command (see 7.2.3).  I       - New "Document description" policy (see 6.3.1.5) and pre-processore'       	DESCRIPTION command (see 7.2.2).-  A       - New "Hyperlinks on Numbers" contents policy (see 6.3.4.6)   I       - New "Document style sheet" policy (see 6.3.6.1) and pre-processor '       	STYLE_SHEET command (see 7.2.4).e       12.6.3 Other changes         _All versions_  P       - Now recognise domain names without a protocol specified (such as http://K         or ftp:// etc.) that end in standard domains (e.g. .edu, .net, .orgiI         etc) as probable FTP sites.  This allows references to sites like1<         rtfm.mit.edu to be correctly turned into hyperlinks.  6       - Some renumbering of this document has occurred  =       - Quoted text is now marked up using <em>..</em> markupx           _Windows version_   1       - Now stores data in the Registry under thesC 	HKEY_CURRENT_USER root with a "\Software\JafSoft\AscToHTM\..." key   ?       - Now supports "most recently used" lists for both policy L         files and files to be converted.  These are accessed via a drop-down 	Combo box.t  5       - Now remembers last source directory each timeaK       	the program is run.  This is used as the initial directory next time $       	the Browse button is pressed.  F       - The filenames now include the path.  This is to allow the mostE       	recently used (MRU) file drop-down list to function correctly.        12.7 Version 2.20 (Feb '98)u  O       First major release after V2.0 (when AscToHTM first went fully-Windowed).iJ       Major change this time has been the introduction of TABLE generatingI       algorithms.  These were first made available as a separate freewares       utility [AscToTab].   J       This version is reviewed by ZDNet and awarded 5-stars, their highest       award.   12.7.1 Bug fixes         - End effects now fixed.  -       - Various emphasis features eliminated.   L       - In-situ contents lists weren't getting the right file names in their* 	hyperlinks when the file was being split.  J       - Right justified numbered sections weren't being detected correctly         past section 9.   K       - No longer break long URLs over two lines.  This occasionally led tog 	hyperlinks that didn't work.i  J       - No longer generate files for underlined sections when document has9 	numbers sections as well, and is being split into files.-  J       - No longer detect pre-formatted text inside BEGIN_HTML ... END_HTML	 	section.   !       - Fixed tab conversion bug.e     12.7.2 New functions         _Table generation_  L       This is the biggest change in this version.  AscToHTM now incorporatesI       the technology first introduced in [AsctoTab].  To support this the L       detection of pre-formatted text has been improved, new policies added,*       and new preprocessor commands added.    2       	New Policies                    Description3         -------------------------------------------d.       	Attempt TABLE generation        6.3.7.1.       	Default TABLE border size       6.3.7.2.       	Default TABLE header rows       6.3.7.3.       	Default TABLE header cols       6.3.7.4.       	Default TABLE cell spacing      6.3.7.5.       	Default TABLE cell padding      6.3.7.6.       	Default TABLE colour            6.3.7.7.       	Default TABLE border colour     6.3.7.8.       	Default TABLE caption           6.3.7.9    3         New Pre-processor commands      Description 3         ------------------------------------------- -         BEGIN_CODE ... END_CODE         7.1.5r-         BEGIN_DIAGRAM ... END_DIAGRAM   7.1.6 -         BEGIN_TABLE ... END_TABLE       7.1.24+         TABLE_BORDER                    7.4 +         TABLE_BORDERCOLOR               7.4S+         TABLE_BGCOLOR                   7.47+         TABLE_CAPTION                   7.4A+         TABLE_CELLSPACING               7.4u+         TABLE_CELLPADDING               7.4 +         TABLE_HEADER_ROWS               7.4l+         TABLE_HEADER_COLS               7.4            _Other changes_   A       - Added a policy to allow <CODE> markup to be used for coden0         fragments in the document (see 6.3.6.11)  K       - Added pre-processor CODE commands to allow sections of code samples B         to be identified and distinguished from tables (see 7.1.5)  K       - Added pre-processor DIAGRAM commands to allow diagrams and sections K       	Ascii art to be identified and distinguished from tables (see 7.1.6)f     12.7.3 Other changes         _Documentation_   E       - Added the [PolDict], and renumbered the document accordingly.            _All versions_  #       - "tables/pre-formatted text"   L       - Various improvements to detecting the start and end of pre-formatted 	regions of text.m  L       - Shareware now expires after 30 days, rather than after a fixed date.  P       - Headings policies have been revised.  Still more work to be done in this       	area.  H       - Slight improvement in detection of centred text.  Still not goodB         enough to offer as a default though (too prone to errors).  <       - Added section on saving/using policy files (see 6.4)  K       - Shareware version now adds nag lines at top and bottom of the page,t          instead of just the top.  9       - A number of improvements in code sample detection3  G       - Reduced number of "error" messages reported.  These may be made3D 	optional in a later version, and are still placed in the diagnostic 	files if these are created.           _Windows version_t  O       - Now added a "Settings" dialog to allow you to configure various aspects2H         of how the program runs such as what browser to view files with,3       	what policy file to use as default etc, etc.       ! 12.8 Version 2.3 (late April '98)   O       Minor bugfixes and upgraded functionality over V2.2.  The main functional        changes have been   A       a) The introduction of wildcard support to allow conversion #          of multiple files at once.   F       b) (related to the above) the introduction of the Directory PageF          feature (see 5.6.3 and 6.3.9) that allows the generation of aD          hyperlinked document spanning all the files in a directory.  F       c) Major re-write of the contents-list generating routines.  TheK          program now makes a third, intermediate, pass through the documentiK          to analyse the contents structure.  This means that contents lists3K          are now placed at the top of the HTML file be default, rather than I       	 in a separate file as previously - though that behaviour is still7          supported if wanted.l  M       	 This approach is expected to pay further dividends in later releases.a     12.8.1 Bug fixes  I       - Hyperlinks added from a link dictionary sometimes got broken over L         two lines - inserting white space into the URL - preventing the link         from working  K       - Confusion with numbered sections beginning with "0" or ending ".00"          eliminated.   A       - Problems with formatting after underlined headings fixed.   F       - Failed to "view results" when DOS-compatible files we're being         generated.  *       - Various email/ftp/URL improvements  6       - Now ignore date-like "headings" e.g. 12.3.1998  F       - Capitalised headings were omitted from contents lists, and had?         bad anchor names (contained spaces, difficult to quote)a  @       - Automatic detection of centred text had stopped working.     12.8.2 New functions         _Windows Version_   H       - Added a "Preform simple conversion" tick box on the front panel.P         This does exactly the same as the "Keep it simple" policy (see 6.2.1.10)  J       - Improved the Headings dialog to allow headings policies to be more         easily edited now.  4       - Pre-processor document sections now working.         _All versions_  6       - Wildcard support has been added (see 4.3.3.1).  N       - Major re-writing of contents list generation has occurred (see 3.3.2).L         Includes new "Use any existing contents list" and "Generate externalK       	contents file" (see 6.3.4.4 and 6.3.4.3).  More changes are expected/         here in later versions.   .       - New Directory Page feature (see 6.3.9)  3       	New Policies                     Descriptioni3         ------------------------------------------- /       	Make Directory                   6.3.9.1 /       	Directory filename               6.3.9.2 /       	Show file titles in Directory    6.3.9.3 /       	Indent headings in Directory     6.3.9.4 /       	Directory title                  6.3.9.5 /       	Directory keywords               6.3.9.6 /       	Directory description            6.3.9.7d/       	Directory return hyperlink text  6.3.9.8 /       	Directory Script file            6.3.9.9s0       	Directory header file            6.3.9.100       	Directory footer file            6.3.9.11  8       - New "Minimum TABLE column separation" policy andN       	TABLE_MIN_COLUMN_SEPARATION pre-processor command (see 6.2.4.2 and 7.4)/         to allow some tuning of table analysis.s  =       - New "Use first heading as title" policy (see 6.3.1.2)   :       - New "Use first line as title" policy (see 6.3.1.3)  ;       - New "Recognised USENET groups" policy (see 6.3.2.5)t  ?       - New "Automatic centring tolerance" policy (see 6.3.6.5)   K       - New "Use <P> markup for paragraphs" policy (see 6.3.6.12), to alloweF         choice of either <P> or <BR> markup to be used for paragraphs.  F       - New "Default table width" policy and TABLE_WIDTH pre-processorL         command (see 6.3.7.10 and 7.4) to allow table widths to be specified  7       - New pre-processor command HTML_LINE (see 7.3.2)l     12.8.3 Other changes  L       - Reinstated some of the "error" messages removed in the last version,L         to do with section numbering.  This should make it more visible when0         the section heading analysis goes wrong.  H       - Added error reporting to file open.  You should now get an errorC         message if the program fails to find/open a file somewhere.   M       - Now support headings down to 5 levels (previously this was 4).  Note,rM         if you only have a couple at this level, the program may still ignoret,         them as statistically insignificant.  J       - Removed certain policies (such as "generate policy file") from theI         output when generating a full policy file.  This is because, when 9       	they were read back in, they could cause problems.o  M       - The "Include document section" policy (see 6.3.5.2) is now renamed touJ         "Include document section(s)" reflecting the fact that you can nowI         enter multiple values on one line, rather than requiring multiples0         lines with one value each as previously.  M       - Major re-structuring and additions to [section 5] to make the sectioniI         more coherent and up to date.  Some of the sections marked as neweG         in this version are simply the documentation catching up on then+         features added in earlier releases.5  )       	Sometimes I just work too hard :^)      12.9 Version 3.0 (August '98)"  K       There are a fair number of small changes in functionality over V2.3, eM       together with a fair number of bugfixes and refined algorithms.  A lot nM       of development during this time was directed towards the production of eL       a text-to-RTF converter using the same analysis engine.  Consequently 4       there are a lot of changes "under the bonnet".  I       The main functional change has been the revamp of the Windows User nH       Interface.  A new section (4.1.2) has been added to this document I       describing the Windows interface in a little details.  The changes @       include :-  H       	 - the button bar is replaced by a proper Windows menu, allowing 4       	   easier access to the programs functions.    L       	 - under the Help menu a link to the HTML documentation shipped with (            the software is now provided.  J       	 - the policy sheets are now "non-modal".  This means you no longerJ            have to dismiss them in order to do a conversion, you can leaveI            them up whilst the conversion is going on, making it easier tof>            go through the convert-change policy-convert cycle.     12.9.1 Bug fixes         _Windows version_   K       - General Protection Fault was occurring on the "Analyse file" button3I         if a file had not yet been converted.  This bug was introduced in.         V2.3         _All versions_  L       - No longer inserts <BR> before first heading if the first line in the         file is a heading   G       - "headings" that were underlined, but which were in fact part of-@         a table are no longer added to generated contents lists.  S       - Underlined/capitalised headings now get correct hyperlinks in contents listr%       	lists when using DOS filenamese  N       - Fixed bug that caused contents lists immediately following underlined %         headings to not be recognisedt  =       - URLs in heading no longer lead to invalid anchor tagsk  E       - Various URL changes; "alt." and "news." no longer treated as 52         a newsgroup, https:// pages now recognised  H       - Properly reject "indent" of 1.  Previously this was reported as ,         rejected, but was actually accepted.  O       - "Expect code samples" policy (see 6.2.1.13) was being ignored in table t         calculations.o  J       - The TABLE_HEADER_COLS directive only worked when there were header         rows as well.l  O       - Use of emphasis inside a TABLE cell was not being detected as all.  NowiM         it is detected if held on a single line.  Phrases that are emphasised I         over several lines inside a table cell may still not be detected.p  J       - Fixed a bullet numbering problem.  Previously the bullet numberingK         wasn't being reset correctly if two sets of bullets were separated )6         by text with a larger margin than the bullets.  7       - Emphasis at end of line now properly recognised   L       - Fixed bug that caused emphasis markup near pre-formatted sections of         text  L       - Small correction to line-splitting algorithm to prevent <TAG>s being2         spilt when they're near the natural break.  F       - Pre-processor command $_$_TITLE was being ignored if the "Use /         first heading as title" policy was set.o     12.9.2 New functions         _Windows Version_   >       - Major re-structuring of the user interface (see 4.1.2)  K       - Program's Help options now provide access to the online and offlineoI         versions of the HTML doco.  A lot of people were downloading the tI         software and then picking up a version of the doco, unawares theyfH         already had it.  Don't you people read README.TXT files or what?           _All Versions_  9       - New "Search for Definitions" policy (see 6.2.1.2)d  +       - New "TAB size" policy (see 6.2.1.6)o  O       - New "Expect sparse tables" policy and TABLE_MAY_BE_SPARSE pre-processor %         command (see 6.2.4.3 and 7.4)   >       - New "Add <BR> to lines with URLs" policy (see 6.3.2.7)  8       - New "Output file extension" policy (see 6.3.3.4)  :       - New "Minimise HTML file size" policy (see 6.3.3.7)  N       - New "Headings colour" policy (see 6.3.6.7).  Eventually I hope to add N         a whole suite of heading styling options, as these have been requested         by a number of people.  J       - New "Convert TABLE X-refs to links" policy and TABLE_CONVERT_XREFS4         pre-processor command (see 6.3.7.11 and 7.4)  9       - New CHANGE_POLICY pre-processor command (see 7.5)f  9       - New "Error reporting level" policy (see 6.3.3.14)d     12.9.3 Other changes  "       - Improved Windows interface  N       - Empty lines in a table cell now get an extra &nbsp; added, in additionL         to the <BR>.  This is to compensate for a bug in Internet Explorer 3K         which would ignore the <BR> otherwise, leading to alignment errors.   O       - Now treat phrases with all the words connected by underscores, and with <         underscores at both ends as well as underlined e.g.          _this_type_of_thing_  M       - Improved handling of tables with long urls in them.  Previously thesesJ         would not be recognised as part of a table.  Increased "long line"-         limit inside tables to 110 characters.  )       - Improved error reporting/handling   0       	- Report unrecognised pre-processor linesI       	- Report results of table analysis (e.g. if diagrams are detected)T0         - Report failure to find requested files=       	- Abort conversion if can't find requested policy filew  H       - Improved detection of "mal-formed" tables.  Previously this was 2         over-cautious, especially on short tables.  E       - Now add a trailing "/" to www etc URLs if none present (e.g.  M         www.yrl.co.uk).  This is a more correct URL, which should be accessedm"         slightly more efficiently.  J       - Now recognised "....." underlining, although why people do this is         beyond me :)  K       - Improved contents list detection in short documents with only levelh7         one headings, and documents with a chapter "0".u  L       - Improved headings detection in small files.  Made this less trigger          happy.  O       - Improved code detection, and now add bold emphasis of C++ like comments          inside a code sectione  P       - No longer allow "{" and "}" to be detected as probable bullet characters         when code is expected   K       - I've produced (with help from antipodean friends) an icon for files L       	converted by AscToHTM.  It's called a2hlogo.gif.  Feel free to use it:       	should you wish on any pages created with AscToHTM.  -       	An example piece of HTML code would be   
 $_$_BEGIN_PREh9       	<A HREF="http://www.yrl.co.uk/~jaf/ASCtoHTM.html">h<         <IMG SRC="a2hlogo.jpg" WIDTH=100 HEIGHT=36 BORDER=0 (         ALT="Converted by AscToHTM"></A> $_$_END_PREi  I       - With the introduction of the "Add <BR> to lines with URLs" policyfK       	(see 6.3.2.7), this behaviour is no longer default.  That is, if youlL       	*do* want <BR> added at the end of all lines containing URLs you will=       	need to switch this behaviour on using the new policy.   K       - With the introduction of the "Convert TABLE X-refs to links" policy M         (see 6.3.7.11), this behaviour is no longer default.  That is, if youaK       	*do* want section links inside your tables, you will need to switch e.       	this behaviour on using the new policy.  I       - ".htm" files are now with a lowercase extension, unless "Use DOS n0         filenames" policy selected (see 6.3.3.5)                                                                                                  