Closed GoogleCodeExporter closed 9 years ago
We may need to explicitly set the encoding to UTF-8
Original comment by willard....@gtempaccount.com
on 8 May 2011 at 1:26
I am observing the same issue on a Windows Vista machine, should I provide the
platform encoding as part of pom.xml to fix this issue?
Original comment by rajesh.k...@gmail.com
on 14 Jul 2011 at 7:26
I added the following properties for the build to use UTF-8 in the root
pom.xml, but the changes didn't make a difference though.
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<project.reporting.outputEncoding>${project.build.sourceEncoding}</project.reporting.outputEncoding>
<file.encoding>${project.build.sourceEncoding}</file.encoding>
</properties>
Original comment by rajesh.k...@gmail.com
on 14 Jul 2011 at 7:43
So I figured it out. Its a line separator issue. On windows the line separator
is \r\n, but on linux its just \n.
I'll apply a patch in the next 24 hours.
Original comment by Simon.Re...@gmail.com
on 7 Aug 2011 at 2:57
Original comment by Simon.Re...@gmail.com
on 8 Aug 2011 at 2:06
The JSON generator (Jackson) has a prettyprint option that is tested in
verifyPrettyPrinter(org.openrtb.common.json.AbstractJsonTranslatorTest)
However, by default the generator uses class
org.codehaus.jackson.impl.DefaultPrettyPrinter.Lf2SpacesIndenter
and the line separators that it generates are specific to the OS and therefore
we need to check the line separators used in order to generate the correct
PRETTY_VALUE to compare against
Original comment by Simon.Re...@gmail.com
on 8 Aug 2011 at 2:20
Works fine, with the new changes.
Original comment by rajesh.k...@gmail.com
on 8 Aug 2011 at 8:52
Original comment by Simon.Re...@gmail.com
on 8 Aug 2011 at 11:38
Original issue reported on code.google.com by
Simon.Re...@gmail.com
on 8 May 2011 at 1:20Attachments: