Re: [xsl] Position() Function Using Filter

[Lighton Phiri <lighton.phiri@xxxxxxxxx>]

I suppose it mostly due to the fact that when I recently started
working with xslt, I naturally found it a lot easier to work with 1.0
since I had xsltproc installed by default. But after seeing the
benefits 2.0 has to offer, I believe its high time I switched.

Lighton Phiri
http://lightonphiri.org/
@lightonphiri




On 29 October 2011 17:53, Vasu Chakkera <vasucv@xxxxxxxxx> wrote:
> why would you want to have more than one processors? saxon is good
> enough and is very actively supported. unless you really have a
> situation where you have to use more than one processor ( i cant see
> ).. The features of XSLT2 are too good to miss.
> Vasu
>
> On 29 October 2011 06:35, Lighton Phiri <lighton.phiri@xxxxxxxxx> wrote:
>> I am new to xslt --and could be wrong here-- but the few resources I
>> have come across all seem to point to the fact that xslt 2.0 is only
>> supported by a few processors --I only know of SAXON. I am trying to
>> avoid that limitation. There are cases when I use SAXON though.
>>
>> Lighton Phiri
>> http://lightonphiri.org/
>> @lightonphiri
>>
>>
>>
>>
>> On 29 October 2011 14:07, Vasu Chakkera <vasucv@xxxxxxxxx> wrote:
>>>>I am working with
>>>> xslt 1.0
>>> Why?? (just out of interest..)
>>>
>>> On 28 October 2011 15:34, Lighton Phiri <lighton.phiri@xxxxxxxxx> wrote:
>>>> Thanks all the the valuable feedback. The count approach suggested by
>>>> Andrew& Brandon did the trick :) --count(preceding-sibling::*)
>>>> Awesome!
>>>>
>>>> just so you know, I forgot an important detail --I am working with
>>>> xslt 1.0 and so "index-of and " and the book[tokenize(., '/')[last()]
>>>> eq $bpage] hint wont work.
>>>>
>>>> Lighton Phiri
>>>> http://lightonphiri.org/
>>>> @lightonphiri
>>>>
>>>>
>>>>
>>>>
>>>> On 28 October 2011 21:01, Imsieke, Gerrit, le-tex
>>>> <gerrit.imsieke@xxxxxxxxx> wrote:
>>>>>
>>>>>
>>>>> On 2011-10-28 20:17, Liam R E Quin wrote:
>>>>>>
>>>>>> On Fri, 2011-10-28 at 10:27 -0400, Murray McDonald wrote:
>>>>>>>
>>>>>>> If you are sure that there will be one and only one "match" then the
>>>>>>> '[1]'
>>>>>>> is unnecessary
>>>>>>>
>>>>>>> index-of(//book, //book[ends-with(., 'ASTRO_00007.JPG')])[1]
>>>>>>
>>>>>> On the other hand, the difference between /a/b/c[1] and (/a/b/c)[1] is
a
>>>>>> major source of confusion for the newcomer and the "perpetual
>>>>>> intermediate" [1] alike.
>>>>>
>>>>> Thanks for confusing the perpetual intermediate with a [1] that looks
like a
>>>>> positional predicate but that actually is a citation link. Pun
intended?
>>>>>
>>>>>>
>>>>>> Sometimes you have to make the computer work a little harder if it
means
>>>>>> getting the right answer more often.
>>>>>
>>>>> Agree [+1].
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Vasu Chakkera
>>> NodeLogic Limited
>>> Oxford
>>> www.node-logic.com
>>> ==============
>>
>>
>
>
>
> --
> Vasu Chakkera
> NodeLogic Limited
> Oxford
> www.node-logic.com
> ==============