Summary: | Use of default encoding: FileReader/Writer and InputStreamReader/OutputStreamWriter | ||
---|---|---|---|
Product: | JMeter - Now in Github | Reporter: | Sebb <sebb> |
Component: | Main | Assignee: | JMeter issues mailing list <issues> |
Status: | NEW --- | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | 3.1 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Mac OS X 10.1 |
Description
Sebb
2017-03-13 18:22:43 UTC
This bug makes properties files unusable for storing data in Central and Easter European countries. For example, a property containing an "é" (U+00E9) in the user.properties file becomes "Ă©" (U+0102, U+00A9) during runtime. I suspect it's also because the file is read from an InputStreamReader, instead of a Reader with UTF-8 encoding. The main problem is that, on the other hand, when reading properties from the .jmx file, it's perfectly read in UTF-8. So I cannot convert ALL of my properties from UTF-8-read-as-Latin-1 to real UTF-8, because I don't know where has a property come from. That means I'm stuck with either using a .properties file or the .jmx. I copied the wrong string, the actual one is "é" (U+00C3, U+00A9). .properties files should be guarded with the tool native2ascii from the jre. That should fix your encoding problems. It would still be a good idea to document the used encodings for the in- and output paths. This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/4329 |