From: "Pawel Jackowski na Onet" <jackos1@poczta.onet.pl>
Subject: Re: ConTeXt, XML and verbatim
Date: Thu, 4 Sep 2003 21:09:19 +0200 [thread overview]
Message-ID: <003501c37318$6b1f5250$0500a8c0@best> (raw)
In-Reply-To: <20030903201826.GB21844@swordfish>
Hi!
> On Wed, Sep 03, 2003 at 09:49:40PM +0200, Simon Pepping wrote:
> > >
> > > Meybe someone knowns how to 'translate' verbatim environments for XML
code?
> > > I mean how to define environment which I can use in this way [......]
> > There are no verbatim environments in XML, and you cannot get literal
> > content. Instead, you can have tags, like your verbatim above, that
> > request line-oriented layout. programlisting is such a tag in Docbook.
> That's correct with respect to elements--since XML deliberately avoids
> defining semantics for any element. But you seem to be overlooking
> CDATA sections, which are more-or-less verbatim environments. The XML
> spec doesn't directly address the question of formatting in CDATA
> sections, but all characters are supposed to be output literally, and
> AFAIK that includes white space--hence all formatting should be
> preserved.
>
> But I don't know if ConTeXt can handle CDATA sections. Can it?
Good question! As far as I'm concerned (but I'm not concerned far...)
ConTeXt can handle some 'metadata'
like <!ENTITY...>. But I don't know exaclty which levels of XML syntax is
handled with ConTeXt core.
I hope Hans will provide some workshops :)
Regards, Pawel
next prev parent reply other threads:[~2003-09-04 19:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 14:09 Pawel Jackowski na WP
2003-09-03 19:49 ` Simon Pepping
2003-09-03 20:18 ` Matt Gushee
2003-09-04 19:09 ` Pawel Jackowski na Onet [this message]
2003-09-04 19:28 ` Hans Hagen
2003-09-04 19:31 ` Hans Hagen
2003-09-06 15:49 ` Simon Pepping
2003-09-04 6:49 ` ConTeXt, XML and verbatim -- thanks Pawel Jackowski na Onet
2003-09-04 18:59 ` Hans Hagen
2003-09-05 8:34 ` ConTeXt, XML and verbatim Pawel Jackowski na Onet
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='003501c37318$6b1f5250$0500a8c0@best' \
--to=jackos1@poczta.onet.pl \
--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).