You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by "Graeme Rocher (JIRA)" <xa...@xml.apache.org> on 2005/03/22 17:08:21 UTC

[jira] Created: (XALANJ-2084) ISO-8859-1 Encoding exception processing stylesheet

ISO-8859-1 Encoding exception processing stylesheet
---------------------------------------------------

         Key: XALANJ-2084
         URL: http://issues.apache.org/jira/browse/XALANJ-2084
     Project: XalanJ2
        Type: Bug
  Components: transformation  
    Versions: 2.6    
 Environment: jdk 1.5, windows xp sp2
    Reporter: Graeme Rocher
    Priority: Critical


I am getting the following exception when attempting to process an XML file with Xalan 2.6 called from Ant. I have tested this outside Ant using jEdits XSLT transformation engine and it produces the same result:

     [xslt] Loading stylesheet C:\projects\aclient\build\work\templates\stylesheets\main.xsl
     [xslt] : Fatal Error! org.xml.sax.SAXException: Attempt to output character of integral value 8230 that is not represented in specified output encoding of ISO-8859-1. Cause: org.xml.sax.SAXExcept
ion: Attempt to output character of integral value 8230 that is not represented in specified output encoding of ISO-8859-1.
     [xslt] Failed to process C:\projects\aclient\src\content\page.xml

This seems similar to a problem reported in bug 1799 (http://issues.apache.org/jira/browse/XALANJ-1799) although in this case upgrading to 2.6 solved the problem and I am already running 2.6.

Character 8230 of the ISO-8859-1 character set is the elipse (...), so why the error is being thrown is beyond me

I downgraded to Xalan 2.5.3 and this solved the problem, but thought I would raise awareness of this issue regardless.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org


[jira] Commented: (XALANJ-2084) ISO-8859-1 Encoding exception processing stylesheet

Posted by "Graeme Rocher (JIRA)" <xa...@xml.apache.org>.
    [ http://issues.apache.org/jira/browse/XALANJ-2084?page=comments#action_12313026 ] 

Graeme Rocher commented on XALANJ-2084:
---------------------------------------

Brian,

I wasn't able to reproduce the exact environment that was causing the error, as my codebase has moved on since I first reported this error.

However, I did try it with a test XML document and a test stylesheet through the jEdit XSLT plugin (which was causing the same problem) and it does appear to be resolved.

Regards,
Graeme

> ISO-8859-1 Encoding exception processing stylesheet
> ---------------------------------------------------
>
>          Key: XALANJ-2084
>          URL: http://issues.apache.org/jira/browse/XALANJ-2084
>      Project: XalanJ2
>         Type: Bug
>   Components: transformation
>     Versions: 2.6
>  Environment: jdk 1.5, windows xp sp2
>     Reporter: Graeme Rocher
>     Assignee: Brian Minchau
>     Priority: Critical

>
> I am getting the following exception when attempting to process an XML file with Xalan 2.6 called from Ant. I have tested this outside Ant using jEdits XSLT transformation engine and it produces the same result:
>      [xslt] Loading stylesheet C:\projects\aclient\build\work\templates\stylesheets\main.xsl
>      [xslt] : Fatal Error! org.xml.sax.SAXException: Attempt to output character of integral value 8230 that is not represented in specified output encoding of ISO-8859-1. Cause: org.xml.sax.SAXExcept
> ion: Attempt to output character of integral value 8230 that is not represented in specified output encoding of ISO-8859-1.
>      [xslt] Failed to process C:\projects\aclient\src\content\page.xml
> This seems similar to a problem reported in bug 1799 (http://issues.apache.org/jira/browse/XALANJ-1799) although in this case upgrading to 2.6 solved the problem and I am already running 2.6.
> Character 8230 of the ISO-8859-1 character set is the elipse (...), so why the error is being thrown is beyond me
> I downgraded to Xalan 2.5.3 and this solved the problem, but thought I would raise awareness of this issue regardless.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org


[jira] Updated: (XALANJ-2084) ISO-8859-1 Encoding exception processing stylesheet

Posted by "Brian Minchau (JIRA)" <xa...@xml.apache.org>.
     [ http://issues.apache.org/jira/browse/XALANJ-2084?page=all ]

Brian Minchau updated XALANJ-2084:
----------------------------------

    Fix Version: 2.7

> ISO-8859-1 Encoding exception processing stylesheet
> ---------------------------------------------------
>
>          Key: XALANJ-2084
>          URL: http://issues.apache.org/jira/browse/XALANJ-2084
>      Project: XalanJ2
>         Type: Bug
>   Components: transformation
>     Versions: 2.6
>  Environment: jdk 1.5, windows xp sp2
>     Reporter: Graeme Rocher
>     Assignee: Brian Minchau
>     Priority: Critical
>      Fix For: 2.7

>
> I am getting the following exception when attempting to process an XML file with Xalan 2.6 called from Ant. I have tested this outside Ant using jEdits XSLT transformation engine and it produces the same result:
>      [xslt] Loading stylesheet C:\projects\aclient\build\work\templates\stylesheets\main.xsl
>      [xslt] : Fatal Error! org.xml.sax.SAXException: Attempt to output character of integral value 8230 that is not represented in specified output encoding of ISO-8859-1. Cause: org.xml.sax.SAXExcept
> ion: Attempt to output character of integral value 8230 that is not represented in specified output encoding of ISO-8859-1.
>      [xslt] Failed to process C:\projects\aclient\src\content\page.xml
> This seems similar to a problem reported in bug 1799 (http://issues.apache.org/jira/browse/XALANJ-1799) although in this case upgrading to 2.6 solved the problem and I am already running 2.6.
> Character 8230 of the ISO-8859-1 character set is the elipse (...), so why the error is being thrown is beyond me
> I downgraded to Xalan 2.5.3 and this solved the problem, but thought I would raise awareness of this issue regardless.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org


[jira] Commented: (XALANJ-2084) ISO-8859-1 Encoding exception processing stylesheet

Posted by "Brian Minchau (JIRA)" <xa...@xml.apache.org>.
     [ http://issues.apache.org/jira/browse/XALANJ-2084?page=comments#action_61968 ]
     
Brian Minchau commented on XALANJ-2084:
---------------------------------------

Current behavior is a rather serious exception when the character being written out by the serializer is not a valid charcter in the stated output encoding.

Should Xalan be kinder and gentler and produce output, though perhaps wrong output, and just give a warning?  

The serialized output might have this xml header:
<?xml encoding="ISO-8859-1"?>
but yet it would break that promise and contain characters not in that encoding.

I'm thinking about this in a web server environment. Such a warning might be produced multiple times per transformation, and such warnings could really pile up in the servers log. On the other hand, the exceptions probably pile up in the log as-is.

Anyone have an opinion on reducing to a warning?


> ISO-8859-1 Encoding exception processing stylesheet
> ---------------------------------------------------
>
>          Key: XALANJ-2084
>          URL: http://issues.apache.org/jira/browse/XALANJ-2084
>      Project: XalanJ2
>         Type: Bug
>   Components: transformation
>     Versions: 2.6
>  Environment: jdk 1.5, windows xp sp2
>     Reporter: Graeme Rocher
>     Priority: Critical

>
> I am getting the following exception when attempting to process an XML file with Xalan 2.6 called from Ant. I have tested this outside Ant using jEdits XSLT transformation engine and it produces the same result:
>      [xslt] Loading stylesheet C:\projects\aclient\build\work\templates\stylesheets\main.xsl
>      [xslt] : Fatal Error! org.xml.sax.SAXException: Attempt to output character of integral value 8230 that is not represented in specified output encoding of ISO-8859-1. Cause: org.xml.sax.SAXExcept
> ion: Attempt to output character of integral value 8230 that is not represented in specified output encoding of ISO-8859-1.
>      [xslt] Failed to process C:\projects\aclient\src\content\page.xml
> This seems similar to a problem reported in bug 1799 (http://issues.apache.org/jira/browse/XALANJ-1799) although in this case upgrading to 2.6 solved the problem and I am already running 2.6.
> Character 8230 of the ISO-8859-1 character set is the elipse (...), so why the error is being thrown is beyond me
> I downgraded to Xalan 2.5.3 and this solved the problem, but thought I would raise awareness of this issue regardless.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org


[jira] Commented: (XALANJ-2084) ISO-8859-1 Encoding exception processing stylesheet

Posted by "Brian Minchau (JIRA)" <xa...@xml.apache.org>.
     [ http://issues.apache.org/jira/browse/XALANJ-2084?page=comments#action_62397 ]
     
Brian Minchau commented on XALANJ-2084:
---------------------------------------

I've given this a bit more thought, and the old behavior from a long time ago was to simply produce the wrong output (characters output that are not in the specified encoding), with no error.

Newer code gives an error, but perhaps too strong of an error. I'm thinking that we should produce the incorrect output, but with a warning.

Henry Zongaro sent this to me, pointing out some additional problems in this area:
<<<
It's interesting to note that there's absolutely no warning or exception produced for the following analogous stylesheet, just pure garbage output.  If you're going to soften the error for the text output method to a warning, I think you should follow the same philosophy for the following test by introducing appropriate warnings.


<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
  <xsl:output method="xml" encoding="US-ASCII"/>

  <xsl:template match="/">
    <xsl:element name="&#xc2;">
      <xsl:text>&#xc2;</xsl:text>
      <xsl:comment>&#xc2;</xsl:comment>
    </xsl:element>
  </xsl:template>
</xsl:stylesheet>

Thanks,

Henry


>>>

It is OK for the text node above to have the &#xc2; output as a character reference, but such character references should not be in comments or element names.



> ISO-8859-1 Encoding exception processing stylesheet
> ---------------------------------------------------
>
>          Key: XALANJ-2084
>          URL: http://issues.apache.org/jira/browse/XALANJ-2084
>      Project: XalanJ2
>         Type: Bug
>   Components: transformation
>     Versions: 2.6
>  Environment: jdk 1.5, windows xp sp2
>     Reporter: Graeme Rocher
>     Priority: Critical

>
> I am getting the following exception when attempting to process an XML file with Xalan 2.6 called from Ant. I have tested this outside Ant using jEdits XSLT transformation engine and it produces the same result:
>      [xslt] Loading stylesheet C:\projects\aclient\build\work\templates\stylesheets\main.xsl
>      [xslt] : Fatal Error! org.xml.sax.SAXException: Attempt to output character of integral value 8230 that is not represented in specified output encoding of ISO-8859-1. Cause: org.xml.sax.SAXExcept
> ion: Attempt to output character of integral value 8230 that is not represented in specified output encoding of ISO-8859-1.
>      [xslt] Failed to process C:\projects\aclient\src\content\page.xml
> This seems similar to a problem reported in bug 1799 (http://issues.apache.org/jira/browse/XALANJ-1799) although in this case upgrading to 2.6 solved the problem and I am already running 2.6.
> Character 8230 of the ISO-8859-1 character set is the elipse (...), so why the error is being thrown is beyond me
> I downgraded to Xalan 2.5.3 and this solved the problem, but thought I would raise awareness of this issue regardless.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org


[jira] Commented: (XALANJ-2084) ISO-8859-1 Encoding exception processing stylesheet

Posted by "Brian Minchau (JIRA)" <xa...@xml.apache.org>.
     [ http://issues.apache.org/jira/browse/XALANJ-2084?page=comments#action_62336 ]
     
Brian Minchau commented on XALANJ-2084:
---------------------------------------

I've looked at how and when this error message is created. From inspection of the source code of Xalan, it can only be created for text output (not xml or html). So I suspect that your stylesheet specifies <xsl:output method="text" .../>.

I produced the error message with this stylesheet:
--------------------------------------------------
<?xml version="1.0" encoding="ISO-8859-9"?>
<xsl:stylesheet version="1.0"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="text" encoding="ISO-8859-1" />
<xsl:template match="/">
<out>&#8230;</out>
</xsl:template>
</xsl:stylesheet>
--------------------------------------------------

However the XSLT 1.0 recommendation (http://www.w3.org/TR/xslt) says this in section 16.3 about text output:
<<
If the result tree contains a character that cannot be represented in the encoding that the XSLT processor is using for output, the XSLT processor should signal an error.
>>

The section quoted by Joanne T. was from section 16.1 on xml output. Section 16.2 on html output is similar to the xml section.  However I think your output method is text, and that we have the correct behavior according to the XSLT 1.0 recommendation.


> ISO-8859-1 Encoding exception processing stylesheet
> ---------------------------------------------------
>
>          Key: XALANJ-2084
>          URL: http://issues.apache.org/jira/browse/XALANJ-2084
>      Project: XalanJ2
>         Type: Bug
>   Components: transformation
>     Versions: 2.6
>  Environment: jdk 1.5, windows xp sp2
>     Reporter: Graeme Rocher
>     Priority: Critical

>
> I am getting the following exception when attempting to process an XML file with Xalan 2.6 called from Ant. I have tested this outside Ant using jEdits XSLT transformation engine and it produces the same result:
>      [xslt] Loading stylesheet C:\projects\aclient\build\work\templates\stylesheets\main.xsl
>      [xslt] : Fatal Error! org.xml.sax.SAXException: Attempt to output character of integral value 8230 that is not represented in specified output encoding of ISO-8859-1. Cause: org.xml.sax.SAXExcept
> ion: Attempt to output character of integral value 8230 that is not represented in specified output encoding of ISO-8859-1.
>      [xslt] Failed to process C:\projects\aclient\src\content\page.xml
> This seems similar to a problem reported in bug 1799 (http://issues.apache.org/jira/browse/XALANJ-1799) although in this case upgrading to 2.6 solved the problem and I am already running 2.6.
> Character 8230 of the ISO-8859-1 character set is the elipse (...), so why the error is being thrown is beyond me
> I downgraded to Xalan 2.5.3 and this solved the problem, but thought I would raise awareness of this issue regardless.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org


[jira] Commented: (XALANJ-2084) ISO-8859-1 Encoding exception processing stylesheet

Posted by "Brian Minchau (JIRA)" <xa...@xml.apache.org>.
     [ http://issues.apache.org/jira/browse/XALANJ-2084?page=comments#action_62238 ]
     
Brian Minchau commented on XALANJ-2084:
---------------------------------------

Joanne Tong sent me this note:
<<
Just wanted to point this out from the XSLT 1.0 spec:

"It is possible that the result tree will contain a character that cannot be represented in the encoding that the XSLT processor is using for output. In this case, if the character occurs in a context where XML recognizes character references (i.e. in the value of an attribute node or text node), then the character should be output as a character reference; otherwise (for example if the character occurs in the name of an element) the XSLT processor should signal an error."

>>


> ISO-8859-1 Encoding exception processing stylesheet
> ---------------------------------------------------
>
>          Key: XALANJ-2084
>          URL: http://issues.apache.org/jira/browse/XALANJ-2084
>      Project: XalanJ2
>         Type: Bug
>   Components: transformation
>     Versions: 2.6
>  Environment: jdk 1.5, windows xp sp2
>     Reporter: Graeme Rocher
>     Priority: Critical

>
> I am getting the following exception when attempting to process an XML file with Xalan 2.6 called from Ant. I have tested this outside Ant using jEdits XSLT transformation engine and it produces the same result:
>      [xslt] Loading stylesheet C:\projects\aclient\build\work\templates\stylesheets\main.xsl
>      [xslt] : Fatal Error! org.xml.sax.SAXException: Attempt to output character of integral value 8230 that is not represented in specified output encoding of ISO-8859-1. Cause: org.xml.sax.SAXExcept
> ion: Attempt to output character of integral value 8230 that is not represented in specified output encoding of ISO-8859-1.
>      [xslt] Failed to process C:\projects\aclient\src\content\page.xml
> This seems similar to a problem reported in bug 1799 (http://issues.apache.org/jira/browse/XALANJ-1799) although in this case upgrading to 2.6 solved the problem and I am already running 2.6.
> Character 8230 of the ISO-8859-1 character set is the elipse (...), so why the error is being thrown is beyond me
> I downgraded to Xalan 2.5.3 and this solved the problem, but thought I would raise awareness of this issue regardless.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org


[jira] Resolved: (XALANJ-2084) ISO-8859-1 Encoding exception processing stylesheet

Posted by "Brian Minchau (JIRA)" <xa...@xml.apache.org>.
     [ http://issues.apache.org/jira/browse/XALANJ-2084?page=all ]
     
Brian Minchau resolved XALANJ-2084:
-----------------------------------

    Resolution: Duplicate

Graeme,
I'm resolving this issue as a duplicate of XALANJ-2087.
I put a patch in XALANJ-2087 that should get correct character encoding information now.  Please verify that
it works for you. Thanks.


> ISO-8859-1 Encoding exception processing stylesheet
> ---------------------------------------------------
>
>          Key: XALANJ-2084
>          URL: http://issues.apache.org/jira/browse/XALANJ-2084
>      Project: XalanJ2
>         Type: Bug
>   Components: transformation
>     Versions: 2.6
>  Environment: jdk 1.5, windows xp sp2
>     Reporter: Graeme Rocher
>     Assignee: Brian Minchau
>     Priority: Critical

>
> I am getting the following exception when attempting to process an XML file with Xalan 2.6 called from Ant. I have tested this outside Ant using jEdits XSLT transformation engine and it produces the same result:
>      [xslt] Loading stylesheet C:\projects\aclient\build\work\templates\stylesheets\main.xsl
>      [xslt] : Fatal Error! org.xml.sax.SAXException: Attempt to output character of integral value 8230 that is not represented in specified output encoding of ISO-8859-1. Cause: org.xml.sax.SAXExcept
> ion: Attempt to output character of integral value 8230 that is not represented in specified output encoding of ISO-8859-1.
>      [xslt] Failed to process C:\projects\aclient\src\content\page.xml
> This seems similar to a problem reported in bug 1799 (http://issues.apache.org/jira/browse/XALANJ-1799) although in this case upgrading to 2.6 solved the problem and I am already running 2.6.
> Character 8230 of the ISO-8859-1 character set is the elipse (...), so why the error is being thrown is beyond me
> I downgraded to Xalan 2.5.3 and this solved the problem, but thought I would raise awareness of this issue regardless.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org


[jira] Commented: (XALANJ-2084) ISO-8859-1 Encoding exception processing stylesheet

Posted by "Brian Minchau (JIRA)" <xa...@xml.apache.org>.
     [ http://issues.apache.org/jira/browse/XALANJ-2084?page=comments#action_62276 ]
     
Brian Minchau commented on XALANJ-2084:
---------------------------------------

Given Joanne's comment, once fixed, the new behavior will be to output characters that are not in the output encoding as character references, with no error or warning where possible, e.g. in text nodes. 

An error will only be given where this is not possible, e.g. in element names.

> ISO-8859-1 Encoding exception processing stylesheet
> ---------------------------------------------------
>
>          Key: XALANJ-2084
>          URL: http://issues.apache.org/jira/browse/XALANJ-2084
>      Project: XalanJ2
>         Type: Bug
>   Components: transformation
>     Versions: 2.6
>  Environment: jdk 1.5, windows xp sp2
>     Reporter: Graeme Rocher
>     Priority: Critical

>
> I am getting the following exception when attempting to process an XML file with Xalan 2.6 called from Ant. I have tested this outside Ant using jEdits XSLT transformation engine and it produces the same result:
>      [xslt] Loading stylesheet C:\projects\aclient\build\work\templates\stylesheets\main.xsl
>      [xslt] : Fatal Error! org.xml.sax.SAXException: Attempt to output character of integral value 8230 that is not represented in specified output encoding of ISO-8859-1. Cause: org.xml.sax.SAXExcept
> ion: Attempt to output character of integral value 8230 that is not represented in specified output encoding of ISO-8859-1.
>      [xslt] Failed to process C:\projects\aclient\src\content\page.xml
> This seems similar to a problem reported in bug 1799 (http://issues.apache.org/jira/browse/XALANJ-1799) although in this case upgrading to 2.6 solved the problem and I am already running 2.6.
> Character 8230 of the ISO-8859-1 character set is the elipse (...), so why the error is being thrown is beyond me
> I downgraded to Xalan 2.5.3 and this solved the problem, but thought I would raise awareness of this issue regardless.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org


[jira] Commented: (XALANJ-2084) ISO-8859-1 Encoding exception processing stylesheet

Posted by "Brian Minchau (JIRA)" <xa...@xml.apache.org>.
     [ http://issues.apache.org/jira/browse/XALANJ-2084?page=comments#action_62215 ]
     
Brian Minchau commented on XALANJ-2084:
---------------------------------------

Xalan JIRA meeting April 5, 2005 agreed that we should give a warning, not through an exception.

Xalan would then send characters to the serializer document that were not in the specified encoding.

> ISO-8859-1 Encoding exception processing stylesheet
> ---------------------------------------------------
>
>          Key: XALANJ-2084
>          URL: http://issues.apache.org/jira/browse/XALANJ-2084
>      Project: XalanJ2
>         Type: Bug
>   Components: transformation
>     Versions: 2.6
>  Environment: jdk 1.5, windows xp sp2
>     Reporter: Graeme Rocher
>     Priority: Critical

>
> I am getting the following exception when attempting to process an XML file with Xalan 2.6 called from Ant. I have tested this outside Ant using jEdits XSLT transformation engine and it produces the same result:
>      [xslt] Loading stylesheet C:\projects\aclient\build\work\templates\stylesheets\main.xsl
>      [xslt] : Fatal Error! org.xml.sax.SAXException: Attempt to output character of integral value 8230 that is not represented in specified output encoding of ISO-8859-1. Cause: org.xml.sax.SAXExcept
> ion: Attempt to output character of integral value 8230 that is not represented in specified output encoding of ISO-8859-1.
>      [xslt] Failed to process C:\projects\aclient\src\content\page.xml
> This seems similar to a problem reported in bug 1799 (http://issues.apache.org/jira/browse/XALANJ-1799) although in this case upgrading to 2.6 solved the problem and I am already running 2.6.
> Character 8230 of the ISO-8859-1 character set is the elipse (...), so why the error is being thrown is beyond me
> I downgraded to Xalan 2.5.3 and this solved the problem, but thought I would raise awareness of this issue regardless.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org


[jira] Commented: (XALANJ-2084) ISO-8859-1 Encoding exception processing stylesheet

Posted by "David Bertoni (JIRA)" <xa...@xml.apache.org>.
     [ http://issues.apache.org/jira/browse/XALANJ-2084?page=comments#action_61381 ]
     
David Bertoni commented on XALANJ-2084:
---------------------------------------

Decimal 8230, AKA hexadecimal 2026, AKA the Unicode code point U+2026 (HORIZONTAL ELLIPSIS) is _not_ representable in ISO-8859-1.

Is your stylesheet using the text output method?  If so, Xalan-J is probably using that encoding by default.  It would be helpful if you could attach a small set of inputs that reproduces the error message.

> ISO-8859-1 Encoding exception processing stylesheet
> ---------------------------------------------------
>
>          Key: XALANJ-2084
>          URL: http://issues.apache.org/jira/browse/XALANJ-2084
>      Project: XalanJ2
>         Type: Bug
>   Components: transformation
>     Versions: 2.6
>  Environment: jdk 1.5, windows xp sp2
>     Reporter: Graeme Rocher
>     Priority: Critical

>
> I am getting the following exception when attempting to process an XML file with Xalan 2.6 called from Ant. I have tested this outside Ant using jEdits XSLT transformation engine and it produces the same result:
>      [xslt] Loading stylesheet C:\projects\aclient\build\work\templates\stylesheets\main.xsl
>      [xslt] : Fatal Error! org.xml.sax.SAXException: Attempt to output character of integral value 8230 that is not represented in specified output encoding of ISO-8859-1. Cause: org.xml.sax.SAXExcept
> ion: Attempt to output character of integral value 8230 that is not represented in specified output encoding of ISO-8859-1.
>      [xslt] Failed to process C:\projects\aclient\src\content\page.xml
> This seems similar to a problem reported in bug 1799 (http://issues.apache.org/jira/browse/XALANJ-1799) although in this case upgrading to 2.6 solved the problem and I am already running 2.6.
> Character 8230 of the ISO-8859-1 character set is the elipse (...), so why the error is being thrown is beyond me
> I downgraded to Xalan 2.5.3 and this solved the problem, but thought I would raise awareness of this issue regardless.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org


[jira] Assigned: (XALANJ-2084) ISO-8859-1 Encoding exception processing stylesheet

Posted by "Brian Minchau (JIRA)" <xa...@xml.apache.org>.
     [ http://issues.apache.org/jira/browse/XALANJ-2084?page=all ]

Brian Minchau reassigned XALANJ-2084:
-------------------------------------

    Assign To: Brian Minchau

Per the Xalan-J JIRA meeting on April 5,
this should be a warning, not an error.

Assigning to Brian M. per the same meeting.

> ISO-8859-1 Encoding exception processing stylesheet
> ---------------------------------------------------
>
>          Key: XALANJ-2084
>          URL: http://issues.apache.org/jira/browse/XALANJ-2084
>      Project: XalanJ2
>         Type: Bug
>   Components: transformation
>     Versions: 2.6
>  Environment: jdk 1.5, windows xp sp2
>     Reporter: Graeme Rocher
>     Assignee: Brian Minchau
>     Priority: Critical

>
> I am getting the following exception when attempting to process an XML file with Xalan 2.6 called from Ant. I have tested this outside Ant using jEdits XSLT transformation engine and it produces the same result:
>      [xslt] Loading stylesheet C:\projects\aclient\build\work\templates\stylesheets\main.xsl
>      [xslt] : Fatal Error! org.xml.sax.SAXException: Attempt to output character of integral value 8230 that is not represented in specified output encoding of ISO-8859-1. Cause: org.xml.sax.SAXExcept
> ion: Attempt to output character of integral value 8230 that is not represented in specified output encoding of ISO-8859-1.
>      [xslt] Failed to process C:\projects\aclient\src\content\page.xml
> This seems similar to a problem reported in bug 1799 (http://issues.apache.org/jira/browse/XALANJ-1799) although in this case upgrading to 2.6 solved the problem and I am already running 2.6.
> Character 8230 of the ISO-8859-1 character set is the elipse (...), so why the error is being thrown is beyond me
> I downgraded to Xalan 2.5.3 and this solved the problem, but thought I would raise awareness of this issue regardless.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org