atom feed12 messages in org.oasis-open.lists.docbook-appsRe: DOCBOOK-APPS: Creating Different ...
FromSent OnAttachments
Holger RauchAug 1, 2000 3:35 am 
Sebastian RahtzAug 1, 2000 4:02 am 
Jorge GodoyAug 1, 2000 7:17 am 
Sebastian RahtzAug 1, 2000 7:23 am 
Sean DonnellanAug 1, 2000 9:30 am 
Sebastian RahtzAug 1, 2000 11:53 am 
Sean DonnellanAug 1, 2000 2:22 pm 
Sebastian RahtzAug 1, 2000 3:44 pm 
Alex LancasterAug 1, 2000 5:05 pm 
Sean DonnellanAug 2, 2000 7:02 am 
Sebastian RahtzAug 2, 2000 7:30 am 
Norman WalshAug 4, 2000 2:22 pm 
Subject:Re: DOCBOOK-APPS: Creating Different Output Formats Using DocBook V4.1 XML
From:Alex Lancaster (ale@bigfoot.com)
Date:Aug 1, 2000 5:05:09 pm
List:org.oasis-open.lists.docbook-apps

"SR" == Sebastian Rahtz <seba@computing-services.oxford.ac.uk> writes:

SR> Jorge Godoy writes:

[...]

- texinfo

SR> why?

It's output is good!

SR> good god. we do have different aesthetics.....

Texinfo is not only about TeX, but mainly about `info' documents, IMHO, which is better form of hypertext than HTML, especially for reference guides/API docs because: 1) it's searchable across pages (not just within a page like HTML), 2) can be manipulated purely by keystrokes (and yes, I know about lynx, but info's more sophisticated w.r.t. documentation features, than lynx); 3) info uses a lightweight reader, which doesn't require a behmoth like Netscape... great if you just want to quickly look up an API or a function within Emacs, whilst programming...

For Docbook formatting into `info', try:

http://sourceforge.net/projects/docbook2x

I believe the maintainer, Steve Cheng, is actually in the process of writing XSL stylesheets to transform DocBook XML into an intermediate Texinfo XML format than can be easily translated into actual Texinfo. I've used the earlier Perl script version on a 400+ reference guide with good results.

Alex