At 2009-11-14 19:36 +0000, Michael Kay wrote:
> But I think it is all you have available to you to try. I
> know of no way to expose the current mode.
I can't think of any way of using the information, why would you want it?
Until modes become first class constructs, having this would have
been helpful in catch-all template rules that report a development
error of misspelling a mode (or in my case forgetting to add the
namespace qualification), or not having handled a particular node in
a particular mode.
I've long wanted to be able to expose the mode for such diagnostic purposes.
. . . . . . . . . Ken
--
Vote for your XML training: http://www.CraneSoftwrights.com/s/i/
Crane Softwrights Ltd. http://www.CraneSoftwrights.com/s/
Training tools: Comprehensive interactive XSLT/XPath 1.0/2.0 video
Video lesson: http://www.youtube.com/watch?v=PrNjJCh7Ppg&fmt=18
Video overview: http://www.youtube.com/watch?v=VTiodiij6gE&fmt=18
G. Ken Holman mailto:gkholman(_at_)CraneSoftwrights(_dot_)com
Male Cancer Awareness Nov'07 http://www.CraneSoftwrights.com/s/bc
Legal business disclaimers: http://www.CraneSoftwrights.com/legal
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--