, April 02, 2010 11:08 PM
To: xalan-dev@xml.apache.org
Subject: Re: problem in disable-output-escaping
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 an
xml.apache.org"
>
> Cc:
>
> ""
>
> Date:
>
> 04/02/2010 11:46 AM
>
> Subject:
>
> Re: problem in disable-output-escaping
>
> Hi!
> The entities öéÙÒ are all read into their
> internal Java char representation, and since the cod
g/1999/XSL/Transform
" >
>"öéÙÒ"
select="$var32_ProfileInfo/ns0:Profile/ns0:Customer/ns0:Address/
ns0:CityName" disable-output-escaping="yes"/>
Hi All,
I used XSLT for transforming one xml to another xml.
Input XML contain some ISO 8859 value like
öéÙÒ
I am using xslt which looks like this
[ http://issues.apache.org/jira/browse/XALANJ-2300?page=all ]
Brian Minchau resolved XALANJ-2300:
---
Fix Version: Latest Development Code
Resolution: Duplicate
Resolving as a duplicate of xalanj-2210
> Bug with disable-output-escaping w
submitting my bug, but I did not notice
XALANJ-2218.
Kind regards,
Andre Powroznik
> Bug with disable-output-escaping when using XSLTC and 2 TransformerHandler
> --
>
> Key: XALANJ-2300
>
ct on this field's initial value.
As for your suggestion on org.apache.xalan.xsltc.runtime.StringValueHandler, I
suspect that you might be right, but haven't looked into that part.
- Brian Minchau
> Bug with disable-output-escaping when using XSLTC and 2
"bool"? (the "setEscaping" method is supposed to return the previous
escaping value).
> Bug with disable-output-escaping when using XSLTC and 2 TransformerHandler
> --
>
> Key: XAL
the issue.
org.apache.xalan.xsltc.compiler.ValueOf.translate() "calls" this method twice
only when _escaping is set to false (once to set it (to disable output
escaping) and once to reset it). If the default value of
org.apache.xml.serializer.ToXMLSAXHandler.m_escapeSetting is se
Bug with disable-output-escaping when using XSLTC and 2 TransformerHandler
--
Key: XALANJ-2300
URL: http://issues.apache.org/jira/browse/XALANJ-2300
Project: XalanJ2
Type: Bug
Components
think of to do what you are trying to do
what I think you are doing would be to construct a text node using
disable-output-escaping that represents the entire input element tag, like this:
<input type="text" SIZE="62" name="text1"
value="
" />
How
ble output escaping applied to it, but this only
applies to text nodes.
>
> disable-output-escaping="yes" is not working
> --
>
> Key: XALANJ-2243
>
and post a _complete_ description of
your problem and include a minimal sample stylesheet and source document.
Otherwise, no one will be able to help you.
>
> disable-output-escaping="yes"
elp
regards
sarajit
>
> disable-output-escaping="yes" is not working
> --
>
> Key: XALANJ-2243
> URL: http://issues.apache.org/jira/browse/XALANJ-
for something other than a text node in the result tree. Thus, it is an error
to disable output escaping for an xsl:value-of or xsl:text element that is used
to generate the string-value of a comment, processing instruction or attribute
node... an XSLT processor may signal the error; if it does not
s working
please help.
regards
>
> disable-output-escaping="yes" is not working
> --
>
> Key: XALANJ-2243
> URL: http://issues.apache.org/
input is "&ab" then it will give parsing error. thats why
i have used it like this (This is coming from
some xml file)
For
and all it is working fine.
Only when i am assigning to
then it is showing تنن as output
please help.
regards
>
> disable-output-escaping=
[
http://issues.apache.org/jira/browse/XALANJ-2243?page=comments#action_12359339
]
David Bertoni commented on XALANJ-2243:
---
You seem to be misunderstanding what CDATA sections are, and what
disable-output-escaping accomplishes. By placing what
disable-output-escaping="yes" is not working
--
Key: XALANJ-2243
URL: http://issues.apache.org/jira/browse/XALANJ-2243
Project: XalanJ2
Type: Bug
[ http://issues.apache.org/jira/browse/XALANJ-1709?page=all ]
Brian Minchau closed XALANJ-1709:
-
Assign To: (was: Xalan Developers Mailing List)
> XSLTC, disable-output-escaping="yes" works on xsl:value-of but
gzilla/show_bug.cgi?id=24268
XSLTC, disable-output-escaping="yes" works on xsl:value-of but not xsl:text
[EMAIL PROTECTED] changed:
What|Removed |Added
gzilla/show_bug.cgi?id=24268
XSLTC, disable-output-escaping="yes" works on xsl:value-of but not xsl:text
[EMAIL PROTECTED] changed:
What|Removed |Added
gzilla/show_bug.cgi?id=24268
XSLTC, disable-output-escaping="yes" works on xsl:value-of but not xsl:text
Summary: XSLTC, disable-output-escaping="yes" works on xsl:value-
of but not xsl:text
Product: XalanJ2
Version: CurrentCVS
o make it multi-byte
safe.
Thanks for the suggestion, ISO-8859-1 works fine.
From: "Voytenko, Dimitry" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
Subject: RE: value-of with disable-output-escaping=&quo
II is subset of it. Method "text" will also ensure that none of tags you
might try to output will go in the result.
Dmitry
-Original Message-
From: Foxy Shadis [mailto:[EMAIL PROTECTED]]
Sent: Saturday, November 30, 2002 20:32
To: [EMAIL PROTECTED]
Subject: RE: value-of with disable-
Reply-To: [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
Subject: RE: value-of with disable-output-escaping="yes"
Date: Sat, 30 Nov 2002 20:11:39 -0800
Oh, I see, you use disable-output-escaping="yes". That's why Xalan doesn't
e
Oh, I see, you use disable-output-escaping="yes". That's why Xalan doesn't
escape 237 into í when outputting.
Why do you need it anyway?
In any case, output is right though.
thanks
-Original Message-
From: Voytenko, Dimitry [mailto:[EMAIL PROTECTED]]
Sent: Saturday,
: Saturday, November 30, 2002 19:45
To: [EMAIL PROTECTED]
Subject: RE: value-of with disable-output-escaping="yes"
Right.
and the stylesheet includes:
which is a big list that defines every html entity plus a few, and which
normally works fine.
Reply-To: [EMAIL PROTECTED]
>
>Hi
ng it.
Thanks,
Dmitry
-Original Message-
From: Foxy Shadis [mailto:[EMAIL PROTECTED]]
Sent: Saturday, November 30, 2002 18:55
To: [EMAIL PROTECTED]
Subject: xsl:value-of with disable-output-escaping="yes"
results in
Kiernan, CaitlAn R. (including a strange unicode problem)
rath
ue-of with disable-output-escaping="yes"
results in
Kiernan, CaitlAn R. (including a strange unicode problem)
rather than
Kiernan, Caitli-n R.
with fairly recent CVS. If it takes more than this to duplicate, I'll supply
all.
Foxy
Swiftpaw Foxyshadis, wildlife artist
[EMA
results in
Kiernan, CaitlÃn R. (including a strange unicode problem)
rather than
Kiernan, Caitlín R.
with fairly recent CVS. If it takes more than this to duplicate, I'll supply
all.
Foxy
Swiftpaw Foxyshadis, wildlife artist
[EMAIL PROTECTED] | http://foxyshadis.slightlydark.com/
_
This is strange
in latest XSLTC
the line &
with html output method
gives: &
and the line &
with html output method
gives: &
while in Xalan the first line
gives: &
and the second
gives: &
A bug?
with best wishes
Alexander Kachanov
Please
ignore my earlier email -- it was not a Xalan problem.
Thanks,
Cory
-Original Message-From: Cory Isaacson (Compuflex)
[mailto:[EMAIL PROTECTED]]Sent: Thursday, January 10, 2002
4:52 PMTo: xalan-dev@xml. apache. orgSubject: Disable
Output Escaping
I have source
I have source XML
which contains JavaScript, with single quotes, such as:
I need to output it
with the single quotes in tact, but they always come out as:
'
I tried
disable-output-escaping, on the xsl:value-of tag, and this doesn't seem to do
anything.
Any he
: org.apache.xalan.xsltc
! AssignedTo: [EMAIL PROTECTED]
! ReportedBy: [EMAIL PROTECTED]
! URL:
! Cc:
! Summary: xsl:text and disable-output-escaping, output wrong in case of html
!
[from SunMicrosystem's bug 4418047]
Given a simple xml input
XalanJ inserts these PIs for use by its own serializers that know how to
interpret them. What are you using to serialize your output?
Gary
Daniel Rubio wrote:
>
> BUG in disable-output-escaping.
>
> I am trying the follwing construct which is part of the XSLT recommendation (se
BUG in disable-output-escaping.
I am trying the follwing construct which is part of the XSLT recommendation (section
16.4) ,
it appers its not implemented in Xalan 2.2 D6
<
and in the transformation it appears as:
<
the XSLT spec (section 16.4) says a "<" should app
:
! Severity: Normal
! Priority: Medium
! Component: Xalan
! AssignedTo: [EMAIL PROTECTED]
! ReportedBy: [EMAIL PROTECTED]
! URL:
! Cc:
! Summary: disable-output-escaping generates
in output.
!
This xsl file generates different output when using
38 matches
Mail list logo
