From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Subtle problem nested XML
Date: Tue, 09 Oct 2001 16:44:27 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20011009164238.020c6500@server-1> (raw)
In-Reply-To: <20011009122051.720b1645.taco@elvenkind.com>
At 12:20 PM 10/9/2001 +0200, Taco Hoekwater wrote:
>Anyway, parsing the internal subset and/or DTDs is not hard nor is it
>overly expensive in computing type, so I will probably add that to the
>parser as soon as I understand it's inner workings again. (I need the
>ENTITY's, not for xml inclusion but for image inclusion).
I tend to stick to schemata without type specs -)
concerning entities, if i know what to support i can probably quite easily
build it into the system while watching a dull tv-show, so i need a simple
list:
<!ENTITY rubish SYSTEM "filename" -> include file
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
next prev parent reply other threads:[~2001-10-09 14:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-06 11:16 Berend de Boer
2001-10-06 19:12 ` Taco Hoekwater
2001-10-08 7:56 ` Hans Hagen
2001-10-08 18:06 ` Berend de Boer
2001-10-09 7:22 ` Hans Hagen
2001-10-09 9:49 ` Berend de Boer
2001-10-09 14:53 ` Hans Hagen
2001-10-09 7:31 ` Hans Hagen
2001-10-09 9:44 ` Berend de Boer
2001-10-09 14:57 ` Hans Hagen
2001-10-09 7:33 ` Hans Hagen
2001-10-09 9:51 ` Berend de Boer
2001-10-09 10:20 ` Taco Hoekwater
2001-10-09 14:44 ` Hans Hagen [this message]
2001-10-09 14:51 ` Hans Hagen
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=5.1.0.14.1.20011009164238.020c6500@server-1 \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/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 NNTP newsgroup(s).