|
Subject: RE: JScript error handling in msxsl ? From: Rob McDougall <RMcDouga@xxxxxxxxxxx> Date: Mon, 9 Mar 1998 11:46:45 -0500 |
In the example you cite, you could always generate a separate rule for
each combination of attributes. Yes, this isn't optimal, but it's the
way I did some similar things.
Rob
>-----Original Message-----
>From: Dave Carlson [SMTP:dcarlson@xxxxxxxxxxxxxx]
>Sent: Sunday, March 08, 1998 9:30 PM
>To: xsl-list@xxxxxxxxxxxxxxxx
>Subject: JScript error handling in msxsl ?
>
>[snip]
><rule>
> <target-element type="Field"/>
>
> <TR>
> <TD><eval>getAttribute("name")</eval></TD>
> <TD><eval>testAttribute(this, "type")</eval></TD>
> <TD><eval>testAttribute(this, "default")</eval></TD>
> <TD><eval>testAttribute(this, "enum")</eval></TD>
> </TR>
></rule>
>
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
| Current Thread |
|---|
|
| <- Previous | Index | Next -> |
|---|---|---|
| Re: JScript error handling in msxsl, Paul Prescod | Thread | RE: JScript error handling in msxsl, Jonathan Marsh |
| RE: select v. select-elements, Jonathan Marsh | Date | RE: JScript error handling in msxsl, Jonathan Marsh |
| Month |