Re: Large fixed-width text

From: Petr Jelinek <pjmodos(at)pjmodos(dot)net>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL www <pgsql-www(at)postgresql(dot)org>
Subject: Re: Large fixed-width text
Date: 2009-09-28 05:33:42
Message-ID: 4AC04AB6.8050608@pjmodos.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

Dave Page napsal(a):
> On 9/27/09, Petr Jelinek <pjmodos(at)pjmodos(dot)net> wrote:
>
>> Dave Page napsal(a):
>>
>>>> Anyway those #txtArchives pre and #txtArchives tt do not affect
>>>> documentation but they indeed seem to be plain wrong, they are actually
>>>> only
>>>> used by Opera (and maybe Chrome , I don't have that browser) and the text
>>>> looks huge there. In FF and Safari they are overwritten by
>>>>
>>>> #pgContainer code, #pgContainer pre, #pgContainer tt {
>>>> font-size: 1.2em;
>>>> }
>>>>
>>>> in geckofixes.css (yes it loads for Safari too on my machine and it's a
>>>> good
>>>> thing) and in IE they're overwritten by
>>>>
>>>> * html #txtArchives pre { font-size: 100%; }
>>>>
>>>> in iefixes.css.
>>>>
>>>>
>>> txtArchives is used by archives.postgresql.org, not the docs.
>>>
>>>
>> Cite from the first sentence: *Anyway those #txtArchives pre and
>> #txtArchives tt do not affect
>> documentation*
>>
>>
>
> Yes, i did read what you wrote. I was pointing out what they do affect.
>

Oh, ok, I know they affect mail body in archives and all I said is true
- they are overwritten by other rules in most browsers and the text is
huge in browsers where they're not overwritten. I think better default
would be 120%, it may still look big somewhere but not as big as it does
now and it compensates for that monospace vs normal font default size.

--
Regards
Petr Jelinek (PJMODOS)

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message std pik 2009-09-28 06:13:40 Postgres performance
Previous Message Dave Page 2009-09-27 19:16:09 Re: Large fixed-width text