#79 Configuration files interpreted w.r.t. default encoding

closed-fixed
nobody
Harness (16)
3
2012-09-11
2010-07-23
Andreas Sewe
No

The configuration files (.cnf) are currently interpreted w.r.t. to the platform's default encoding (file.encoding); consequently, the following fails:

> java -Dfile.encoding=UTF-16 -jar 9.12-bach/dacapo-9.12-bach.jar fop

Fortunately, this is a problem easy to solve: Decide on a encoding for configuration files (IMHO, UTF-8 would be best) and use the ConfigFile(InputStream, String) constructor instead of its one-argument counterpart.

Discussion

  • Andreas Sewe
    Andreas Sewe
    2012-06-19

    A fix for this issue is available on Bitbucket: https://bitbucket.org/sewe/dacapobench/changeset/50a24878300a

    Note that the suggested fix also enables Unicode in .cnf files. Personally, I consider this to be quite useful; a benchmark program's copyright notice can easily contain umlauts, for example.

     
  • Andreas Sewe
    Andreas Sewe
    2012-09-11

    • priority: 5 --> 3
    • status: open --> closed-fixed
     
  • Andreas Sewe
    Andreas Sewe
    2012-09-11

    Fixed in changeset 50a24878300a.