Hi.
This thread is bit old, but I've just gotten back on to this.
I implemented the mapping you showed here, and it works enough to allow Tap to
serve the doctype to the user, and not raise any exceptions. But the entities
still don't work. In fact, character references don't work either: char
Ok, this is a touch hackish, but... you can map the HTML definitions
to their corresponding xml definitions. It's hackish because, a)
it's contributing to an "internal" service, and b) You'll still have
to write valid xml templates. But you'll be able to use the 4.01
DTD, and that is the
It's most definitely hackish!!! I'm considering it completely temporary.
But, I can't currently specify HTML 4 strict: Tapestry runs the XML DTD parser
which errors on that DTD. I want to use this DTD (not XHTML).
Actually I just stumbled over the UTF-8 encoding entry in the Wiki, so that is
an
If you specify a doctype in your templates (like XHTML 1.0 Strict), you can
use entities like ©
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
http://www.w3.org/1999/xhtml"; xmlns:t="
http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";>
Copyright © Me
On 6/8/07, Steven Coco <[EMA
I just implemented a set of properties in WEB-INF/Application.properties. They
look like this:
# HTML entities:
entity.copy: ©
entity.trade: ™
...
Now in templates I can "use" them like so:
Such is life.
Ciao.
-Steven Coco.
---
