Difference between revisions of "Phoenix Project"

From WRG
Jump to navigationJump to search
Line 40: Line 40:
 
* [[Archive:The Whitney Family of Connecticut, Links 401-500]], all
 
* [[Archive:The Whitney Family of Connecticut, Links 401-500]], all
 
* [[Archive:The Whitney Family of Connecticut, Links 501-600]], 501-550, all
 
* [[Archive:The Whitney Family of Connecticut, Links 501-600]], 501-550, all
 +
* [[Archive:The Whitney Family of Connecticut, Links 601-700]], 666-700, all
 +
* [[Archive:The Whitney Family of Connecticut, Links 701-800]], 701-800, all
 
* [[Archive:The Whitney Family of Connecticut, page 746]]
 
* [[Archive:The Whitney Family of Connecticut, page 746]]
 
* [[Archive:The Whitney Family of Connecticut, page 747]]
 
* [[Archive:The Whitney Family of Connecticut, page 747]]

Revision as of 11:23, 9 August 2008

These are notes to plan the conversion of the Phoenix book from the old website to this one.

Steps

  1. Finish templates (need footnote templates, see Test)
  2. Determine which pages the script will convert (1 to 2475)
  3. Write conversion program
  4. Test results, repeat if needed
  5. Run conversion
  6. Upload all pages
  7. Manually convert preface pages, errata pages, index pages, etc.

Notes

  • Tables in the body of an entry will require hand-editing. Current solution: split the entry into three parts, use PhoenixEntry for the first and last, and explicitly code the table in the middle one. First example: a signature on page 11.
  • Footnotes may contain preformatted text, which cannot be passed into the PhoenixFootnote template for some reason. Current solution: explicitly code the footnote without using the template, but using <span>, <font>, <sup>, and text. First example: a footnote on page 25.
  • I have replaced two-column footnotes with one-column ones. This could be undone if we find a convenient way to handle two columns. Tables cannot be passed into the PhoenixFootnote template, probably because the "|" character used as a delimiter for a table interferes with the same character used as a delimiter in the template. Current solution: explicitly code a two-column footnote using a table, <span>, <font>, <sup>, and text.
  • Using the "|" character in diagrams does not work, interfering with the same character used as a delimiter in templates. I substituted the string "&#124;" instead. That works, but drawing the diagram becomes more difficult. First example: a diagram on page 15.

Templates and Test Pages for the Conversion

Pages Already Converted