Support » Everything else WordPress » can I disable all text-to-HTML translators in WP?

  • I want to use WordPress, but I don’t want to use any sort of HTML pseudocode, e.g., __foo__ instead of foo, that sort of thing. Perhaps I’m an eccentric, but it’s much easier for me to just type the XHTML myself.
    (Elsewhere there’s a discussion, “is anybody’s site XHTML compliant?” Mine is – a while ago, I ran all 1200 [hand-coded] pages through an XHTML validator, and got exactly eight errors, mostly unescaped ampersands in href attribute values. I fixed ’em.)
    So: can I configure WordPress not to modify in any way the text I type in? Don’t replace __foo__ with foo, don’t insert / remove / escape any XHTML tags, don’t do anything.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Apparently not – even with all relevant options disabled, WordPress still monkeys with my code, by inserting inside


    My site has been XHTML 1.1 Transitional and CSS 2 compliant for about 2 months. I’ve never had any problems with WP monkeying with my posts, but then again I never use any XHTML in them.

    My reading of the DTD (pages 601 & 595 of HTML & XHTML: The Definitive Guide, 5th edition, by Musciano & Kennedy, is that blockquote contains Flow, where Flow is defined as #PCDATA or various other things.
    Plus, I just sent
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE html
    PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
    <html xmlns="" xml:lang="en" lang="en">
    <meta http-equiv="content-type" content="text/html; charset=UTF-8" />

    Block quote

    to, and it came back valid.
    So I’m skeptical that is required within

    . Certainly they’re allowed, but they are not required.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘can I disable all text-to-HTML translators in WP?’ is closed to new replies.