Replace Content in PRE Tags with HTML Entities
If you have a website that relies heavily on PRE tags, you know the important of converting PRE tag content to their HTML entities. Doing so prevents worlds of possible rendering issues. The following PHP snippet HTML-Entitizes (?) any code within PRE tags:
//replaces pre content with html entities
function pre_entities($matches) {
return str_replace($matches[1],htmlentities($matches[1]),$matches[0]);
}
//to html entities; assume content is in the "content" variable
$content = preg_replace_callback('/<pre.*?>(.*?)<\/pre>/imsu',pre_entities, $content);
I use this for just about every post I write. You could also stick this in your CMS if you have clients that may have use for PRE tags.
![Being a Dev Dad]()
I get asked loads of questions every day but I'm always surprised that they're rarely questions about code or even tech -- many of the questions I get are more about non-dev stuff like what my office is like, what software I use, and oftentimes...
![CSS vs. JS Animation: Which is Faster?]()
How is it possible that JavaScript-based animation has secretly always been as fast — or faster — than CSS transitions? And, how is it possible that Adobe and Google consistently release media-rich mobile sites that rival the performance of native apps?
This article serves as a point-by-point...
![Introducing MooTools ScrollSidebar]()
How many times are you putting together a HTML navigation block or utility block of elements that you wish could be seen everywhere on a page? I've created a solution that will seamlessly allow you to do so: ScrollSidebar. ScrollSidebar allows you...
![Google Extension Effect with CSS or jQuery or MooTools JavaScript]()
Both of the two great browser vendors, Google and Mozilla, have Extensions pages that utilize simple but classy animation effects to enhance the page. One of the extensions used by Google is a basic margin-top animation to switch between two panes: a graphic pane...
Beware that having someting like “something” in another would leave you with one opening and two closings. If this is a possible usecase, you might use a regex like this :
/(.*?[.*]*)/imsu
…but it still wouldn’t handle the case of having a single closing tag inside another . Could someone manage to write a regex which would handle this case ?
The function name (pre_entities) should be between quotes otherwise it will throw a notice.
Beware that having a pre tag inside another pre tag would leave you with one pre opening and two pre closings. If this is a possible usecase, you might use a regex like this :
/<pre.*?>(.*?[<pre.*?>.*<\/pre>]*)<\/pre>/imsu
The tags got stripped in my first comment, sorry about that, if htmlentities show up in the regex, replace them with the good characters …but it still wouldn’t handle the case of having a single closing pre tag inside another pre. Could someone manage to write a regex which would handle this case ?
The function name (pre_entities) should be between quotes otherwise it will throw a notice.
It works as long as you don’t have nested <pre> tags.
I wrote about this on my blog but the only real way to do it is to use an XML parser.
One issue to watch out for is to not encode any of the content before this is run, as it will double-entitize the ampersand e.g., &.
Also, would there be any issues if not matches are found?
To solve the nested ‘pre’ tag issue, just use some non-standard tags that you’re sure won’t be in your content, rather than ‘pre’ (i.e. ‘mycode’). Your regular expression then becomes a match for the ‘mycode’ tags, and you can immediately follow it up with another preg_replace () to turn the ‘mycode’ tags into ‘pre’ tags after you’re done htmlentitizing the content.
I’ve been using elliotswan.com/postable. It seems to get the job done for me. But it’s nice to know this option.
Could someone explain how to fix the following notice?
Notice: Use of undefined constant pre_entities – assumed ‘pre_entities’ in C:\wamp\www\example.com\admin\get_posts.php on line 16
doh! put quotes on ‘pre_entities’, fixes it. Thanks David! Great snippet.
Thank you for the tip! I couldn’t find what was going wrong with the HTML…