--- Ian Bicking [EMAIL PROTECTED] wrote:
The documentation format discussion kind of died down, but I'd like
to
do some documenting, and that's one of those fleeting motivations you
really have to grab onto ;) Anyway, after looking some at the XML
produced by reST, I think the format
Ian Bicking wrote:
The documentation format discussion kind of died down, but I'd like to
I know that I'm late to this discussion, but something has occurred to me.
As I understand it, OpenOffice stores all of its docs in pure XML
format. What if we had someone design a SIMPLE template, then
Enought writing about how to write, just write!
The format DOES NOT MATTER as long as it has some logic. reStruct, XML,
docbook, gentoo, OpenOffice ... all can be CONVERTED to something.
Here is a deal.
Once we have written 30 new pages of documentation we will revisit this
topic and see what
I've already done some heavy work in transforming the OO-Xml files to other things.
It's definitely do-able, but from my perspective I'd rather go with something that
VIM, or Emacs, or heck even nano can open. reST seems to be amazingly easy.
I say go with reST, and we'll work out the
To: Webware discuss
Subject: [Webware-discuss] Documentation format
The documentation format discussion kind of died down, but I'd like to
do some documenting, and that's one of those fleeting motivations you
really have to grab onto ;) Anyway, after looking some at the XML
produced by reST, I
On Wed, 2002-10-30 at 09:09, Roger Haase wrote:
At the risk of making the documentation project even harder, it seems
to me the best place to create Webware documentation is in a TWiki-like
environment because mass participation would be so easy. Having looked
over the reStructuredText specs
I know... it's only because I'm planning on ripping out old markup and
replacing it with new markup that I'm reluctant to dive in without
feedback. But now that I have that feedback I'll move forward on that.
On Wed, 2002-10-30 at 10:04, Aaron Held wrote:
Enought writing about how to write,
