[FFmpeg-devel] ffmpeg.org clean up

Robert Swain robert.swain
Fri Feb 20 00:25:46 CET 2009

2009/2/19 Stefan Gehrer <stefan.gehrer at gmx.de>:
> Robert Swain wrote:
>> 2009/2/15 Jan Knutar <jknutar at nic.fi>:
>>> On Sunday 15 February 2009, Dave Dodge wrote:
>>>> On Sun, Feb 15, 2009 at 02:34:02AM +0000, Robert Swain wrote:
>>>>> Don't you find reading lines as long as this uncomfortable? :
>>>> I guess if you tend to maximize applications I can see how you might
>>>> find it to be an issue.  Personally it would take a very special
>>>> situation, such as viewing HD screencaps, for me to make my browser
>>>> window anywhere close to that wide.
>>> Scalability is much nicer than assumptions about the amount of chars the
>>> user can fit on the screen.
>> So, you don't all object to having a maximum width because you don't
>> run your browsers maximised, but rather you do complain about fixed
>> width not scaling down to smaller widths on smaller screens. The
>> suggestion of having:
>> #container {
>>     max-width: <some value>;
>>     width: 100%;
>> }
>> Seems to be a reasonable compromise. How many people actually have
>> their browsers maximised and want really long lines? Aurelien? Jan?
>> Anyone?
> I usually browse maximised on 1920 pixels wide and I can not see any
> point in limiting the width. On the contrary, having the full width
> gets more information on the screen and really makes good use of the
> resolution even without having multiple windows open.

And it's not fixed-width. :)

> Also, has sans-serif been dropped now for a good reason?

Some people wanted sans, some wanted serif. If you change your
browser's default font it will be whatever you choose.

> But I don't want to complain, the page look tons better than it used to.
> Thanks for that.



More information about the ffmpeg-devel mailing list