CSS Fonts: Detect Font DPI use specific CSS

"Neal" <neal413 (AT) yahoo (DOT) com> wrote

Not inventing. Note my response to another of your messages in which I
confirmed the problem ... with some browsers.

I did a test - see http://users.rcn.com/neal413/fontsizetest.html - where
I compare calculated percentages to what it should be. In each section
we're comparing:

1) 81%
2) 90% nested in 90%
3) 100% (baseline)
4) 90% of 90% of 90%
5) 72.9%

1) and 2), and 3) and 4), should be the same size, one calculated in the
browser, the other calculated by hand and set as a direct size.

I'm interested in the observations of others and results in other
browsers, or differences in the same browsers on other machines.

Okay, on my main PC: NN4.08 and 4.80 had major problems; Opera 7.54,
IE5.01, 5.5, and 6.0 had problems in the 3rd group; Mozilla was (to my eye)
perfect.

Which basically confirms my earlier assertion that the % unit causes
problems for some browsers. Though your point is well taken that it may
also depend on the PC.

"C A Upsdell" <cupsdell0311XXX@-@- (AT) XXXrogers (DOT) com> wrote

"Beauregard T. Shagnasty" <a.nony.mous (AT) example (DOT) invalid> wrote in message
news:az9md.9647$zk7.8184 (AT) twister (DOT) nyroc.rr.com...
C A Upsdell wrote:

.legalese { font-size: 90% }

Which can result in the 'type gets insanely small' problem; whereas my
equivalent suggestion -- .legalese { font-size:small; } -- does not.

Sure does on my pages. 90%, that is.

Not if it is nested, which what the OP was concerned with. 90% of 90% of
90% ... can quickly become too small to read, whereas font-size:small
font-size:small font-size:small ... does not.

Wow, someone who actually is still paying attention to the actual problem at

hand a.o.2 ripping into eachother...

In most cases, all applicable for that matter, I use relative type sizes.
However, in this case I am working on a site designed by someone else - some
one who knew nothing about web design, as esp. CSS. There really is no easy
fix for this situation without re-codeing from scratch, something that is
not an option due to deadlines (this is internal corporate courseware).

This leaves me with the option that i've already reached - a user 'options'
screen allowing the user to select type sizes from a variety of CSS
documents (differing size/colour models). This is then set using JS and
served via a cookie. Easy, done.. dirty.

The reason it's done this way a.o.2 ASP or PHP site transformations is
because the courseware needs to operate as easily from a CD as from the
net - not possible with server technologies - so don't rag on me for that.

In the end, this is a quick fix better left to the annuls of time - the
whole thing is gonna get dropped into the template I've created for all
future projects.

Many thanks to those who remained somewhat on topic.

Regards,
David

in comp.infosystems.www.authoring.stylesheets, brucie wrote:

In comp.infosystems.www.authoring.stylesheets C A Upsdell said:

Once upon a time, I did use % units, and I did have endless
shrinking text size problems (at least with some browsers),

sounds like an inheritance issue with your css. i've never had any
problems using %.

That is because you have not been stupid enaugh to use unclosed P
elements and different than 100% font for in NN4. Irrelevant today, of
course...



--
Lauri Raittila <http://www.iki.fi/lr> <http://www.iki.fi/zwak/fonts>