to summarize from the above indicated email thread and what I've found on the code:
</td> exposes the error.
all in all, given that freemarker only knows how to properly present Strings and Numbers, I wonder if using <td>$
</td> or any other formatting strategy/workaround is not such a common need that whomever uses freemarker has to deal with that.
If so, do we really need to care about wrapping booleans as strings so one can simply use <td>$
When asked Andrea if this behaviour is actually a bug or a feature,.. he didn't need to answer as he had a nice idea: to keep around both the original attribute value and a default string representation, so users can choose between, say,
Waiting for comments from Justin...
Fixed for 1.5.x and 1.6.x, and accordingly updated the documentation for http://docs.codehaus.org/display/GEOSDOC/GetFeatureInfo+templates and http://docs.codehaus.org/display/GEOSDOC/01-Placemark+Templates