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: Re: Evolution of the DocBook tools
Date: Wed, 27 Dec 2000 06:36:00 -0000	[thread overview]
Message-ID: <38B533C6.C543446A@cybercable.tm.fr> (raw)
In-Reply-To: <m31z63v7wo.fsf@nova.revier.com>

Jorge Godoy wrote:
> 
> IMHO, if we want not interfere with the stylesheets used and want tro
> allow a generic use of these tools, there are few alternatives:
> 
> - Using the CATALOG directive
> - Using the DELEGATE directive
> - Merging CATALOG files (would require that we _change_ the specified
>   paths!)

- plus a fourth one, letting db2* scripts determine where are the
catalogs (my solution)

Among the first three ones, only the first one is really good, IMHO.

The third one was chosen by the current DocBook-tools and implied a
dirty directory layout if you don't want to re-work the paths. And this
had bad consequences if you wanted to use alternate stylesheets.

> Which programs don't recognize the CATALOG keyword? Jade and OpenJade
> work with no problems. Programs that don't work aren't in accordance
> with the specifications. Should we support them or "brake" them and
> make the author improve their programs?

Now I remember Epic does not recognize this keyword.

> > 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" ;-)
> 
> Ok... I'm using a slightly different notation:
> 
> /usr/lib/sgml
>  - docbook-3.1
>  - docbook-3.0
>  - docbook-4.0beta
>  - docbook-2.4
>  - docbook-2.4.1
>  - docbook-version (generalization! I don't have this directory)
>  - jade
>  - iso-entities-8879.1986 (this is from sgmltools 1.09, not DocBook related)
>  - gnome (as you suggested)
>  - ldp (they don't have a stylesheet for DocBook yet...)
>  - kde (they have it?)

Yes, kde customization is available in package "kdesdk", subdirectory
"ksgmltools/customization"

Why don't you put the stylesheets at the same level as the dtd ? it
allows to change the stylesheets version, without changing the dtd, in a
simpler way (there are more stylesheet versions than dtd ones).

Docbook DTD and stylesheets numbering is a really good idea, indeed. It
looks like you went even further in the reflexion than I did ;-). What
about making a symbolic link from the generic name to the numbered name
? Like : docbook-dtd -> docbook-dtd-4.0beta.

Iso-entities are not only needed by sgmltools 1.09, but by jade as well.
Maybe you have them duplicate, just check.

So I suggest :

/usr/lib/sgml
  docbook-dtd-2.4
  docbook-dtd-2.4.1
  docbook-dtd-3.1
  docbook-dtd-3.0
  docbook-dtd-4.0beta
  docbook-dtd -> docbook-dtd-3.1
  docbook-sylesheets-1.49
  docbook-sylesheets-1.50
  docbook-sylesheets-1.51
  docbook-sylesheets-1.52
  docbook-stylesheets -> docbook-stylesheets-1.52
  jade
  iso-entities-8879.1986
  gnome
  ldp
  kde

> The problem with "iso-entities" is that some stylesheets refer to them
> on it's catalog. Making a patch in a packaged distribution (RPM, deb,
> etc.) is easy, but I don't know if it's good in a plain .tar.gz
> distribution (of course, a note saying that files were modified and
> the like would be enough).

I have been adding a catalog for them in iso-entities-8879.1986, the one
that was in sgml-tools-1.09 ;-) I searched a lot, even on ISO web
servere, but I was unable to find something that looked "official". So I
just did like the others and took what was available...

> BTW, there's another problem regarding iso-entities: sgmltools use
> them with upper case (ISOamsa) and Norm's stylesheets use it with
> lower case and an extension (isoamsa.gml). It's another
> standardization issue.

I was about to say it. I took :

ISOamsa  ISOamsc  ISOamso  ISObox   ISOcyr2  ISOgrk1  ISOgrk3  ISOlat1 
ISOnum  ISOtech
ISOamsb  ISOamsn  ISOamsr  ISOcyr1  ISOdia   ISOgrk2  ISOgrk4  ISOlat2 
ISOpub  iso-entities.cat

I had to remove the DTD catalog entries to have them shared between
sgml-tools and the modular stylesheets. Maybe it's not the right
solution, but it works (and anyway, this catalog had to be patched,
because it uses the DTDDECL keyword which is not supported by Jade).
Tell me if you have found a better solution.

All of this discussion, according to me, shows that it was necessary to
embetter the docbook-tools distribution, and to normalize the choices.
-- 
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 ` David Mason
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 ` David Mason
2000-12-27  6:36   ` Norman Walsh
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 ` 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           ` 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               ` Jorge Godoy
2000-12-27  6:36               ` Jochem Huhmann
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           ` Eric Bischoff
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   ` Jorge Godoy
2000-12-27  6:36 Evolution of the DocBook tools Gregory Leblanc
2000-12-27  6:36 ` Eric Bischoff
  -- strict thread matches above, loose matches on Subject: below --
2000-12-27  6:36 Peter Ring
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=38B533C6.C543446A@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).