Support » Requests and Feedback » Storing markup and html

  • One thing that is nice about the TextPattern model is that it stores each entry in the db as both what the user entered and as the rendered XHTML — for instance an entry might be marked up using Textile or Markdown, which is stored separately from the converted code.
    Does WordPress do something like this?
    It would be nice if the formatting engine were not an all or nothing proposition, or that it could be turned off and old entries would still work because the formatted entry could be used…

Viewing 1 replies (of 1 total)
  • Hear hear —
    Another problem with using Textile or some other text processor in WordPress at present is that the information sent out via the RSS feed is the pre-formatted text, which will not be parsed by 99% of RSS readers, one would imagine…

Viewing 1 replies (of 1 total)
  • The topic ‘Storing markup and html’ is closed to new replies.