public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Blurred bold characters in urxvt
Date: Mon, 7 Jun 2010 14:19:18 +0100	[thread overview]
Message-ID: <AANLkTikT_1Waj4f2hvyG1x_2h8cI3A8uGW_wJpyqRoHA@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimtBWzvJkgUWv7RUWaqpJg_oaTFNenJSEdlMZE1@mail.gmail.com>

On 7 June 2010 13:52, Joshua Murphy <poisonbl@gmail.com> wrote:
> On Sat, Jun 5, 2010 at 3:09 PM, Mick <michaelkintzios@gmail.com> 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:
>>
>> aterm*font:-*-fixed-*-*-*-*-20-*-100-*-*-*-*-*
>>
>> Setting a different font and using xft seems to overcome this problem:
>>
>> /usr/bin/urxvt -pe tabbed -fn "x:Bitstream Vera Sans Mono:pixelsize=15"
>>
>> No idea why aterm copes with fixed font and urxvt does not ...
>>
>> --
>> Regards,
>> Mick
>
> 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.
-- 
Regards,
Mick



      reply	other threads:[~2010-06-07 14:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-05 18:13 [gentoo-user] Blurred bold characters in urxvt Mick
2010-06-05 19:09 ` [gentoo-user] " Mick
2010-06-07 12:52   ` Joshua Murphy
2010-06-07 13:19     ` Mick [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTikT_1Waj4f2hvyG1x_2h8cI3A8uGW_wJpyqRoHA@mail.gmail.com \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox