If you're outputting in UTF-8, it can express all of Unicode directly (as 
two- or three-byte sequences if necessary), so Numeric Character 
References generally won't be needed and won't be produced.

If you set the output encoding to ASCII rather than UTF-8, any characters 
over 127 will be escaped as Numeric Character References (since ASCII is a 
seven-bit code).

Other encodings will differ in what they can escape directly vs. what they 
have to escape.



______________________________________
"... Three things see no end: A loop with exit code done wrong,
A semaphore untested, And the change that comes along. ..."
  -- "Threes" Rev 1.1 - Duane Elms / Leslie Fish (
http://www.ovff.org/pegasus/songs/threes-rev-11.html)

Jesper Møller <jes...@selskabet.org> wrote on 04/02/2010 11:42:19 AM:

> From:
> 
> Jesper Møller <jes...@selskabet.org>
> 
> To:
> 
> "xalan-dev@xml.apache.org" <xalan-dev@xml.apache.org>
> 
> Cc:
> 
> "<xalan-dev@xml.apache.org>" <xalan-dev@xml.apache.org>
> 
> Date:
> 
> 04/02/2010 11:46 AM
> 
> Subject:
> 
> Re: problem in disable-output-escaping
> 
> Hi!
> The entities &#246;&#233;&#217;&#210; are all read into their 
> internal Java char representation, and since the codepoints in 
> question would never be encoded as entities, there is no escaping to 
disable.
> 
> BTW: This kind of question is more suited for the 'users' mail list
> 
> Hope this helps!
> 
> -Jesper
> 
> On 02/04/2010, at 07.44, "dipesh" <dipe...@erevmax.com> wrote:

> Hi All,
> 
> I used XSLT for transforming one xml to another xml.
> 
> Input XML contain some ISO 8859 value like 
> 
>                                     <Address Type='1'>
>                                         <AddressLine></AddressLine>
> 
> <CityName>&#246;&#233;&#217;&#210;</CityName>  
>                                     </Address>
> 
> I am using xslt which looks like this 
> 
>                   <?xml version="1.0" encoding="UTF-8"?>
> <xsl:stylesheet version="1.0" xmlns:xsl="
http://www.w3.org/1999/XSL/Transform
> " >
> <Address>
>                        <xsl:attribute name="Type" namespace="">
>                              <xsl:value-of select="string
> ($var32_ProfileInfo/ns0:Profile/ns0:Customer/ns0:Address/@Type)"/>
>                        </xsl:attribute> 
>                            <AddressLine>
>                                <xsl:value-of select="string
> (ns0:Customer/ns0:Address/ns0:AddressLine)"/>
>                            </AddressLine>
>                            <xsl:text disable-output-escaping="no" 
> >"&#246;&#233;&#217;&#210;"</xsl:text>
>                            <CityName>
>                              <xsl:value-of 
> 
select="$var32_ProfileInfo/ns0:Profile/ns0:Customer/ns0:Address/ns0:CityName" 

> disable-output-escaping="yes"/>
>                            </CityName>
>                     </Address>
>                   </xsl:stylesheet>
> 
> Now I want that output xml shold be like this
> 
>                   <Address Type='1'>
>                                         <AddressLine></AddressLine>
>                                          &#246;&#233;&#217;&#210;
> 
> <CityName>&#246;&#233;&#217;&#210;</CityName>  
>                                     </Address>
> 
> But it gives output like this
> 
>                                    <Address Type='1'>
>                                         <AddressLine></AddressLine>
>                                          öéÙÒ
>                                         <CityName>öéÙÒ</CityName>  
>                                     </Address>
> 
> 
> Can anybody can tell me how I can solve this problem
> 
> DISCLAIMER
> This email message and any accompanying attachments may contain 
> confidential information.
> If you are not the intended recipient, do not read, use, 
> disseminate, distribute or copy
> this message or attachments. If you have received this message in 
> error, please notify the
> sender immediately and delete this message. Any views expressed in 
> this message are those
> of the individual sender, except where the sender expressly, and 
> with authority, states
> them to be the views of eRevMax Technologies, Inc. Before opening 
> any attachments, please
> check them for viruses and defects.

Reply via email to