Comment 7 for bug 1103394

Description of problem:
history uses wrong encoding to show utf8 logs.

Version-Release number of selected component (if applicable):
since 3.6.3
empathy-3.8.1-2.fc19.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Send e.g. "Привет" ("Hello" in Russian)
2. Open Previous conversations

Actual results:
The last entry is "Привет"

Expected results:
Last entry will be "Привет"

Additional info:
I have checked that my logs in ~/.local/share/TpLogger/ are in utf8. Then I
downgrade empathy up to 3.6.2 and restart gnome-session. This is fixed my
problem. I have checked several times and can confirm that with empathy 3.6.2
the bug is not reproducible, but reproducible since 3.6.3.

The problem here is that g_strescape changed its specifications over time -
from the UTF-8-compatible "double every backslash" to ASCII-only "escape
everything except 0x20 through 0x7E". Would it be right to invent a new
backslash-doubling function for empathy-log-window.c specifically? Not pretty,
but passing a 128-character exception string to g_strescape is even less so.

This commit created this bug: https://git.gnome.org/browse/empathy/commit/?h=gnome-3-6&id=1e7449f5a14e2f031389808206c9991f65d3ade7