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

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

On Thu, Feb 24, 2000 at 12:55:46PM +0100, Eric Bischoff wrote:

Sorry! I forgot one thing:

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

If we don't accept merging catalogs, we ar going to allow users
specifying catalog at the command line. He (the user) will have to
say:

- Where's jade/openjade stylesheets
- Where's DocBook stylesheets
- Where is/are his customized stylesheets.

The command typed would be huge and subject to typing errors. I don't
think it's a good approach... 


--
Godoy.	<godoy@conectiva.com.br> 

Setor de Publicações
Publishment Division                   Conectiva S.A.

  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     ` Mark Galassi
2000-12-27  6:36   ` Norman Walsh
2000-12-27  6:36 ` was something else - now SGML and XML David Mason
2000-12-27  6:36 ` db2??????? vs. SGMLTools2 vs. what else? 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           ` Eric Bischoff
2000-12-27  6:36             ` Jorge Godoy
2000-12-27  6:36             ` Jorge Godoy [this message]
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           ` Re : db2??????? vs. SGMLTools2 vs. what else? Eric Bischoff
2000-12-27  6:36             ` Jorge Godoy
2000-12-27  6:36             ` Jochem Huhmann
2000-12-27  6:36           ` Evolution of the DocBook tools Eric Bischoff
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 ` David Mason
2000-12-27  6:36   ` Norman Walsh
2000-12-27  6:36 ` 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 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=20000224105322.M24290@conectiva.com.br \
    --to=godoy@conectiva.com.br \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=ebisch@cybercable.tm.fr \
    /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).