Save response to file and View Results XML Log - inconsistent coding and not BodySize(which is not logged in JTL XML)

**RuThaNiel van den Naar** ([Bug 63962](https://bz.apache.org/bugzilla//show_bug.cgi?id=63962&redirect=false)):
Hello,
i have problem to pair errors created by:
1) Save Response to file
2) View results

Save response to file is producing nice UTF-8 log.
View results tree is producing log in some strange coding - Notepad++ is reporting as ANSI as UTF-8, Pspad is reporting it as Unicode UTF-8 no Bom.

In log is lots of unwanted characters like:
<"> strings instead of "normal" ones in Save Response to file.

When i reopen log by View Results, there is some transformation - i no more see these characters and its same as Save Response to File log.

I tried to change:
sampleresult.default.encoding from ISO-8859-1 to UTF-8 with line:
sampleresult.default.encoding=UTF-8
But nothing changed, View results logging is still the same.

I need to pair them for my errors stats generator tool, where is trying to find same response in both file, in order to find transaction controller (lb=xx), where its failing and generate some report about in which steps errors which errors are..

I could be some workaround to to avoid to search logs for exact <responseData></responseData> content. When i open logs in view results Tree can see in Sample results view these:
Size in bytes: XXX
Body size in bytes: XX

There are exactly the same as size of my Save Response to File response in UTF.. So i would be able to pair it.. is this number would be loggend in View Results tree XML log.. unfortunately, i searched whole XML can there is no such number,
so i seems that its calculated during View Results tree logging.. In log is only Sent bytes number (sby) - which match number in Jmeter View result tree, where are some.. There is some by= parameter, but number not match with (Size in bytes / Body size in bytes),
i dunno is this reporting some other number or its bugged.

Severity: normal
OS: All