On 21 Jul 2005, at 4:43 am, James Cerra wrote:
In an XSLT-based Atom-to-XHTML processor, that is a large cost when
HTML
includes many many many entities. At least, I think so and have
ignored the
problem because I can't think of a good way to solve it.
Yes, but your proposed solution just requires people at the other end
of the chain to do the hard work. A common theme in the design of
Atom is minimizing the amount of work that must be done by publishers
(of which there are many) vs the amount of work done by processing
tools (of which there are few, and which are easier to turn into
common libraries).
Graham
