public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gregory Leblanc <GLeblanc@cu-portland.edu>
To: 'Jorge Godoy' <godoy@conectiva.com.br>,
	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: <A5F46F4ED18FD211ABEE00105AC6CF077F7CD0@email.cu-portland.edu> (raw)

Please, mail the list when that list is online, I'm enjoying this
discussion.

> -----Original Message-----
> From: Jorge Godoy [ mailto:godoy@conectiva.com.br ]
> Sent: Thursday, February 24, 2000 4:45 AM
> To: Eric Bischoff
> Cc: docbook-tools-discuss@sourceware.cygnus.com
> Subject: Re: Evolution of the DocBook tools
> 
[snip]
> 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? 

I'd break them, but I'm just a mean nasty guy...

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

When everything gets hashed out, just make a .tar.gz.  I'm quite sure that
we can get a .spec file written for RPMs, either by myself or somebody who's
better at it.  debs should be easy to make from there.
	Greg
Sun Hardware Reference Maintainer
http://sun-ref.sunhelp.org/

             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 Gregory Leblanc [this message]
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           ` 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
  -- 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=A5F46F4ED18FD211ABEE00105AC6CF077F7CD0@email.cu-portland.edu \
    --to=gleblanc@cu-portland.edu \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=ebisch@cybercable.tm.fr \
    --cc=godoy@conectiva.com.br \
    /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).