Home/ Questions/Q 1034929
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-16T14:28:07+00:00

I have an inline markup editor built into my website, which should produce XHTML

  • 0

I have an inline markup editor built into my website, which should produce XHTML compliant markup. But as you can see, it uses the deprecated font tag and size attribute. 

<font style="font-family: Courier New; color: rgb(0, 0, 153);" size="2">
   asdfa
   <span style="color: rgb(0, 51, 0);">
    a
    <font size="5">fds</font>
   </span>
</font>

On other browsers, it produces the <span class="Apple-style-span" style="font-size: xx-large;"> instead of <font size="5">

Is there a Javascript/Regex solution to taking the first set of markup and replacing it with XHTML compliant markup using style attribute and span tag.
Thanks in advance!!

(ps. jQuery can be used too)

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The markup above is perfectly valid in XHTML 1.0 Transitional.

    Whether deprecated elements like <font> are used are a completely orthogonal issue to whether XHTML or HTML syntax is used. XHTML 1.0 is nothing more or less than a restating of HTML 4.01 in XML syntax: consequently there are Transitional and Strict variants just as there are for HTML 4.

    <font size="5"> and <span class="Apple-style-span" style="font-size: xx-large;"> are semantically equally useless. If you want markup to use a set of defined elements and classes that are meaningful in the context of your site, you’ll have to hack the editor into using those, instead of being based purely on visual formatting.

    You could parse the XHTML and alter it as a later step, to try to make it look better. But regex is not at all an adequate tool to do so, as previously mentioned. You would need an XML parser, then you’d fix up the elements and attributes, then re-serialise it to XHTML. It would be sensible to do this on the server-side, because getting an XML parser on the client-side is slightly tricky, and you will need to do it on the server side anyway if you’re going to be cleaning non-whitelisted elements and attributes.

    • 0