On Sat, Oct 06, 2012 at 05:06:45PM +0200, Christoph Lohmann wrote: > Sadly, I haven’t found a way to to overwrite the global settings in > fontconfig for just an application. So the needed antialiasing in Fire‐ > fox (The web looks ugly without!) will automatically overwrite the st > settings, where using non‐antialiasing will create more readable output > with small monospaced text. Maybe that’s a topic which will come up when > Wayland is moving things forward.
hahaha wayland anyway, you can set specific exclusions to certain fonts at certain sizes. this involves dicking around in xml. I told you so. there should be examples in your /etc/fonts/conf.avail; if not, some minor googling should help. within xft itself, this might be happening because you're using XftFontOpenPattern, which is subject to 'automagic' editing based on global xft config, which in turn is molested by freetype. you might try taking the match, appending your XFT_ANTIALIAS bool, and then using XftFontOpenName instead. Not sure if this works any more, but iirc it did the last time I was under the delusion that xft was worth using. speaking of which, the simplest way to disable antialiasing is to use real fonts.
