TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
I think I've had this discussion in the past here. While none of the browsers,
not even Opera, support 100% of the CSS spec, it is certainly possible to
completely replace font tags in IE 3, IE 4, NN 4, and Opera, which was my
original (and only) contention. There is no good reason to use the font tag ever
again.
Both the major browsers seem to be having difficulty re-writing the parts of the
rendering engine that control white space, so margins, padding, borders, and so
on is still patchy, but you can't do that with a font tag either.
Check out the Web Review site for what you need to avoid and you won't have too
many problems.
Abby Schiff <aschiff -at- factset -dot- com> wrote:
>
> One caveat here: In my experience, CSS works better in IE 3.x and higher
> than in Netscape. Although Netscape Navigator 4.x and higher support CSS
> (sort of), its support of styles inside tables leaves MUCH to be desired.
> This can make things dicey if you're using page templates that place all
> body-text into a table!!
>
> FWIW,
> Abby Schiff
>
> ====
> Steve wrote:
> > Bag the directly applied fonts altogether and go with Cascading
> > Style Sheets. FrontPage 98 supports style sheets but forces you
> > to set them up manually. Style sheets easily and cleanly replace
> > everything you can do with font tags and, according to statmarket.com,
> > they are supported by 95% of the browsers in use on the WWW.
