How Does WP Use Textile?

  • I have been searching through the WP source trying to work out how WP uses the Textile plugin. I can sort of work out how it textiles input to go into the database, but can’t seem to find how it turns the markup back to the input text, since there doesn’t seem to be a detextile() function, and as far as I can see notextile() handles areas that are escaped from textile processing.
    Can anyone cast some light on this?
    It’s not a showstopper for my site or anything, just something I’m wondering about (thus the post to the Misc forum).

Viewing 1 replies (of 1 total)

  • WordPress has a concept of “filter” plugins, which is what Textile, Markdown, etc are. The idea is to store the text un-converted in the database, and convert it on the way out.

    The idea is that if, for instance, you wanted to upgrade your site to XHTML 1.1 or even XHTML 2 … or whatever the next version of XHTML is after that … you would upgrade to Textile 5 (or whatever we’re up to by then) and your output would be safe, instead of having to update all your posts by hand…

    Of course, the real reason is that nobody has written a good alternative markup that can convert *back* from XHTML.

Viewing 1 replies (of 1 total)
  • The topic ‘How Does WP Use Textile?’ is closed to new replies.