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

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

On Tue, 29 May 2001, wrote:
> Le Mardi 29 Mai 2001 01:29, Jorge Luiz Godoy Filho a écrit :
>> > Hi Jorge. I hope you are doing fine.
>> Hi! I'm OK, thanks. :-))
> Super! :-)

Thanks! And how about you? Too much work?

>> (...) For XML entities one uses Unicode representation, for SGML
>> not.
> I know. But XML files are SGML files (the contrary is not true) and
> SGML tools can use both entity sets. I'm not sure however that it
> would mean that we can get rid of the SGML-only version of the ISO
> entities, they way they are declared could have some impact, for
> example on stylesheets.
> 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. 

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

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

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

Be seeing you,
Godoy. <>

Suporte à Rede Conectiva de Serviços -- Conectiva Services Network Support
Conectiva S.A     -     -   +55 (41) 360-2600
Conectiva Inc.    -        -   +55 (41) 360-2600

  reply	other threads:[~2001-05-29  6:19 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 [this message]
2001-07-27 18:51                     ` Eric Bischoff
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 \
    --in-reply-to=m3wv70guha.fsf@dagon.conectiva \ \ \ \

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