ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gilles Scokart (JIRA)" <j...@apache.org>
Subject [jira] Updated: (IVY-816) Report encoding is incorrect
Date Thu, 29 May 2008 09:52:44 GMT

     [ https://issues.apache.org/jira/browse/IVY-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gilles Scokart updated IVY-816:
-------------------------------

    Issue Type: Bug  (was: Improvement)
       Summary: Report encoding is incorrect  (was: Report encoding should be UTF-8)

It is indeed a bug.  If the local default encoding is not ISO-Latin-1 the produced XML is
either not correct ("special characters are not correctly encoded) or even invalid.

> Report encoding is incorrect
> ----------------------------
>
>                 Key: IVY-816
>                 URL: https://issues.apache.org/jira/browse/IVY-816
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0-beta-1, 2.0.0-beta-2
>            Reporter: Jim Bonanno
>            Assignee: Gilles Scokart
>
> The xsd for ivy specifies xs:string for the values of module and organisation, so non
8859 characters are supported.
> 		            <xs:attribute name="organisation" type="xs:string" use="required"/>
> 		            <xs:attribute name="module" type="xs:string" use="required"/>
> But currently the ivy report is written with xml encoding 8859.
>         out.println("<?xml version=\"1.0\" encoding=\"ISO-8859-1\"?>");
>         out.println("<?xml-stylesheet type=\"text/xsl\" href=\"ivy-report.xsl\"?>");
> If the encoding written from XmlReportWriter was changed to UTF-8 then the report could
display dbcs characters.

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


Mime
View raw message