Re: reStructuredText

From: Date: Thu, 12 Jun 2003 12:21:11 +0000
Subject: Re: reStructuredText
References: 1 2 3 4 5 6 7 8 9 10 11 12  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-17354@lists.php.net to get a copy of this message
On 12 Jun 2003 14:10:41 +0200 Christian Stocker <chregu@bitflux.ch> wrote: > Maybe this situation will improve soon. If anyone's attending the > phpdoc meeting at linux-tag in Karlsruhe, you'll see what I mean (ie > using our browserbased XML Wysiwig Editor (http://bitfluxeditor.org, > demo is Mozilla only) > > At the moment, the Bitflux Editor is not that advanced to be used with > full blown docbook as phpdoc is, but we are currently developing a > much improved version, so please don't judge about the demo and come > to LinuxTag ;) Again, I like your vision :). Docbook should be the format; use userfriendly tools to edit it. That said, reST is obviously a specific syntax. Translators has to learn it before starting any translations (or others editors). It will a pain for the peardoc team to work with many formats. Docbook can quickly have something to edit the files in a wysiwyg tool, using post transformations to get peardoc2 files (phpdocu?). I doubt this will be possible to get that quickly with reST. An interesting point is the link I posted earlier from Norm Walsh: <note> the purpose for which DocBook was originally designed -- primarily as an "exchange" or "interchange" vocabulary -- is at odds with what most people use it for today; most current users directly author documents in"standard" DocBook, as opposed to "writing in some private tag set, or deep customization of DocBook, and then converting to the standard to pass documents to other interchange partners") </note> imho, using office tools to edit documentations is the way (I consider Bitflux editor as an office tools :) ). That's the idea we have from months, and that's what has been discussed during the meeting. hth pierre

« previous php.pear.dev (#17354) next »