+1 to UTF-8 as the default encoding. (Even, if we had another default in the past.)
And +10 to rewriting the XML stuff to use a proper XML generation tool, for example java.xml.transform. (This has always been one of the worst aspects in the Rat code base.) Jochen On Thu, Jan 4, 2018 at 10:57 PM, Philipp Ottlinger (JIRA) <j...@apache.org> wrote: > > [ > https://issues.apache.org/jira/browse/RAT-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312090#comment-16312090 > ] > > Philipp Ottlinger commented on RAT-242: > --------------------------------------- > > Pull request concerning the same problem: > https://github.com/apache/creadur-rat/pull/8 > >> Encoding of XML report >> ---------------------- >> >> Key: RAT-242 >> URL: https://issues.apache.org/jira/browse/RAT-242 >> Project: Apache Rat >> Issue Type: Bug >> Components: reports >> Affects Versions: 0.12 >> Environment: ubuntu >> Reporter: Eric Barboni >> >> Hi, we encounter an issue with encoding of a xml rat report. >> We try to parse an xml rat report generated on an iso-8859-1 file system. >> The xml has no encoding element in the prolog. If you open it with >> fileinpustream it may fail. >> last comment in this pull request >> (https://github.com/apache/incubator-netbeans/pull/70) by Matthias Bläsing >> suggest forcing to UTF-8. >> encoding may also be an option in the report task >> Regards > > > > -- > This message was sent by Atlassian JIRA > (v6.4.14#64029)
