> On a more serious note, XSLT is not designed for string
> processing. This might be bearable with XSLT2, but still a
> curious design choice.


Not quite true. XSLT 2 and XPath F & O provide powerful text-
processing functions, including RegEx processing.

I have had some nice experience implementing a generalized LR(1)
parser in XSLT, a JSON to XML convertor (the f:json-document()
function of FXSL), an XPath 2.0 parser, a spell checker, a concordance
tool, a text justification tool -- all with reasonable efficiency (for
example the spellchecker processes several thousand words per second).


Cheers,
Dimitre Novatchev



On Feb 6, 1:43=A0am, Pavel Lepin <p.le...@ctncorp.com> wrote:
> Francesc001 <francesc...@hotmail.com> wrote in
> <b74f9c0e-a46c-4d7e-9bcb-bae1ad485...@d70g2000hsb.googlegroups.com>:
>
>
>
>
>
> > On 5 feb, 16:08, Martin Honnen <mahotr...@yahoo.de> wrote:
> >> ButXSLTtransforms a tree, usually created by parsing
> >> XML, to XML or HTML or plain text. I don't see how you
> >> would applytemplatesto plain text. You would need to
> >> write a parser first for your plain text format to emit
> >> XML but then you would not needXSLTany longer.
>
> > I willcreatean XML document with a simple tree, like
> > this....
>
> > <MyXMLDoc>
> > =A0 =A0 <Parameter>1234</Parameter>
> > =A0 =A0 <Data>Here it is string to process</Data>
> > </MyXMLDoc>
>
> > I need aXSLTwho take <Data> and split its fields to a
> > new XML file. I look for atoolfor creating thisXSLT.
>
> Thetoolyou're looking for is commonly called "brain" and
> humans are typically supplied with one at birth. If you
> have lost or misplaced yours, contact your vendor's
> customer support centre for a replacement.
>
> On a more serious note,XSLTis not designed for string
> processing. This might be bearable with XSLT2, but still a
> curious design choice.
>
> --
> When all you have is a transformation engine, everything
> looks like a tree.- Hide quoted text -
>
> - Show quoted text -