creadur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jochen Wiedmann <>
Subject Re: RAT-190 - default encoding UTF-8 / patch / what should be implemented?
Date Thu, 19 Feb 2015 10:30:39 GMT
My personal believe is, that a default doesn't make sense at all.
Whatever you choose, you'll find people that cannot use it. For
example, in the case of UTF-8, I am quite certain that it will be
wrong for western europeans, like you and me.

The only change, that I'd be in favour of would be to enforce an
explicit encoding. Or, in other words, throw an exception, if an
encoding (aka charset) isn't explicitly choosen.


On Tue, Feb 17, 2015 at 11:59 PM, P. Ottlinger <> wrote:
> Hi *,
> after finalizing the analysis on
> it seems that RAT is not explicit enough when it comes to encoding.
> If mvn is configured to run with a non UTF-8 encoding there will be
> problems when matching UTF-8 content with licenses.
> I've browsed over some of the code parts and added some "UTF-8" to make
> it more explicit that UTF-8 should be the default. What do you think of
> that proposal?
> 1) Is it sufficient enough?
> 2a) Should we have a RAT configuration option to allow specific setting
> of encodings? With UTF-8 as default if not configured/set otherwise.
> 2) Should we just use UTF-8 as default (hardcoded) and do not give the
> user a chance to set the encoding to use.
> Since we seem to run with UTF-8 encoding in Jenkins we did not see these
> problems before. Does anyone have a good idea on how to test this?
> A UTF-8 encoded file should be analysed with mvn -Dfile.encoding!=UTF-8?
> Cheers & thanks for any opinions :-)
> Phil

Any world that can produce the Taj Mahal, William Shakespeare,
and Stripe toothpaste can't be all bad. (C.R. MacNamara, One Two Three)

View raw message