public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Eric Bischoff <e.bischoff@noos.fr>
To: Jorge Luiz Godoy Filho <godoy@conectiva.com>
Cc: <docbook-tools-discuss@sourceware.cygnus.com>
Subject: Re: Support for XML iso entities
Date: Tue, 29 May 2001 01:47:00 -0000	[thread overview]
Message-ID: <01052910534905.01734@boson.caldera.de> (raw)
In-Reply-To: <m3elt99hn2.fsf@dagon.conectiva>

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

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! :-)

> >> Don't do that. Instead create an xml-common. XML entities are not
> >> required to proccess SGML documents and SGML entities aren't
> >> required to proccess XML documents.
> >
> > But you can use SGML entities to process XML documents and XML
> > entities to process SGML documents. There is interoperability.
>
> (...) 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? ;-)

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. 

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.

-- 
Éric Bischoff  -  Documentation and Localization
Caldera (Deutschland) GmbH - Linux for eBusiness
Tel: +49 9131 7192 300 -  Fax: +49 9131 7192 399
http://www.caldera.de/

  reply	other threads:[~2001-05-29  1:47 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 [this message]
2001-05-29  6:19                   ` Jorge Luiz Godoy Filho
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:
  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=01052910534905.01734@boson.caldera.de \
    --to=e.bischoff@noos.fr \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=godoy@conectiva.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).