[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: manipulating whole XML documents as text

• To: <xml-dev@l...>
• Subject: Re: manipulating whole XML documents as text
• From: "Rick Jelliffe" <ricko@a...>
• Date: Wed, 20 Mar 2002 18:43:12 +1100
• References: <1016553671.5546.31.camel@l...> <p05100303b8bd1253a3aa@[128.148.157.217]> <1016560898.5546.44.camel@l...>

From: "Simon St.Laurent" <simonstl@s...>
> If I wanted to replace text that was partially in one element and
> partially in a sibling, there'd be a lot of juggling to do.  It may not
> be worth bothering, but it's worth considering.

In OmniMark you can do this kind of thing. 

1) You can text process documents coming in, and change the
mode of the text processor based on the current state of the
(subsequent) parser.

2) You can defer generate text output until after an element has
been fully read in, and generate whatever equivalent output
is required.

OmniMark is rather like XSLT with Perl stuck on the front-end,
except you generate text (by default) not WF XML and the
XSLT and Perl can communicate. 

Markup-aware text processing certainly has its place. 

Cheers
Rick Jelliffe

• References:
  • manipulating whole XML documents as text
    • From: "Simon St.Laurent" <simonstl@s...>
  • Re: manipulating whole XML documents as text
    • From: "David G. Durand" <david@d...>
  • Re: manipulating whole XML documents as text
    • From: "Simon St.Laurent" <simonstl@s...>

• Prev by Date: Re: which came first: content or markup?
• Next by Date: Re: which came first: content or markup?
• Previous by thread: Re: manipulating whole XML documents as text
• Next by thread: RE: XSLT and the 80/20 point (was RE: Tim Bray on "Which Technologies Matter?")
• Index(es):
  • Date
  • Thread