public inbox for
 help / color / mirror / Atom feed
From: Eric Bischoff <>
To: Jorge Luiz Godoy Filho <>
Cc: <>
Subject: Re: Support for XML iso entities
Date: Fri, 27 Jul 2001 18:51:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <m3wv70guha.fsf@dagon.conectiva>

On Tuesday 29 May 2001 15:22, Jorge Luiz Godoy Filho wrote:
> >> > Hi Jorge. I hope you are doing fine.
> >>
> >> Hi! I'm OK, thanks. :-))
> >
> > Super! :-)
> Thanks! And how about you? Too much work?

As you can say with the date of this reply, yes :-(.

> > I've simply been putting everything together because of this
> > interoperability, and to avoid multiplying the number of
> > packages. Don't you think we've got already enough of them? ;-)
> No, I don't. As a base package for SGML processing, I think it should
> be only for SGML processing. Without caring for what tool can or
> cannot use it. If the specs says that we should use those entities in
> some specific way, that's what we should go for.

The problem is that XML processing is SGML processing.

> XML specs says that entities must be specified in Unicode. So, the
> specs requires different things. Besides, I don't see any problem
> having a package with only XML entities (and that package might
> requires sgml-common, for the catalog installation and other tools).

I don't see any problem with having only one package either.

> > I agree that a separate xml-common package could be a valid
> > technical solution, I just don't really see a good reason why we
> > should go this way.
> The reason is: having fewer things, makes you worry with fewer
> problems. And (I know disk is cheap) it will make our packages smaller
> and more specific to a desired function.

Come on... sgml-common is ridiculously small, and now you want to split it 

> > Everything this package contains are very basic and small
> > ressources, although a bit heterogeneous. I think that both versions
> > of the ISO entities go well together in this package.
> I still think that there should be an xml-common. BUT, I don't want to
> push you to this decision. I just want, if it will be in the same
> package, to be able to split them here and have all the tools
> working. There should be no requirement os assumption on any of the
> tools that I will always have both XML and SGML stuff together since
> this isn't true. People get really lost with this complex system and
> all this catalog and entities stuff... Having unused stuff installed
> there will make them even more confused.

Having too much packages doesn't help a lot with respect to complexity either.

> As I saida, this is only my opinion. If you decide not to take it,
> I'll accept and keep on using the packages. :-)

I'm no dictator ;-). I need to speak about this with Mark Galassi. A lot of 
people seem to (unfortunately ;-) ) agree with you.

Sad you didn't make it to go to San Diego. We could have met.

  reply	other threads:[~2001-07-27 18:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-22  4:08 Docbook on Mandrake 7.2/8.0 Gary Stainburn
2001-05-22  4:55 ` Eric Bischoff
2001-05-24  8:16   ` Gary Stainburn
2001-05-24 10:28     ` Eric Bischoff
2001-05-25 17:08       ` HTML 2 DocBook tool Poet/Joshua Drake
2001-05-26  0:04         ` Support for XML iso entities Eric Bischoff
2001-05-28  5:31           ` Jorge Luiz Godoy Filho
2001-05-28  9:24             ` Eric Bischoff
2001-05-28 16:25               ` Jorge Luiz Godoy Filho
2001-05-29  1:47                 ` Eric Bischoff
2001-05-29  6:19                   ` Jorge Luiz Godoy Filho
2001-07-27 18:51                     ` Eric Bischoff [this message]
2001-08-12 15:39                       ` Jorge Godoy
2001-05-30  4:37       ` Tex Capacity Exceeded (was Docbook on Mandrake 7.2/8.0) Gary Stainburn
2001-05-30  5:28         ` Eric Bischoff
2001-05-30  7:33           ` Gary Stainburn
2001-08-15  2:38 Support for XML iso entities Peter Ring

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

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