Format for Contents List Database
--------------------------------- 

1. The name of the file corresponds to the journal issue. e.g. "j62.txt"

2. The contents of the file must be plain text. It should not contain
   any HTML tags but, if it does, they must be valid within <DT> and <DD>
   elements. If it contains any disallowed characters they must be 
   escaped; e.g. use "&pound;".  Double quotation marks are not allowed and
   should ideally be replaced by "&quot;", but modern browsers do not seem 
   to mind if they arent.

3. The text within the file consists of pairs of entries. 
   i) A single line containing the article title, terminated by end-of-line. 
   ii) A single line containing the article description terminated by e-o-l.
   These lines must not be longer than 1000 characters.  The first line of 
   the pair is encapsulated in <DT> tags before displaying. The second is 
   wrapped in <DD> tags.

4. Blank lines containing zero or more white spaces are valid anywhere in 
   the file.

5. Note: the article title and descriptions must one ONE LINE of up to 1000
   characters each. Do not put end-of-line characters in the middle of a 
   long line.

6. No other alterations to the database structure are required. The routine
   that displays the list of contents "understands" what journals have been
   published by whether the .TXT files exist. It works out the intended date 
   of publication itself.

7. If a journal has been published, but no contents list is available, this 
   fact can be noted by creating the appropriate TXT file and inserting two
   lines (note: all entries must be pairs of lines - see note 3 above) as
   follows.

   Notice
   Journal 62 was published on xxx. Its contents list will be available soon.

8. A JPG of the front cover is optional. If it exists, it should be named
   "j62.jpg", etc and placed in the "covers" sub-directory. It should be 200
   pixels wide; sharpened and compressed appropriately.