Replacement of <font size=> tag?

FCKEditor is, says the website, XHTML 1.0 compliant. But the <font tag is not supported in XHTML 1.0 strict, having been deprecated since HTML 4.01, I believe.

In the interests of standards, accessibility and competition with RADeditor for example it would be great to be able to select XHTML 1.0 Strict support as the default with XHTML 1.0 Transitional or others perhaps as options.

I want to hasten to add that the improvements in terms of standards support are noticeable and appreciated - good job!

We just have to be totally accessible by law as a state university, so need to look for Strict. May have to purchase RAD but I'm trying to hold them off with the promise that surely FCKEditor is soon to go strict!

Hi,

Yes this is an anoying thing. I have searched Hi and Low and cant find a place to change font-size to style="font-size:
So if anyone can point us in the right direction it would be nice.

I would like to do the same.

I think if there is a new standard of the W3 committee to make cleaner HTML then use it.

XHTML 1.1 is a dream come true in my eyes.

There is no more need for <font> that's what <div style=""> is for.

I would like to see that in an upcoming version of FCKeditor. At least somehow set options so you can choose between HTML 4.0 or HTML 4.01 / XHTML 1.1?

XHTML isn't just a standard to make cleaner HTML, you can do perfectly clean HTML with HTML 4.01 and it will be valid with any current User Agent.

On the other side, XHTML is more that just deprecation some tags and attributes, if you are aiming for strict compilance with XHTML then you should go all the way and send it as application/xhtml+xml and then it won't render in IE (and I don't think that you want that), so you're only "fooling" yourself if you think that by removing some tags you are on the next level of standards.

Read carefully this document as it explains the problems much better that I would ever be able to do:
http://www.hixie.ch/advocacy/xhtml

pmger:

Accessibility has less to do about XHTML and more to do with proper semantic markup.

Being strict, can help, but semantics are what's more important.

Of course, the font-tag and other styles have no meaning what-so-ever, so they shouldn't be used at all.

We've been using Xstandard as it's the ONLY inline editor we've found that can handle proper semantic markup with the idea of accessibility in mind.

I think FCKeditor is close, but has a way to go.

The other major issue I have with FCKEditor (and ALL javascript based editors, for that matter) is that they seem to be inable to create proper paragraph tags when used within Firefox.