On Tue, 28 Oct 2014 11:11:03 -0300 dequis <d...@dxzone.com.ar> wrote:
> In practice, this only makes things worse by not displaying characters > that are perfectly supported by fontconfig and xft, but not by libc. > But... whatever. It's your own fault when you use the broken glibc. File a bug-report and wait for them to fix it. Displaying the INVALID-character is imho the best compromise. The graphics don't glitch out and we don't blindly assume something. As soon as glibc gets its shit together, it will work. Strict error-checking and blindly accepting return values and not interpreting them in some weird context is often the best way to go. Don't think about it, just catch it well. Cheers FRIGN -- FRIGN <d...@frign.de>
