This change fixes a text rendering issue in the X11/Xft path where xmobar was UTF-8 encoding strings again before drawing them. The implementation now passes the character data through directly instead of calling UTF8.encode, which avoids double-encoding and better matches the expectation that upstream data is already in the right form. In practice, this should prevent garbled text for affected inputs and make rendering behavior more predictable.