public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Peter Ring <PRI@cddk.dk>
To: "'docbook-tools-discuss@sourceware.cygnus.com'"
	<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: <c=DK%a=_%p=CD-Danmark%l=CDDKSERVER-000225110001Z-8990@cddkserver.cddk.dk> (raw)

Keep talking!

I've been waiting for this subject to get some real focus. It seemed
that most SGML tool developers were happy hacking their means of
distribution (including introducing silly variants of SGML Open catalog
files), which is fine as long as you can pretend to own the poor users'
namespace. Well, you don't.

We try putting together a directory structure for the kind of 'things'
that SGML tools share, based on James Clark's design for the entity
manager in sgmls (refer to
http://www.uic.edu/~cmsmcq/tech/sgmls.entities.html ). The idea is to
find a pattern that is easy to understand and implement, so that anyone
(e.g. a program) would come up with the same directory structure, given
the FPI for an entity. The structure must allow for different releases
of 'the same' entities, and we'd like to use the resulting directory
structure as a name space that also manages related processing tools,
scripts and stylesheets. Some of the processing tools use the directory
structure as part of a name space, e.g. Python.

Comments? Thoughts? 

Kind regards,
Peter Ring


-----Original Message-----
From: Jorge Godoy [ mailto:godoy@conectiva.com.br ]
Sent: Thursday, February 24, 2000 3:11 PM
To: Eric Bischoff
Cc: docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: Evolution of the DocBook tools

<snip>

> All of this discussion, according to me, shows that it was necessary to
> embetter the docbook-tools distribution, and to normalize the choices.

I think the same. Isn't it subject for a new list? I can create one to
discuss it. It might be called "sgml-packages" and be hosted here at
Conectiva. Or, if nobody on this list gets bored, we might continue
talking here... 

<snip>

             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 Peter Ring [this message]
2000-12-27  6:36 ` Eric Bischoff
  -- strict thread matches above, loose matches on Subject: below --
2000-12-27  6:36 Eric Bischoff
2000-12-27  6:36 Gregory Leblanc
2000-12-27  6:36 ` Eric Bischoff
     [not found] <951281049.19725.ezmlm@sourceware.cygnus.com>
2000-12-27  6:36 ` db2??????? vs. SGMLTools2 vs. what else? Horacio MG
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             ` Jorge Godoy
2000-12-27  6:36           ` Eric Bischoff
2000-12-27  6:36           ` Eric Bischoff
2000-12-27  6:36           ` Eric Bischoff
2000-12-27  6:36             ` Jorge Godoy

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='c=DK%a=_%p=CD-Danmark%l=CDDKSERVER-000225110001Z-8990@cddkserver.cddk.dk' \
    --to=pri@cddk.dk \
    --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).