public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gregory Leblanc <GLeblanc@cu-portland.edu>
To: docbook-tools-discuss@sourceware.cygnus.com
Subject: RE: Getting indexes?
Date: Wed, 27 Dec 2000 06:36:00 -0000	[thread overview]
Message-ID: <A5F46F4ED18FD211ABEE00105AC6CF077F8114@email.cu-portland.edu> (raw)

> -----Original Message-----
> From: Eric Lee Green [ mailto:eric@badtux.org ]
> Sent: Tuesday, May 23, 2000 8:43 PM
> To: Gregory Leblanc; docbook-tools-discuss@sourceware.cygnus.com
> Subject: RE: Getting indexes?
> 
[snip]
> 
> I'm still ambivalent about the whole Docbook thing. It seems 
> powerful enough,
> but nobody seems to have really put together things so that 
> they're easy to use
> for mere mortals (I can write scripts in my sleep, but that 
> ain't gonna work
> for our technical documentation team!).  On the other hand, 
> the HTML output
> looks pretty decent compared to the output of LaTeX2HTML, 
> which is my current
> method of getting HTML out of structured markup...  On the 
> other hand, I can
> use LyX for writing LaTeX code... hmm... do any of the XML 
> editors work similar
> to LyX? How do Docbook and XML get along? 

Well, recomendations on SGML just went out to the LSB this week (err, maybe
before the weekend, I forget).  Hopefully those will get things a bit more
standardized.  I don't use the output from my stuff too often, so I'm not
sure how to resolve those issues.  You can use LyX and export to Docbook,
but I'm not sure how that works.  I just noticed that DocBook 4.0 is
official, guess it's time to move to XML.  (As of DB4, XML is official)  

I have to agree that the tools that do exist aren't very well put together
to get you up and running (although with a bit of work, it's do-able).
What's a MUCH bigger concern to me is the lack of tools to do anything
except process the DocBook source into other formats.  What about using
DocBook to enhance searches?  How about and OO database?  What about
indexing the document into a larger collection?  I don't see any tools for
these yet.  I've got some ideas about how do to a couple of those, but
they're kinda slow in taking shape.
	Greg

WARNING: multiple messages have this Message-ID
From: Gregory Leblanc <GLeblanc@cu-portland.edu>
To: docbook-tools-discuss@sourceware.cygnus.com
Subject: RE: Getting indexes?
Date: Tue, 23 May 2000 22:13:00 -0000	[thread overview]
Message-ID: <A5F46F4ED18FD211ABEE00105AC6CF077F8114@email.cu-portland.edu> (raw)
Message-ID: <20000523221300.Vrxyr3GNzujpayGW-nRUuUWSgNAlXAsD3UOGDOdNu9E@z> (raw)

> -----Original Message-----
> From: Eric Lee Green [ mailto:eric@badtux.org ]
> Sent: Tuesday, May 23, 2000 8:43 PM
> To: Gregory Leblanc; docbook-tools-discuss@sourceware.cygnus.com
> Subject: RE: Getting indexes?
> 
[snip]
> 
> I'm still ambivalent about the whole Docbook thing. It seems 
> powerful enough,
> but nobody seems to have really put together things so that 
> they're easy to use
> for mere mortals (I can write scripts in my sleep, but that 
> ain't gonna work
> for our technical documentation team!).  On the other hand, 
> the HTML output
> looks pretty decent compared to the output of LaTeX2HTML, 
> which is my current
> method of getting HTML out of structured markup...  On the 
> other hand, I can
> use LyX for writing LaTeX code... hmm... do any of the XML 
> editors work similar
> to LyX? How do Docbook and XML get along? 

Well, recomendations on SGML just went out to the LSB this week (err, maybe
before the weekend, I forget).  Hopefully those will get things a bit more
standardized.  I don't use the output from my stuff too often, so I'm not
sure how to resolve those issues.  You can use LyX and export to Docbook,
but I'm not sure how that works.  I just noticed that DocBook 4.0 is
official, guess it's time to move to XML.  (As of DB4, XML is official)  

I have to agree that the tools that do exist aren't very well put together
to get you up and running (although with a bit of work, it's do-able).
What's a MUCH bigger concern to me is the lack of tools to do anything
except process the DocBook source into other formats.  What about using
DocBook to enhance searches?  How about and OO database?  What about
indexing the document into a larger collection?  I don't see any tools for
these yet.  I've got some ideas about how do to a couple of those, but
they're kinda slow in taking shape.
	Greg

             reply	other threads:[~2000-12-27  6:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-27  6:36 Gregory Leblanc [this message]
2000-05-23 22:13 ` Gregory Leblanc
2000-12-27  6:36 ` Eric Bischoff
2000-05-24  3:54   ` Eric Bischoff
  -- strict thread matches above, loose matches on Subject: below --
2000-12-27  6:36 Gregory Leblanc
2000-05-23 16:52 ` Gregory Leblanc
2000-12-27  6:36 Eric Lee Green
2000-05-23 15:38 ` Eric Lee Green
2000-12-27  6:36 Gregory Leblanc
2000-05-23 16:56 ` Gregory Leblanc
2000-12-27  6:36 ` Eric Lee Green
2000-05-23 21:12   ` Eric Lee Green

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=A5F46F4ED18FD211ABEE00105AC6CF077F8114@email.cu-portland.edu \
    --to=gleblanc@cu-portland.edu \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).