From: Dion A. <di...@go...> - 2010-06-19 05:05:08
|
I'm on a mac. And I agree with all these points: Setup is non-trivial. Still doesn't work. Docbook build errors totally unhelpful to help diagnose. I've never seen the result because I can't get it working. And I don't understand the the extra layer of complexity, since the output is just html. Dion. On Sat, Jun 19, 2010 at 12:58 AM, Shlomy Reinstein <sre...@gm...> wrote: > Hi, > > The documentation of jEdit and some plugins is in docbook format. > Setting up a docbook environment on Windows is non-trivial. After > having spent many hours on this, with advice from Eric and Alan, I > still don't have a working docbook environment, and still unable to > build the jEdit documentation. > Due to this, I sometimes update the documentation without actually > seeing the result. > > Is there a good reason for using docbook? If not, let's switch to > plain html, so that every developer can easily update the > documentation without requiring special tools. I can prepare some > macros to insert docbook structures like 'author', e.g. using > SuperAbbrevs, to make it easier to write. > > Thanks, > Shlomy > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > -- > ----------------------------------------------- > jEdit Developers' List > jEd...@li... > https://lists.sourceforge.net/lists/listinfo/jedit-devel > |