Re: [xsl] Template matching preceding-sibling.
Subject: Re: [xsl] Template matching preceding-sibling.|
From: Wendell Piez <wapiez@xxxxxxxxxxxxxxxx>
Date: Fri, 16 Nov 2007 12:14:30 -0500
No insult is taken, at least not by me. I was just taking the risk of
muddying the waters further, by perturbing them in hopes that things
might become clearer.
At 12:24 AM 11/16/2007, you wrote:
Having read this, I have strong feeling (correct me if I'm wrong)
that my message was seen as if I was somehow blaming the list
members for not running the actual transformation, which is
definetely NOT the meaning of my post, by no mean!
I wouldn't go that far (at least I didn't take your message to mean
you were blaming anyone), but on the other hand, how much work we
impose on one another, in an all-volunteer public forum, can be an
issue (and has been in the past). As I said, sometimes I'm guilty of
cutting corners in the hope that it will "cut to the chase" (a fine
metaphor from the cinema). So there you have it.
In opposite, I find it amusing that contributors to this list can
deduce the real problem and suggest the working solution without
actually writing and testing any single line of code!
Indeed. But then, we see the same issues over and over. (Which leads
to problems when something new turns up and we think it's something old.)
All I wanted to know is just whether somebody got the result I
obtained, and my speculations about possible not running the
transformation and in-mind analysis were in this sense only. It's
important since if my assumption is wrong then my template
processing software is giving incorrect results and it's obviously
odd and requires serious analysis.
Right. One way of addressing this is to show us exact code with input
and results (pasted please) in minimal form and also tell us what
processor you're running. There are list readers who run several
different processors in order to check exactly this kind of thing,
and can confirm what you're seeing or help to analyze relevant
factors if they can't. Also, we can collectively establish quite
quickly what a processor should be doing in a given specific case --
that is, the relevant expertise is available to expose mistaken
assumptions and even reasonable but incorrect interpretations.
After all, it is of interest to us when a processor fails: we like to
know which one it is, and when possible, the exact nature and scope
of the problem. And developers have an extra incentive to fix bugs
quickly once they are exposed on this list. For which, of course,
they are rewarded by being able to announce it.
Wendell Piez mailto:wapiez@xxxxxxxxxxxxxxxx
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
Mulberry Technologies: A Consultancy Specializing in SGML and XML
Ilya Konanykhin - Fri, 16 Nov 2007 11:24:08 +0600
- Wendell Piez - Fri, 16 Nov 2007 12:14:30 -0500 <=
- Message not available