Lists Home |
Date Index |
- From: John Cowan <email@example.com>
- To: XML Dev <firstname.lastname@example.org>
- Date: Mon, 22 Jun 1998 17:23:09 -0400
Peter Murray-Rust wrote:
> Unless there is
> sensible running text whose prime purpose is to be read by humans there is
> no particular value in having mixed content (i.e. strings + elements mixed).
I have an application in mind (which I'm not ready to disclose publicly
yet) which will have many elements with mixed content, of the form
"running text with occasional empty elements in it". This text
will not necessarily be meant for human consumption: it may be
programming language code.
> The responsible thing to do is to provide enough DTD information to make
> it clear that the prettyprinting whitespace is insignificant. It only needs
> a few contentspecs in the internal subset. Thus <ELEMENT foo (bar | baz)*>
> will drive SAX to identify any whitespace children of foo and flag it as
Not necessarily! Depending on the underlying parser, SAX may or may
not report the WS as ignorable-WS.
> I suspect that for newcomers to XML prettyprinting will be the de facto
> standard. They won't realise the whitespace issue even exists. However,
> when JUMBO2 reads an unknown file without a DTD it faithfully displays
> whitespace-only nodes. To try to help this I have a button in JUMBO2 called
> 'delete whitespace'. This will remove whitespace PCDATA recursively from
> the descendants of a selected node (or the root node if none selected).
John Cowan http://www.ccil.org/~cowan email@example.com
You tollerday donsk? N. You tolkatiff scowegian? Nn.
You spigotty anglease? Nnn. You phonio saxo? Nnnn.
Clear all so! 'Tis a Jute.... (Finnegans Wake 16.5)
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)