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

Hi.

"Bernhard R. Link" <[email protected]> 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

_______________________________________________
Ratpoison-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/ratpoison-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (OpenBSD)

iQIcBAEBCgAGBQJP7yvAAAoJEGGRj78GoRSUEs8P/2EtpKrYzbnxsnNxxk+mdmY8
k9+9rzxla/LzPctBmaTtI3BlYV5ilrwGsFSy7cZ00gRXeeH8d97O2wMnXtIVirWh
xlUjOkzJHqNpVjcUKfG0aLn+PVFl2xkBeWqJqsYqNdqst/mySTxYKvvFfsEP790J
XKpgUqolM4TZTuxJP1lEk99dBAIv9oK/bOZmrnTnSnOrkyBVWN/9sNmGcTxjNkse
hQJWLxP+Y+38XvU1BilmZR9E9T2hGwTLIqcZlnnq5ide8UFLimYEEE4qwcz0JTN5
fm+wnGqiDmk2g8gLqPvDSls7KWxtsPldr/CoYxUoWGuhPLp1rn52222zZNfX4V9Q
2FLlg6wS9KpF9+DKG64Zhn+7Nb+5CKcnQOnS3aRqyH6/csjL67MsmvmM5gVK00q6
SQc/p4JiH0rmfUB21Di1gSLfbDnCN4nQGvT0GnXsy6AeAbqcn7WLduExhhCxErts
5+jnZpXgJ7bswTvBQZUTdv9/Pdo+QuztnUqdlm1pAeYyaucbpGbIhuYx0dV3/pLp
lEZH63OboolA0QY5GyNWF7HMJ20vJZQ+BHQ0NpiNQbJl65FtdOymRiwiJi29lHiA
EcebIRuCPUUk9pgt1Hj0chE85Hn4T90qplcA3YPaliefbrg0fidekXPXjfMkP/v4
y3RPwLFqtsubAsO8cIFJ
=flpy
-----END PGP SIGNATURE-----