dorayme wrote:
> In article <iv4dqj$vs2$>,
> "Neil Gould" <> wrote:
>
>> dorayme wrote:
>>> In article <iv48er$iki$>,
>>> "Neil Gould" <> wrote:
>>>
>>>> dorayme wrote:
> ...
>>> I know many of my own browsers are set to 16 for most reading
>>> fonts but I forget if I set them or they came that way and they
>>> suited me! The mozilla url on the page at the url below is a
>>> small clue that maybe they come that way. I guess (just noticed
>>> this).
>>>
>> My FF5s are set to 16, and because I didn't bother to change them I
>> presume they came that way. I wonder what that "16" would mean,
>> anyway? Like an amplifier that can be turned up to 11, I think it's
>> a relative figure that will not have an absolute physical size
>> representation due to such things as the size, pixel resolution and
>> font rendering methods of the users' monitor and video subsystem.
>>
>
> I think it just means pixels. But maybe you are right and it
> happens to be pixels without quite meaning it.
>
Or, it's a number that has nothing to do with pixels or anything else; 16
pixels on a monitor with a vertical screen size of 15" and vertical
resolution of 1500 would render medium fonts 0.16" high. But, since I can
read it, I'm pretty sure that's not happening!
>>> Just got to wondering about it for a page I am cobbling to
>>> together, a draft of which is at
>>>
>>> <http://dorayme.netweaver.com.au/diff...textSpill.html
>>>
>> Well, your page taps into one of my beefs with CSS-based styling. No
>> matter how well-crafted, only the simplest of page layouts can avoid
>> being trashed by user settings.
>
> Well, I guess it depends on what you mean by simplest.
>
Full width, single-column, simple div parameters, etc.
>> Perhaps an idea from early web days may still be useful...
>> have a button that redirects users with special needs to another
>> version of the site.
>
> Now and then, this is probably not too bad an idea but we should
> aim not to need to do this.
>
Well, it's a down-side to the generalized markup approach that has plagued
presentation since SGML days, but at least then someone had to access a
common DTD to render a document. It might be one reason why people prefer
one browser over another, but IMO all browsers suck at rendering something
or other, and user settings can make things completely unreadable.
--
Neil