public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Eric Bischoff <ebisch@cybercable.tm.fr>
To: Jochem Huhmann <joh@gmx.net>
Cc: docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: [Fwd: Evolution of the DocBook tools]
Date: Wed, 27 Dec 2000 06:36:00 -0000	[thread overview]
Message-ID: <38BD6B50.CC2C1D52@cybercable.tm.fr> (raw)
In-Reply-To: <m31z5vkndn.fsf@nova.revier.com>

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

Jochem Huhmann wrote:

> There is another possible approach: A defined interface instead of a
> defined directory layout.

We could do both.

I have been reading your paper on the topic and it's a very
interesting approach. But now we have an opportunity to
define common directory names and catalog file names we
should take profit of it.

The scripts I've been rewriting also try to guess the
locations (a third approach), so they don't even need this
directory layout either. But I still think a common
directory layout would simplify things.

The problem is more general and is all what the Linux
Standard Base is about. I just want to solve it on the very
pecular DocBook side.

> So every distribution could use their own
> directories and filenames, but the interface stays the same. And some
> options to query the actual locations would allow other applications to
> find the location of the catalog and such. This would also work for
> FreeBSD, Solaris or whatever. Waiting for all Linux distributions and
> other Unix-Systems implement a common directory layout might take a long
> time, but an interface has just to be ported.

You're perfectly right. But as I said before, we can fight
on both fronts.

> PS: Jorge - if the new list barfs and you find a message of me causing

Jorge, did you change the list address ? I'm unable to write
to it, this is why I'm polluting docbook-tools-discuss
again.

Attached the new scripts (with the backends system) with the
corresponding man page drafts.

If a charity person can convert these drafts into good
docbook and send me the result, he would make me gain some
precious time. Thanks in advance.

Sorry to the non-interested people from this list about the
attachement.
 
-- 
 Éric Bischoff   -   mailto:ebisch@cybercable.tm.fr
 __________________________________________________
                                           \^o~_.
     .~.                           ______  /( __ )
     /V\         Toys story         \__  \/  (  V
   //   \\                            \__| (__=v
  /(     )\                        |\___/     )
    ^^-^^                           \_____(  )
     Tux                        Konqui     \__=v
 __________________________________________________
docbook-utils.tgz


[-- Attachment #2: docbook-utils.tgz --]
[-- Type: application/x-gzip, Size: 12342 bytes --]

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <38B562D1.DB411A17@cybercable.tm.fr>
     [not found] ` <shn1ojktao.fsf@Frechet.suse.de>
2000-12-27  6:36   ` Eric Bischoff
2000-12-27  6:36     ` Jochem Huhmann
2000-12-27  6:36       ` Eric Bischoff [this message]
2000-12-27  6:36         ` Jochem Huhmann
2000-12-27  6:36           ` Eric Bischoff

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=38BD6B50.CC2C1D52@cybercable.tm.fr \
    --to=ebisch@cybercable.tm.fr \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=joh@gmx.net \
    /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).