|
Re: Font sizes.
by davis (Vicar) on Feb 11, 2003 at 10:27 UTC
|
Not a bad idea
As a stopgap solution, quite a few decent browsers (half-assumption, I only really use Mozilla) allow you to set the minimum font size of any text.
You could also mess with your User Settings, and add some css to enlarge the font size. Having just looked at mine though, I'm not sure that you could apply it to just the replies.
cheers
davis
Is this going out live?
No, Homer, very few cartoons are broadcast live - it's a terrible strain on the animator's wrist
| [reply] |
|
|
Well, I tried setting some CSS, but that didn't work at all.
The reason might be the utter garbage Perlmonks seems to
be producing. Replies get markup that looks like:
<UL><UL><font size = "2">User reply<P>More reply</font>
What kind of markup is *that*? No list items, no end of list
markup, <font> spanning over paragraphs. Of course,
because of the hardcoded font size using the <font>
tag, it's no wonder CSS can't cope.
Abigail | [reply]
[d/l]
[select] |
|
|
* {
color: white !important;
background-color: black !important;
FONT-FAMILY: sans-serif;
FONT-SIZE: 13px;
FONT-WEIGHT: normal;
}
a { text-decoration: underline; }
a:link { background-color: #000; }
a:visited { background-color: #131; text-decoration: strikethrough; }
form { display: inline; }
textarea {
width: 100%;
height: 25em;
}
pre { font-family: monospace; }
tt * {
font-family: monospace;
color: green;
}
| [reply]
[d/l] |
|
|
Mozilla can do this - simply edit the userContent.css file, as documented in Customizing Mozilla
Cheers
davis
Is this going out live?
No, Homer, very few cartoons are broadcast live - it's a terrible strain on the animator's wrist
| [reply] |
|
|
I've yet to find a document that describes the used element
ids on perlmonks, which would be needed to do something
with CSS. And I don't really fancy reenginering
the generated HTML.
Abigail
| [reply] |
Re: Font sizes.
by thraxil (Prior) on Feb 12, 2003 at 16:52 UTC
|
body,td,p,li,pre {
font-size: 16px !important;
}
in the user stylesheet on my user settings page seems to catch about 90% of the text. with a few more rules, you could probably get the rest of it.
the <font> tags should definitely go though. they're sooo 1996...
update: this:
body * {
font-size: 16px !important;
}
catches every bit of text on the site i can find. (tested in mozilla).
anders pearson
| [reply]
[d/l]
[select] |
|
|
Well, it doesn't work for me. All I've managed to do with
CSS so far is to set the background colour. But only partially.
Anything that's boxed somehow (replies, input fields, nodelets)
just stay white. Font-size stays tiny.
Abigail
| [reply] |
Re: Font sizes.
by particle (Vicar) on Feb 12, 2003 at 21:57 UTC
|
although this is a bit of a kludge, you can force the font tag to display a specific font-size like so:
font { font-size:11pt; }
this has some side effects, but it will change the size of the font in reply nodes.
~Particle *accelerates*
| [reply]
[d/l]
[select] |
|
|
Unfortunally, it doesn't. Not with my Netscape 4.77.
Abigail
| [reply] |
Re: Font sizes.
by Aristotle (Chancellor) on Feb 18, 2003 at 16:52 UTC
|
It's unfortunately commonplace for browsers not to inherit the properties set for the body tag down into tables. You can get around that by explicitly specifying the same properties for table cells.
"Reverse engineering" the HTML is a chore indeed; it might be more helpful to just look at the site's own CSS at the top of the page source. My Perl-blue theme is a fairly comprehensive batch of settings that might also help.
pmdev are aware of the sometimes incredibly awful HTML quality of the site, but it's a huge code/page base to fix and manpower is limited, esp as each patch has to be tested and applied by one of the much fewer gods. Also, Everything's approach of storing the majority of the code itself in the database, though very powerful and flexible, also has obvious drawbacks with regards to collaborative development efforts.
It's a slowly evolving work in progress.
Makeshifts last the longest.
| [reply] |
