Hi Yusuf, Thanks for your response. It turns out it was because the tick symbol isn't part of the character entity set in the HTML4 spec, and so it all came down to whether the individual machine contained a font set with the corresponding glyph. There are only a couple of fonts that have that tick glyph (one of which is Arial Unicode MS), and it turns out the machines that displayed the character correctly had the full set for that font installed and the ones that didn't display it correctly only had a subset installed. In the end we went for a Wingdings tick to get around the problem. Cheers, Chris.