Will, thanks for the offer. If I get stuck, I'll be sure to give you a yell.
On the alignment issue, that's just exactly what I did yesterday to fix the cell problem except that I made them each 33 pixels wide instead of 30 as you suggested. Nice to know I wasn't way off base on that. raynor has the fix but he crashed early Last night and it may be a little while before he can get the new Version out. He also has some other things he wants to add to spiff it up some more.
I've been thinking about CSS and I'm leaning away from using that just because I want this to be as standard and compatible as possible. From my reading it seems that style sheets might cause some problems with non MS Explorer browsers and make maintaining this more work than I'd like it to be. I tend to take the K.I.S.S. principal fairly seriously.
As for helping out with the manual project, it's my hope that what raynor and I are doing can be directly incorporated into it. I think raynor is already working on that project as well. The advantage to the approach we're taking is:
1) The HTML documentation is easily updated in an automated fashion whenever new SE4 patches come out. Becuase of this the document information is never out of date.
2) Documentation can be generated for user mods just as easily as for the standard game.
3) A very wide range of SE4 information can be generated in an automated fashion that would take literally weeks or months to generate by hand.
We have some neat ideas on how this technique can be extended to document racesets, facilities, non-weapon components, ship designs, weapon comparisons, etc. With all the data files we have to work with there are a lot of areas in which we could use this approach. I can't help it, I'm a programmer, I'm always looking for ways to automate tedious tasks. So, okay, I'm lazy too, what can I say? LOL.
Now off to work (gah!).