Am 2015-09-15 um 00:09 schrieb Jan Tosovsky :
> XSLT 1.0 is capable to handle anything (turing machine).
> XSLT 2.0 brings some syntactic sugar.
> XSLT 3.0 supports streaming.
>
> If you need 2.0 features, you can use Saxon-B 9.1.0.8 (free, but not
> maintained any more).
Thank you, I’ll first t
On 2015-09-12 Henning Hraban Ramm wrote:
> Am 2015-09-12 um 18:14 schrieb luigi scarso :
>
> > Do you know a good XSLT processor except Saxon? Its free version is
> > just too limited.
> >
> > xsltproc for xslt 1.0, but you are looking for xslt 2.0 , right ?
>
> No, the only extension from comme
Am 2015-09-13 um 02:53 schrieb Aditya Mahajan :
>> Do you know a good XSLT processor except Saxon? Its free version is just too
>> limited.
>
> Why not just use your favorite programming language; most languages have a
> decent XML parsing library?
Yes of course (mine is Python). I don’t know
On Sat, Sep 12, 2015 at 2:28 PM, Henning Hraban Ramm wrote:
> Am 2015-09-12 um 18:14 schrieb luigi scarso :
>
> >> Do you know a good XSLT processor except Saxon? Its free version is
> just too limited.
> >
> > xsltproc for xslt 1.0, but you are looking for xslt 2.0 , right ?
>
> More like 3.0, I
On Sat, 12 Sep 2015, Henning Hraban Ramm wrote:
Do you know a good XSLT processor except Saxon? Its free version is just
too limited.
Why not just use your favorite programming language; most languages have a
decent XML parsing library?
Aditya
___
On 9/12/2015 2:14 PM, luigi scarso wrote:
xsltproc for xslt 1.0, but you are looking for xslt 2.0 , right ?
for regular transformations that's good enough
Hans
-
Hans Hagen | PRAGMA ADE
Am 2015-09-12 um 18:14 schrieb luigi scarso :
>> Do you know a good XSLT processor except Saxon? Its free version is just too
>> limited.
>
> xsltproc for xslt 1.0, but you are looking for xslt 2.0 , right ?
More like 3.0, I guess ;)
No, the only extension from commercial Saxon that I would nee
On 12/09/15 13:00, Hans Hagen wrote:
> On 9/12/2015 1:37 PM, Toby Miller wrote:
>> Thank you! That's exactly what I was looking for.
>>
>> I have a few other things I'd like to be able to do with this kind of
>> thing (print '' self-closed tags for example, and add attributes
>> as you say), but
On 12/09/15 13:14, Hans Hagen wrote:
> On 9/12/2015 2:04 PM, Henning Hraban Ramm wrote:
>> Am 2015-09-12 um 17:37 schrieb Toby Miller :
>>
>>> I have a few other things I'd like to be able to do with this kind of
>>> thing (print '' self-closed tags for example, and add attributes
>>> as you say)
On Sat, Sep 12, 2015 at 2:04 PM, Henning Hraban Ramm wrote:
> Am 2015-09-12 um 17:37 schrieb Toby Miller :
>
> > I have a few other things I'd like to be able to do with this kind of
> > thing (print '' self-closed tags for example, and add attributes
> > as you say), but I feel bad about posting
On 9/12/2015 2:04 PM, Henning Hraban Ramm wrote:
Am 2015-09-12 um 17:37 schrieb Toby Miller :
I have a few other things I'd like to be able to do with this kind of
thing (print '' self-closed tags for example, and add attributes
as you say), but I feel bad about posting to the list for them. Is
Am 2015-09-12 um 17:37 schrieb Toby Miller :
> I have a few other things I'd like to be able to do with this kind of
> thing (print '' self-closed tags for example, and add attributes
> as you say), but I feel bad about posting to the list for them. Is there
> any documentation for these features
On 9/12/2015 1:37 PM, Toby Miller wrote:
Thank you! That's exactly what I was looking for.
I have a few other things I'd like to be able to do with this kind of
thing (print '' self-closed tags for example, and add attributes
as you say), but I feel bad about posting to the list for them. Is the
Thank you! That's exactly what I was looking for.
I have a few other things I'd like to be able to do with this kind of
thing (print '' self-closed tags for example, and add attributes
as you say), but I feel bad about posting to the list for them. Is there
any documentation for these features at
On 9/11/2015 4:21 PM, Toby Miller wrote:
I'm using ConTeXt's export to XML feature, but I'd like more control
over the XML output. Is there a way to define a TeX command that will
output a specific tag (content) around some text in the output?
\setupbackend[export=yes]
\definehighlight[this]
I'm using ConTeXt's export to XML feature, but I'd like more control
over the XML output. Is there a way to define a TeX command that will
output a specific tag (content) around some text in the output?
Ideally I'd like to write a completely custom XML printer; it would be
very simple, but would a
16 matches
Mail list logo