public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Eric Bischoff <ebisch@cybercable.tm.fr>
To: docbook-utils@bazar.conectiva.com.br,
	docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: Getting indexes?
Date: Wed, 24 May 2000 03:54:00 -0000	[thread overview]
Message-ID: <392BB577.AE72C36A@cybercable.tm.fr> (raw)
Message-ID: <20000524035400.-v5dWXxe_Sr4kKoo6hAjybf4mfYje1civSybaYC4yso@z> (raw)
In-Reply-To: <A5F46F4ED18FD211ABEE00105AC6CF077F8114@email.cu-portland.edu>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2830 bytes --]

Gregory Leblanc wrote:
> 
> 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.

Hopefully. I don't have any feedback yet.

>  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)

Yes, and thanks to Norman Walsh, it comes with XSL style
sheets.

> 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).

We have spent some time on rewriting them in a new project
called "docbook-utils" that should if Mark accepts become
part of the DocBook tools. I am waiting for Mark Galassi's
green light to put them on the DocBook-tools FTP server at
Sourceware, along with a new "LSB-proposals-conformant"
packaging (which does, by the way, put collateindex.pl in
/usr/bin ;-) ).

> 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.

Yes.

We already added a script, sgmldiff.pl, to compare the
markup of two SGML files, regardless of the text between the
tags. It's really precious for translations - now I even
wonder how we could have been living without it at KDE.

I have on the TODO list for docbook-utils list :
- conversion from legacy input formats (texinfo, linuxdoc,
...)
- wrapper for collateindex.pl.
- extraction of the contents of a given tag from command
line
  (precious for <releaseinfo>, <keyword>, <date>, ...)
  (more SGML-aware than a simple "grep")
It seems to rejoin pretty much what you are requesting ;-).
I already have people volunterring for the first two points,
and I might write the third one.

We just have set up a docbook-utils@bazar.conectiva.com.br
developers mailing list to accelerate the development.

-- 
 Éric Bischoff   -   mailto:ebisch@cybercable.tm.fr
 __________________________________________________
                                           \^o~_.
     .~.                           ______  /( __ )
     /V\         Toys story         \__  \/  (  V
   //   \\                            \__| (__=v
  /(     )\                        |\___/     )
    ^^-^^                           \_____(  )
     Tux                        Konqui     \__=v
 __________________________________________________

  parent reply	other threads:[~2000-05-24  3:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-27  6:36 Gregory Leblanc
2000-05-23 22:13 ` Gregory Leblanc
2000-12-27  6:36 ` Eric Bischoff [this message]
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:56 ` Gregory Leblanc
2000-12-27  6:36 ` Eric Lee Green
2000-05-23 21:12   ` Eric Lee Green
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:52 ` Gregory Leblanc

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=392BB577.AE72C36A@cybercable.tm.fr \
    --to=ebisch@cybercable.tm.fr \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=docbook-utils@bazar.conectiva.com.br \
    /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).