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

Jorge Godoy wrote:
> 
> 
> You might have several catalogs merged in your personal catalog
> file. How? You can add a `CATALOG "file.cat"' in it and it will
> "automagically" include the other catalog.

Of course you can do a lot of things manually. But what I was saying is
that a standard installation needed the "install-catalog" script (or
some equivalent mechanism if you want to use the CATALOG keyword) to be
installed *early* with respect to the other packages.

But yes, it's true, "install-catalog" could be improved to use the
CATALOG keyword instead of really merging the catalog themselves. But
wasn't there a problem with the CATALOG keyword that wasn't supported by
jade or something else ?

> Look at "conectiva.cat" in the file I've sent you in the other
> message. It solves lots of problems and you don't need to merge an
> entire new catalog each time a new release is done. And, besides, you
> use the stylesheets catalog with all it's relative paths. It works
> wonderfully.

You're mentioning another problem that I hadn't been speaking about :
merging catalogs implied that the other packages couldn't be in their
own directory, because the relative paths became relative to the merged
CATALOG file. There are two
ways to work around this (if not more) :
- accept not to merge catalogs in the db2* scripts (my solution)
- use the CATALOG keyword (your solution)

but sure, the best would be to offer the choice between both solutions,
therefore to enhance install-catalog script, with the restriction that I
can remember the CATALOG keyword not to be recognized by some programs.
My db2* scripts accept both a merged catalog or separate catalogs, the
first having the priority, of course.

> > That's what I did for Caldera, and I'll keep it unless Debian has
> > different names with a clean directory layout too. It would be stupid to
> > have only two-letter differences... ;-)
> 
> I'm doing some work at Conectiva Linux on that too.
> I'm using /usr/lib/sgml and then creating subdirectories with each
> stylesheet. It's still a mess, but I'm cleaning it up.

Same idea for what I did. What are your directory names ? I chose :

docbook-dtd  docbook-stylesheets  iso-entities-8879.1986  jade  kde 

Let's all take the same names, if you accept. I also suggest "gnome" for
Gnome project customizations  and "ldp" for Linux Documentation Project
customizations.

And I think it is becoming urgent that Mark should give us his blessing,
so those evolutions become "official" ;-)

-- 
Eric Bischoff  -  Documentation and Localization
Caldera (Deutschland) GmbH - Linux for Business!
Tel: +49 9131 7192 300 -  Fax: +49 9131 7192 399
http://www.caldera.de/

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

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <951281049.19725.ezmlm@sourceware.cygnus.com>
2000-12-27  6:36 ` Re : db2??????? vs. SGMLTools2 vs. what else? David Mason
2000-12-27  6:36   ` Eric Bischoff
2000-12-27  6:36 ` was something else - now SGML and XML David Mason
2000-12-27  6:36   ` Norman Walsh
2000-12-27  6:36 ` David Mason
2000-12-27  6:36 ` Re : db2??????? vs. SGMLTools2 vs. what else? David Mason
2000-12-27  6:36   ` Eric Bischoff
2000-12-27  6:36     ` Mark Galassi
2000-12-27  6:36   ` Norman Walsh
2000-12-27  6:36 ` David Mason
2000-12-27  6:36   ` Norman Walsh
2000-12-27  6:36 ` Horacio MG
2000-12-27  6:36   ` Jorge Godoy
2000-12-27  6:36   ` Re : " Eric Bischoff
2000-12-27  6:36     ` Jochem Huhmann
2000-12-27  6:36       ` Eric Bischoff
2000-12-27  6:36         ` Jochem Huhmann
2000-12-27  6:36           ` Evolution of the DocBook tools Eric Bischoff
2000-12-27  6:36             ` Jorge Godoy
2000-12-27  6:36           ` Eric Bischoff
2000-12-27  6:36           ` Re : db2??????? vs. SGMLTools2 vs. what else? Eric Bischoff
2000-12-27  6:36             ` Jochem Huhmann
2000-12-27  6:36             ` Jorge Godoy
2000-12-27  6:36           ` Evolution of the DocBook tools Eric Bischoff
2000-12-27  6:36           ` Re : db2??????? vs. SGMLTools2 vs. what else? Eric Bischoff
2000-12-27  6:36             ` Jochem Huhmann
2000-12-27  6:36               ` Eric Bischoff
2000-12-27  6:36             ` New list (was Re: Re : db2??????? vs. SGMLTools2 vs. what else?) Jorge Godoy
2000-12-27  6:36               ` Jochem Huhmann
2000-12-27  6:36               ` Jorge Godoy
2000-12-27  6:36           ` Eric Bischoff [this message]
2000-12-27  6:36             ` Evolution of the DocBook tools Jorge Godoy
2000-12-27  6:36             ` Jorge Godoy
2000-12-27  6:36     ` Re : db2??????? vs. SGMLTools2 vs. what else? Jorge Godoy
2000-12-27  6:36       ` Eric Bischoff
2000-12-27  6:36 Evolution of the DocBook tools Peter Ring
2000-12-27  6:36 ` Eric Bischoff
  -- strict thread matches above, loose matches on Subject: below --
2000-12-27  6:36 Gregory Leblanc
2000-12-27  6:36 ` Eric Bischoff
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=38B51C42.41B72A89@cybercable.tm.fr \
    --to=ebisch@cybercable.tm.fr \
    --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).