> On Sat, Mar 30, 2002 at 12:17:19AM -0800, Neil Watkiss wrote:
> | I'm a bit disappointed. I tell you what: if I were to convert it to a
> | different format that could generate both HTML and PDF, would you
> | object to using _that_ as the main source for the spec, instead of
> | the HTML?
> HTML is rather awful.. I don't have any objections!
I agree, in principle.
> | The next question is whether you have any preferences or objections to
> | any format over another. GNU documentation is written in Info format,
> | which can be converted to PostScript, PDF and HTML. We could use POD,
> | too. Or LaTeX.
> | Frankly, I'm for anything _but_ HTML.
> What ever you are comfortable with. Although I must
> warn you that extensive use of HTML tables was used to
> get the productions to line up nicely...
- We'd absolutely require the source to be a plain text file, rather than a
format editable but some specific program.
- The system(s) for processing it into HTML/PDF/etc. should be readily
available for all three of us (Brian, Clark and myself).
- It needs to be "smart" enough to format the productions well without too
much pain. Likewise it must allow embedding links to external URLs, support
in-document links, etc.
- The resulting HTML file should be reasonably clean, ideally use CSS etc.
- I'd rather not use something which was *too* heavy (I have to download it
into my home computer, for example :-). Though I suppose if we want PDF
output that's a luxury...
Hmmm. Systems I worked with which may fit the bill are Info and LaTeX. LaTeX
is certainly strong enough to do anything, but it is rather heavy and I'm
not certain about the quality of the resulting HTML. Info is much simpler
and lightweight, but I don't know if it is strong enough for our purposes.
I know the Linux documentation project uses some system (DocBook). It may be
a better choice... but I've never used it.
Another point: there are some changes which we know need to be done to the
spec. I guess the best thing would be not to mix any changes with the
porting itself - that is, take a version and convert it "as is". The changes
we have in mind are rather minor and I could enter them by next weekend. So
I suggest that in the mean while you just look into the various possible
formats and let us know which one seems best, before you actually start the
Final point: Many thanks for taking on this project! I was chafing a bit
working in HTML, and being able to produce a better printable version via
PDF would be very nice.