On vie, 2010-09-10 at 21:32 +0200, Fred Kiefer wrote: > The current way how we test whether a cairo (or rather fontconfig) font > supports a character is horribly broken. As is the whole way we deal > with characters and glyphs in that backend. The result is that > characters get reported back as being supported by a font although they > aren't. That way the font replacement code that is already in gui wont > kick in here. > The simplest way to work around this is to use fonts that actually > supply all the characters you might use. An even better way to fix this > is to rewrite the glyph handling of the GNUstep cairo backend to move > away from the cairo toy font implementation. > > Fred
Well, the fonts I'm using have those characters. I can write without problem on OpenOffice with these. But I noticed that if I copy and paste these characters from OpenOffice to Ink, I can see these perfectly. Then the problem is on the input from keyboard to get those characters. Or I think so. _______________________________________________ Discuss-gnustep mailing list Discuss-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnustep
