On 7 June 2010 13:52, Joshua Murphy <email@example.com> wrote:
> On Sat, Jun 5, 2010 at 3:09 PM, Mick <firstname.lastname@example.org> wrote:
>> On Saturday 05 June 2010 19:13:24 Mick wrote:
>>> Hi All,
>>> I emerged rxvt-unicode because aterm which I have been using faithfully for
>>> years does not do UTF8, but as you can see in the attachment all bold
>>> characters look distorted. *In xterm and aterm they look nice and clear
>>> *when bold.
>>> How can I fix this?
>> It seems that it was a limitation of the fixed font that I had defined for
>> aterm in .Xresources:
>> Setting a different font and using xft seems to overcome this problem:
>> /usr/bin/urxvt -pe tabbed -fn "x:Bitstream Vera Sans Mono
>> No idea why aterm copes with fixed font and urxvt does not ...
> The 'why' I can answer. Aterm doesn't do antialiasing for the fonts
> while urxvt does, and the 'fixed' font wasn't made to be able to
> handle antialiasing cleanly.
Thanks, it makes sense now.