Re: [PATCH] if compiling with xft, hardcode encoding to utf-8
"Bernhard R. Link" <[email protected]>
| Newsgroups | gmane.comp.window-managers.ratpoison.devel |
|---|---|
| Message-ID | <[email protected]> |
* Jérémie Courrèges-Anglas <[email protected]> [120630 18:39]: > > 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? without Xft fonts, UTF-8 works correctly. With Xft one has to use a single-character encoding or use utf8. do you know any way to know in which case libX11 currently is so one can call the correct Xft function? Bernhard R. Link