> I've looked at it and gave up. I don't know what Maven is doing here
> on the Mac. Maybe fresh eyes will have a better chance at fixing it.
>
> My experience with Maven is it works about 5% of the time, and the
> other 95% of the time you have to work around it by skipping tests,
> or by writing massive blocks of XML in your pom.xml file, or by
> redesigning your entire project directory structure and revision
> control system to use SVN instead of Git.
Ok. It's not (just) a Maven problem as I can get the same tests to
fail in Eclipse by setting the Console Encoding to MacRoman (which is
the default Charset.defaultCharset() when running a java app on OS X).
Doing some digging, just on testGetText_DiffCc :- where it fails, I
look at the output of each doing getBytes() - so will be in MacRoman -
(cols are byte no, exp before the replace, after the replace and the
result of fh.getScriptText. I get :
94 32 32,32
95 43 43,43 ++
96 116 116,116 tt
97 101 101,101 ee
98 115 115,115 ss
99 116 116,116 tt
100 32 32,32
101 -127 -127,-59 !!!!!!!!!!!!!!!!!!!!!!!!!!!! ??
102 110 110,110 nn
103 103 103,103 gg
104 115 115,115 ss
105 116 116,116 tt
106 114 114,114 rr
107 -102 -102,-10 !!!!!!!!!!!!!!!!!!!!!!!!!!!! ??
108 109 109,109 mm
109 10 10,10
-10 (F6) is ^, and -59 (C5) is some wavy lines..
However, I'm slightly confused - possibly because I don't know what
/should/ be the case. In
exp.replace("\303\205ngstr\303\266m", "\u00c5ngstr\u00f6m")
is \303\205 really meant to represent U+00C3 and U+0085 ? Shouldn't
the replace be being done on bytes rather than strings?
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
