[FFmpeg-cvslog] r22522 - in trunk: configure libavcodec/Makefile libavcodec/dsputil.c libavcodec/dsputil.h libavcodec/dwt.c libavcodec/dwt.h libavcodec/ivi_dsp.c libavcodec/snow.c libavcodec/snow.h libavcodec/x86/...

Måns Rullgård mans
Mon Mar 15 22:49:33 CET 2010


Justin Ruggles <justin.ruggles at gmail.com> writes:

> Jai Menon wrote:
>
>> On Tue, Mar 16, 2010 at 2:23 AM, Michael Niedermayer <michaelni at gmx.at> wrote:
>>> On Sun, Mar 14, 2010 at 07:32:23PM -0400, Alex Converse wrote:
>>>> On Sun, Mar 14, 2010 at 7:21 PM, Michael Niedermayer <michaelni at gmx.at> wrote:
>>>>> On Sun, Mar 14, 2010 at 05:00:34PM -0400, Alex Converse wrote:
>>>>>> On Sun, Mar 14, 2010 at 4:50 PM, Michael Niedermayer <michaelni at gmx.at> wrote:
>> 
>> [...]
>> 
>>>> I challenge you to try to do you H.264 refactoring in an soc style
>>>> topic branch in SVN for two months... If you aren't too busy trying to
>>>> find fonts less readable than the ones you use now.
>>> iam using courier new in kwrite which is quite nice except the l/1 issue
>>> suggestions for some other font are welcome, but most other monospaced
>>> fonts ive seen dont look that good.
>> 
>> since you already use a truetype font, maybe try anonymous pro
>
> That is an interesting font.

Bonus points for providing bitmaps at small sizes (or very, very good
hinting) for a nice, crisp render.

> I use Consolas, but I might consider switching.

Hmm, I don't think I like that one.

I use Lucidatypewriter in emacs.  At small sizes, bitmap fonts are
usually much more legible than truetype.  They're also faster to
render.

I've also found the Android fonts[1] to be very readable at small
sizes (no surprise).  They're not as good at large sizes though.

[1] http://android.git.kernel.org/?p=platform/frameworks/base.git;a=tree;f=data/fonts;hb=HEAD

-- 
M?ns Rullg?rd
mans at mansr.com



More information about the ffmpeg-cvslog mailing list