Re: [RP] [PATCH] if compiling with xft, hardcode encoding to utf-8

[Jérémie Courrèges -Anglas]

Hi.

"Bernhard R. Link" <address@hidden> writes:

> Unlike the X primitives, Xft does not seem to support
> utf-8 when drawing a string encoded according to the current
> locale. So if compiling with Xft, hardcode the encoding to be
> used to utf-8.

This has the undesirable effect to break existing setups.  People using
for example latin1 wouldn't be able to input and echo latin1 characters.
I'm no unicode expert, but if ratpoison has to get unicode support, then
it should probably do it correctly, right?

> ---
>  src/events.c  |    4 ++++
>  src/globals.c |   12 ++++++++----
>  src/manage.c  |    4 ++++
>  3 files changed, 16 insertions(+), 4 deletions(-)
>
>  This has the side effect of command line utilities always
>  outputting everything as utf-8 -- no matter what the locale is.
>  (But as they use the locale of the ratpoison running as WM
>  and not the one outputting the data, I guess that is not much worse).

Right, ratpoison -c 'some stuff with non-utf8 valid characters' works in
a shell, but not within the input bar.

Regards.
-- 
Jérémie Courrèges-Anglas
GPG fingerprint: 61DB D9A0 00A4 67CF 2A90 8961 6191 8FBF 06A1 1494

pgpgkYQ_0UXf0.pgp
Description: PGP signature