You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@abdera.apache.org by "Adam Constabaris (JIRA)" <ji...@apache.org> on 2008/05/30 03:33:45 UTC

[jira] Created: (ABDERA-171) Set explicit encoding on OutputStreamWriter in FOMTest.testContent2

Set explicit encoding on OutputStreamWriter in FOMTest.testContent2
-------------------------------------------------------------------

                 Key: ABDERA-171
                 URL: https://issues.apache.org/jira/browse/ABDERA-171
             Project: Abdera
          Issue Type: Test
    Affects Versions: 0.4.0
         Environment: Windows XP, JDK 1.6.0_10, us_en
            Reporter: Adam Constabaris
            Priority: Trivial
             Fix For: 0.5.0


org.apache.abdera.test.parser.stax.FOMTest.testContent2 in the abdera-parser module fails on XP because it uses an OutputStreamWriter with default encoding; apparently the test content cannot be correctly encoded into CP1252 (test also fails if you specify iso-8859-1 encoding).  Presumably this does not fail on other platforms because the default encodings there (UTF-8?) can correctly encode the content.

I will attach a patch that explicitly sets the encoding on the OSW to utf-16

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (ABDERA-171) Set explicit encoding on OutputStreamWriter in FOMTest.testContent2

Posted by "Adam Constabaris (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ABDERA-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Constabaris updated ABDERA-171:
------------------------------------

    Attachment: FOMTest.patch

Patch for FOMTest.java

> Set explicit encoding on OutputStreamWriter in FOMTest.testContent2
> -------------------------------------------------------------------
>
>                 Key: ABDERA-171
>                 URL: https://issues.apache.org/jira/browse/ABDERA-171
>             Project: Abdera
>          Issue Type: Test
>    Affects Versions: 0.4.0
>         Environment: Windows XP, JDK 1.6.0_10, us_en
>            Reporter: Adam Constabaris
>            Priority: Trivial
>             Fix For: 0.5.0
>
>         Attachments: FOMTest.patch
>
>
> org.apache.abdera.test.parser.stax.FOMTest.testContent2 in the abdera-parser module fails on XP because it uses an OutputStreamWriter with default encoding; apparently the test content cannot be correctly encoded into CP1252 (test also fails if you specify iso-8859-1 encoding).  Presumably this does not fail on other platforms because the default encodings there (UTF-8?) can correctly encode the content.
> I will attach a patch that explicitly sets the encoding on the OSW to utf-16

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (ABDERA-171) Set explicit encoding on OutputStreamWriter in FOMTest.testContent2

Posted by "James M Snell (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ABDERA-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James M Snell resolved ABDERA-171.
----------------------------------

    Resolution: Fixed

checked in

> Set explicit encoding on OutputStreamWriter in FOMTest.testContent2
> -------------------------------------------------------------------
>
>                 Key: ABDERA-171
>                 URL: https://issues.apache.org/jira/browse/ABDERA-171
>             Project: Abdera
>          Issue Type: Test
>    Affects Versions: 0.4.0
>         Environment: Windows XP, JDK 1.6.0_10, us_en
>            Reporter: Adam Constabaris
>            Priority: Trivial
>             Fix For: 0.5.0
>
>         Attachments: FOMTest.patch
>
>
> org.apache.abdera.test.parser.stax.FOMTest.testContent2 in the abdera-parser module fails on XP because it uses an OutputStreamWriter with default encoding; apparently the test content cannot be correctly encoded into CP1252 (test also fails if you specify iso-8859-1 encoding).  Presumably this does not fail on other platforms because the default encodings there (UTF-8?) can correctly encode the content.
> I will attach a patch that explicitly sets the encoding on the OSW to utf-16

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.