Re: To avoid converting html entities

Thanks for the reply, David.

You write: "On output the system will do the reverse translation
writing < as &lt;
and & and &amp;  so the end result will be as you wish with these entity
references being used in the result."

So my xsl code should work then ?

If the html entities have already been parsed as <> etc by the xml
parse, and the xsl processor has to output it in reverse, then I'm
afraid that's not happening in my case. Even without the
disable-output-escaping attribute.

Yhe output in the result html document is as follows:

<input type="hidden"
value="LX,LX,,,,243,1612,,,,DXB,ZRH,,,,ZRH,MXP,,,,20050701,20050701,,,,140,74
0,,,,20050701,20050701,,,,625,840,,,,B,B,,,,1,540,LX,EK,,,,1617,88,,,,MXP,ZRH
,,,,ZRH,DXB,,,,20050810,20050810,,,,1125,1545,,,,20050810,20050810,,,,1210,23
50,,,,B,V,,,,1,625,515000,571000,0,0,0,0,AED,86270166,0,0,0,2,0,0,0,,<RulesIn
fo><UniqueKey>1</UniqueKey><QuoteNum>1</QuoteNum><FareNum>1</FareNum><FareRul
eInfo>Y</FareRuleInfo><PermittedDisc>N</PermittedDisc><DiscAdultFare>N</DiscA
dultFare><Spare1>NNNYN</Spare1><StartPt>DXB</StartPt><EndPt>MXP</EndPt><First
TravDt>20050701</FirstTravDt><AirV>YY</AirV><FIC>MEE3M3</FIC><TotFareComponen
t>70109</TotFareComponent><Currency>NUC</Currency><DecPos>2</DecPos><FareAmt>
70109</FareAmt><RuleSupplierID>0</RuleSupplierID><RuleNumOrdinal>00F2F6</Rule
NumOrdinal><FareTariffNum>0016</FareTariffNum><RuleTextOrdinalNum>F0F5</RuleT
extOrdinalNum><RulesApply>Y</RulesApply><RtesApply>Y</RtesApply><NoRulesExist
>N</NoRulesExist><Spare2>NNNNN</Spare2><DBInd>N</DBInd><HostUseOnly91>N</Host
UseOnly91><PFQuoted>N</PFQuoted><Spare3>YNNNN</Spare3><DBID
/><FareRuleInfoYQual><GlobDirOrdinal>EH</GlobDirOrdinal><HIFCity1
/><HIFCity2
/><MileSurchargeRtgInd>1</MileSurchargeRtgInd><FlownMileComponent>3096</Flown
MileComponent><MPMComponent>3480</MPMComponent><DifBetween>0</DifBetween><Ext
raMileCity1
/><ExtraMileCity2 /><ExtraMileCity3
/><OTWTransportingAirV>LX</OTWTransportingAirV><ComponentAirV1
/><ComponentAirV2 /></FareRuleInfoYQual></RulesInfo>
&amp;lt;xsl:output cdata-section-elements=&quot;&quot;/>. "><input
type="hidden"
value="LX,LX,,,,243,1612,,,,DXB,ZRH,,,,ZRH,MXP,,,,20050701,20050701,,,,140,74
0,,,,20050701,20050701,,,,625,840,,,,B,B,,,,1,540,LX,EK,,,,1617,88,,,,MXP,ZRH
,,,,ZRH,DXB,,,,20050810,20050810,,,,1125,1545,,,,20050810,20050810,,,,1210,23
50,,,,B,V,,,,1,625,515000,571000,0,0,0,0,AED,86270166,0,0,0,2,0,0,0,,<RulesIn
fo><UniqueKey>1</UniqueKey><QuoteNum>1</QuoteNum><FareNum>1</FareNum><FareRul
eInfo>Y</FareRuleInfo><PermittedDisc>N</PermittedDisc><DiscAdultFare>N</DiscA
dultFare><Spare1>NNNYN</Spare1><StartPt>DXB</StartPt><EndPt>MXP</EndPt><First
TravDt>20050701</FirstTravDt><AirV>YY</AirV><FIC>MEE3M3</FIC><TotFareComponen
t>70109</TotFareComponent><Currency>NUC</Currency><DecPos>2</DecPos><FareAmt>
70109</FareAmt><RuleSupplierID>0</RuleSupplierID><RuleNumOrdinal>00F2F6</Rule
NumOrdinal><FareTariffNum>0016</FareTariffNum><RuleTextOrdinalNum>F0F5</RuleT
extOrdinalNum><RulesApply>Y</RulesApply><RtesApply>Y</RtesApply><NoRulesExist
>N</NoRulesExist><Spare2>NNNNN</Spare2><DBInd>N</DBInd><HostUseOnly91>N</Host
UseOnly91><PFQuoted>N</PFQuoted><Spare3>YNNNN</Spare3><DBID
/><FareRuleInfoYQual><GlobDirOrdinal>EH</GlobDirOrdinal><HIFCity1
/><HIFCity2
/><MileSurchargeRtgInd>1</MileSurchargeRtgInd><FlownMileComponent>3096</Flown
MileComponent><MPMComponent>3480</MPMComponent><DifBetween>0</DifBetween><Ext
raMileCity1
/><ExtraMileCity2 /><ExtraMileCity3
/><OTWTransportingAirV>LX</OTWTransportingAirV><ComponentAirV1
/><ComponentAirV2 /></FareRuleInfoYQual></RulesInfo>">

Thanks,

Ahsan

On 6/8/05, David Carlisle <davidc@xxxxxxxxx> wrote:
>
>   I want to select (and output) the above data, without converting the
>   html entities above to < & >, etc.
>
>
> The XML parser will already have done that conversion before XSLT sees
> the input, as that's what parsers do.
>
> On output the system will do the reverse translation writing < as &lt;
> and & and &amp;  so the end result will be as you wish with these entity
> references being used in the result.
>
> Or at least that would be the default behaviour unless you have stopped
> that happening by using  disable-output-escaping="yes" It is rarely a
> good idea to use this attribute unless you really need it. In this case
> however you are using d-o-e inside an attribute where it is specified as
> having no effect so < should be written out as &lt; Is that not what you
> are getting?
>
>   Another quick question.. Is it possible to write the above xsl code in
>   such a way that the input tag is output as <input />, and _not_
>   <input></input>
>
> The choice of empty element syntax is not under the control of the
> stylesheet author. Most sytems do use /> for empty elements. msxml uses
> either syntax depending on some heuristics that try to make it use the
> same form as used for input.
> so actually using the equivalent form
>
>
> <input type="hidden" value="{PostData}"/>
>
> might work and persuade msxml to use the /> syntax.
>
> David
>
> ________________________________________________________________________
> This e-mail has been scanned for all viruses by Star. The
> service is powered by MessageLabs. For more information on a proactive
> anti-virus service working around the clock, around the globe, visit:
> http://www.star.net.uk
> ________________________________________________________________________
>
>


--
Muted Musings - http://doubleletter.blogspot.com