>> I have a huge, badly organized, flat text 'README' that few people
read and even fewer understand. After flirting with various doc
technologies, it occured to me they were all more complex than I wanted
any part of and the _real_ problem is the organization and not the
presentation technology. Fixing that has a much lower cost entry ticket
and even that was more expensive than I've been able to tackle. <<
Need to "payback" some of the benefit that I have derived here, so,
would be glad to help with this if you are interested.
Spent about a year on the different doc formats with a project to
convert a "dead tree" book authored by my father to electronic format
and, as a result, have some strong ideas.
In general, they distill down to using _simple_ html... something that
is only slightly less common than plain ascii text.
The primary benefit of html is the ability to "flow" the text in almost
any browser or reader (including small devices such as pda's, ipods, and
possibly gps units) to maintain readability using only up/down
scrolling. Further, "opening" an html document not only brings it up in
an interface almost everyone is familiar with, it brings it up in the
user's choice of a browser app.
Next is the ability to "link" both within a single document as well as
point to specific places in other local documents. For example, table
of content and index links are dirt simple, you can use the same targets
to cross link in the text while retaining the ability to return to your
starting place when reading.
Further, it's easy to include images if needed.
Finally, if you need to assure that your prose doesn't get edited by
someone else, generating a pdf file out of an html file retains all of
the above benefits
With your permission, will cobble up an indexed html page of your README
(which I _have_ read) The README copy I have is dated 8/15/05
Might even get to my overdue batch file promise as well ;-)
Beverly Howard [MS MVP-Mobile Devices]