ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gilles Scokart (JIRA)" <>
Subject [jira] Commented: (IVY-816) Report encoding should be UTF-8
Date Tue, 27 May 2008 11:58:38 GMT


Gilles Scokart commented on IVY-816:

I think there is actually more than an improvement.  I think there is a bug there.

We are indeed writing using the default platform encoding, but saying in the xml that it is
Iso-Latin-1.  If your default encoding is for instance UTF-8 or UTF-16, the produced xml might
be invalid. (if the second byte of a character would be read in iso-latin a '<' or a '&'
for instance).

> Report encoding should be UTF-8
> -------------------------------
>                 Key: IVY-816
>                 URL:
>             Project: Ivy
>          Issue Type: Improvement
>          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.

View raw message