ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Simon Pepping <spepping@scaprea.hobby.nl>
Subject: Re: Some XML typesetting questions
Date: Tue, 9 Oct 2001 21:10:07 +0200	[thread overview]
Message-ID: <20011009211007.A465@scaprea> (raw)
In-Reply-To: <5.1.0.14.1.20011009173610.02407e10@server-1>; from pragma@wxs.nl on Tue, Oct 09, 2001 at 05:38:34PM +0200

On Tue, Oct 09, 2001 at 05:38:34PM +0200, Hans Hagen wrote:
> At 11:53 AM 10/9/2001 +0200, Berend de Boer wrote:
> >Hans Hagen <pragma@wxs.nl> writes:
> >
> > > then, is this
> > >
> > > ENTITY bla SYSTEM "filename"
> > >
> > > the pattern to support?
> >
> >Exactly.
> >
> >It's often used in things like this:
> >
> >-----------------------
> ><?xml version="1.0" encoding="ISO-8859-1" ?>
> ><!DOCTYPE document [
> >   <!ENTITY body SYSTEM "body.xml">
> >   <!ENTITY sidebar SYSTEM "sidebar.xml">
> 
> yes, but according to bradley there can also be "yetanother.dtd" there so i 
> assume that the inclusion should be limited to xml ?
> 
> taco: what was this about graphics? Should &whatamess; then expand to 
> \externalfigure[whatamess] ? How does one know what is a figure?

I do not have the spec at hand, but I think these patterns occur:

<!DOCTYPE rootelement [
  <!ENTITY name SYSTEM "filename.xml">
  <!ENTITY name PUBLIC "PubId" "filename.xml">
  <!ENTITY figname SYSTEM "figname.gif" NOTATION gifimage>
]>

The notation marks it as a non-parsed entity, i.e., a non-xml
file. The notation must have been declared in the DTD or in the
internal part of the DTD.

<!NOTATION GIF		SYSTEM "GIF">
<!NOTATION GIF87a   PUBLIC
"-//CompuServe//NOTATION Graphics Interchange Format 87a//EN">

I do not think you can include a figure by just using an entity
&figname;. The entity should be the value of an attribute, e.g.
<!ENTITY eiffeltower SYSTEM "figures/eiffeltower.gif" NOTATION gifimage>
<imagedata entityref="eiffeltower" format="gif"/>.
But more direct approaches also occur:
<imagedata fileref="figures/eiffeltower.gif" format="gif"/>
(from docbook).

All entities may be parameter entities: <!ENTITY % name ..., but then
they can only contain pieces of DTD or ENTITIES.

Each public ID must be followed by a system ID. Public IDs are rarely
used for non-dtd files.

Public IDs and system IDs can be mapped to actual paths via an entity
resolver mechanism. In SGML that was the catalog; I am not sure how it
is done in XML. I guess you should only support unmapped system IDs.

So basically, you should indeed only support this pattern:

   ENTITY bla SYSTEM "filename"

Simon

-- 
Simon Pepping
email: spepping@scaprea.hobby.nl


  reply	other threads:[~2001-10-09 19:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-07 21:05 Jaroslav Snajdr
2001-10-08  7:07 ` Berend de Boer
2001-10-08  7:10 ` Berend de Boer
2001-10-08  9:25   ` Hans Hagen
2001-10-08 10:00     ` Berend de Boer
2001-10-08 16:15       ` Hans Hagen
2001-10-08 17:16         ` Berend de Boer
2001-10-09  7:24           ` Hans Hagen
2001-10-09  9:53             ` Berend de Boer
2001-10-09 15:38               ` Hans Hagen
2001-10-09 19:10                 ` Simon Pepping [this message]
2001-10-08 20:33     ` Simon Pepping
2001-10-09  7:40       ` Hans Hagen
     [not found] ` <87lmiksq01.fsf@dellius.nederware.nl>
2001-10-10  8:21   ` Hans Hagen
2001-10-23 11:08   ` 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=20011009211007.A465@scaprea \
    --to=spepping@scaprea.hobby.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).