Converting XHTML To Text-Only Version Using ColdFusion And XSLT

Posted May 20, 2009 at 7:13 PM

Tags: ColdFusion

The other day, I was having a discussion about sending emails using ColdFusion. At one point, the conversation turned to email format. To me, in this day an age, it seems silly to even worry about text-only versions of emails. I mean really - are there even any clients anymore that can't handle HTML formatting? I think even BlackBerrys can handle HTML formatted emails. As such, I generally have no problem building apps that only send out HTML versions.

But, I did think it would be a fun exercise to come up with a way to take XHTML content for emails and automatically convert it into a text-only version. I really love writing and working with XML and it just seemed that XML Transformations using XSLT would be the right tool for the job. The following demo is what I came up with after a little bit of trial and error. I'm no XSLT expert (far from it), so it's not perfect. But, considering that this is automatically created, "just in case" content, I think it's pretty good:

 Launch code in new window » Download code as text file »

  • <!--- Save HTML content. --->
  • <cfsavecontent variable="strHTML">
  •  
  • <h1>
  • Thank you for your purchase!
  • </h1>
  •  
  • <p>
  • Invoice number: <strong>12345</strong><br />
  • Price: <strong>$19.95</strong>
  • </p>
  •  
  • <hr />
  •  
  • <h2>
  • Purchased Products
  • </h2>
  •  
  • <table cellspacing="5" border="1">
  • <tr>
  • <td>
  • Muscle Girls Gone Wild
  • </td>
  • <td>
  • $10.95
  • </td>
  • </tr>
  • <tr>
  • <td>
  • Female Muscle - The Definitive Guide
  • </td>
  • <td>
  • $9.00
  • </td>
  • </tr>
  • </table>
  •  
  • <hr />
  •  
  • <p>
  • If you have any questions about your order please
  • contact us at
  • <a href="mailto:orders@amazon.com">orders@amazon.com</a>.
  • </p>
  •  
  • </cfsavecontent>
  •  
  •  
  • <!--- Define the XSLT --->
  • <cfsavecontent variable="strXSLT">
  •  
  • <?xml version="1.0" encoding="ISO-8859-1"?>
  • <xsl:transform
  • version="1.0"
  • xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
  •  
  • <!--- Store variable for new line. --->
  • <xsl:variable
  • name="new-line"
  • select="'&#10;'"
  • />
  •  
  • <!--- Store variable for double-new line. --->
  • <xsl:variable
  • name="new-lines"
  • select="concat( $new-line, $new-line )"
  • />
  •  
  •  
  • <!---
  • Match the root node plus any nodes that are not
  • matched specifically by the templates defined
  • below.
  • --->
  • <xsl:template match="*">
  • <xsl:apply-templates select="text()|*" />
  • </xsl:template>
  •  
  • <!--- For all text nodes, output trimmed value. --->
  • <xsl:template match="text()">
  • <xsl:value-of select="normalize-space( . )" />
  • </xsl:template>
  •  
  • <!--- Denote primary header with hrule. --->
  • <xsl:template match="h1">
  • <xsl:apply-templates select="text()|*" />
  • <xsl:value-of select="$new-line" />
  • <xsl:text>---------------------------------</xsl:text>
  • <xsl:value-of select="$new-lines" />
  • </xsl:template>
  •  
  • <!--- Denote secondary headers with hash marks. --->
  • <xsl:template match="h2|h3|h4|h5">
  • <xsl:text>## </xsl:text>
  • <xsl:apply-templates select="text()|*" />
  • <xsl:value-of select="$new-lines" />
  • </xsl:template>
  •  
  • <!--- Turn block level elements into text-only. --->
  • <xsl:template match="p|blockquote|li">
  • <xsl:apply-templates select="text()|*" />
  • <xsl:value-of select="$new-lines" />
  • </xsl:template>
  •  
  • <!--- Add new line after table. --->
  • <xsl:template match="table">
  • <xsl:apply-templates select="*" />
  • <xsl:value-of select="$new-line" />
  • </xsl:template>
  •  
  • <!--- Turn table rows into bracketed values. --->
  • <xsl:template match="tr">
  • <xsl:apply-templates select="*" />
  • <xsl:value-of select="$new-line" />
  • </xsl:template>
  •  
  • <!--- Bracket table values. --->
  • <xsl:template match="td">
  • <xsl:value-of select="'[ '" />
  • <xsl:apply-templates select="text()|*" />
  • <xsl:value-of select="' ]'" />
  • </xsl:template>
  •  
  • <!---
  • Strip out any inline tags (and start them off with
  • an initial space so that nested and sibling tags don't
  • get concatenated text).
  • --->
  • <xsl:template match="strong|em|span|a">
  • <xsl:text> </xsl:text>
  • <xsl:value-of select="text()" />
  • </xsl:template>
  •  
  • <!---
  • Replace hrule with manual dashes.
  • NOTE: template also named for manual execution.
  • --->
  • <xsl:template match="hr" name="hr">
  • <xsl:text>. . . . . . . . . . . . . . . . .</xsl:text>
  • <xsl:value-of select="$new-lines" />
  • </xsl:template>
  •  
  • <!--- Replace break tag with new line. --->
  • <xsl:template match="br">
  • <xsl:value-of select="$new-line" />
  • </xsl:template>
  •  
  • </xsl:transform>
  •  
  • </cfsavecontent>
  •  
  •  
  • <!---
  • Convert to the HTML to text only. As we are doing this,
  • we need to wrap the HTML in a root node so that the XML
  • document we parse is well formatted.
  • --->
  • <cfset strTextOnly = XmlTransform(
  • ("<data>" & strHTML & "</data>"),
  • Trim( strXSLT )
  • ) />
  •  
  • <!--- Strip out doc type. --->
  • <cfset strTextOnly = Trim(
  • REReplace(
  • strTextOnly,
  • "<[^>]*>",
  • "",
  • "one"
  • )
  • ) />
  •  
  •  
  • <!--- Output the text-only verson. --->
  • <cfset WriteOutput( strTextOnly ) />

As you can see, the HTML would need to be stored in some sort of content buffer and it would have to be XHTML compliant such that it could be parsed using XmlParse(). My HTML content doesn't happen to have any special characters (ex: ampersand); but, if it did, I assume they would have to be escaped prior to XML parsing. Once the XHTML is parsed, I then use ColdFusion's XmlTransform() and the given XSLT document to create the following output (copied from rendered page source):

Thank you for your purchase!
---------------------------------

Invoice number: 12345
Price: $19.95

. . . . . . . . . . . . . . . . .

## Purchased Products

[ Muscle Girls Gone Wild ][ $10.95 ]
[ Female Muscle - The Definitive Guide ][ $9.00 ]

. . . . . . . . . . . . . . . . .

If you have any questions about your order please contact us at orders@amazon.com.

For an automated process, I think that's pretty cool! I'm not sure I would even bother putting this into an application; but, if I needed to, it's nice to see that automatically converting HTML email content into text-only content is a rather straightforward task.

Download Code Snippet ZIP File

Post Comment  |  Ask Ben  |  Permalink  |  Other Searches  |  Print Page




Reader Comments

May 21, 2009 at 11:40 AM // reply »
23 Comments

This will be useful for sending email newsletters. Thanks Ben.


May 21, 2009 at 11:49 AM // reply »
6,516 Comments

@Brian,

My thoughts exactly.


May 21, 2009 at 1:11 PM // reply »
23 Comments

Interesting post. Speaking of which, when you have a free moment, will you be so kind as to answering the email I just sent you.

Thank you kindly.

Have a great day.


May 21, 2009 at 5:32 PM // reply »
3 Comments

For a comprehensive XSL template to convert XHTML to Text you use the screen reader template that comes with XStandard as a good starting point.

Email newsletters - I use XSLT to transform XHTML to plain text for our newsletter module. It works nicely.


May 22, 2009 at 12:17 PM // reply »
23 Comments

Hey Ben-

I know you are a way busy guy, but you think maybe you can answer my question as soon as you get a chance. I dont mean to be a pain but its really important.

Thanks, and sorry to bother.

Have a happy holiday weekend.


May 25, 2009 at 10:29 AM // reply »
6,516 Comments

@Johans,

I didn't know that XStandard came with a screen reader XSLT. Aswesome!


May 26, 2009 at 8:34 AM // reply »
30 Comments

Ben!

The problem isn't so much if e-mail clients can or can't read HTML-based messages, it's the darn rendering engines running within the email clients or webmail clients that make it a horrendous effort to create equal looking e-mails ;-)

Luckily there's http://www.email-standards.org/ ;-)


May 27, 2009 at 8:45 AM // reply »
6,516 Comments

@Sebastiaan,

Email standards is good, but depressing :)


Jun 10, 2009 at 10:23 AM // reply »
23 Comments

Hey Ben-

Just wanted to say thanks for answering my questions. Good answer. As always, it was really great talking to you.

Hope to see you again real soon ;)!


Aug 8, 2009 at 9:26 AM // reply »
1 Comments

mein gott! you forget that many people prefer to turn off html email rendering, not merely to avoid their bandwidth sucking aquaintances spamming them with twinkling eFun, but so that slimy requests for evil embedded links can't be used by noxious, pestulant spammers to verify their manky catalogues of addresses and domains.

gah.


Post Comment  |  Ask Ben

Recent Blog Comments
Nov 20, 2009 at 11:32 PM
Five Months Without Hungarian Notation And I'm Loving It
I've used headless camel case for years for not only ColdFusion variables, but also SQL tables and fields... pretty much everything involving code. I also subscribe to the "don't abbreviate and clea ... read »
Nov 20, 2009 at 11:00 PM
Five Months Without Hungarian Notation And I'm Loving It
@Marcel, Yeah, I always err on the side of longer but more readable variable names. As for the camel casing of CF methods and the headless camel casing of custom items, I get around this by always ... read »
Nov 20, 2009 at 10:56 PM
Five Months Without Hungarian Notation And I'm Loving It
I use the following and love it: my.namespace.MyComponents.functionMethodsOrUDF() CONSTANT_VALUES_OR_PROPERTIES One thing I always try is to CamelCaseBuiltInColdFusionFunctions() so others can tell ... read »
Nov 20, 2009 at 5:38 PM
Learning ColdFusion 8: CFImage Part I - Reading And Writing Images
Hi Ben, Great article. I've been looking around to see if ColdFusion image engine can programatically create the following "wrap around" effect: http://www.creativepro.com/article/photoshop-s-she ... read »
Nov 20, 2009 at 5:35 PM
Maintaining ColdFusion Sessions Across SMS Text Message Requests Without Cookies
@Dave: I talked to Gert he suggested: <cfhttp method="get" url="http://{some cf website}" result="stuff" addtoken="yes" /> Note the addition of cfhttp attribute addtoken. That should persist y ... read »
Nov 20, 2009 at 5:23 PM
Maintaining ColdFusion Sessions Across SMS Text Message Requests Without Cookies
@Todd, Ahh, gotcha, yeah that makes sense. ... read »
Nov 20, 2009 at 5:17 PM
Maintaining ColdFusion Sessions Across SMS Text Message Requests Without Cookies
Ben, sorry if I didn't make this clear. You can make it work like that if you want, just put <cfset session.foo = 1> (and <cfset application.foo = 1>) in your OnRequestStart() and it reve ... read »