On Sun, 26 Sep 1999, Torsten Neuer wrote:
> - SGMLEntities::translate()
> Will return an ampersand instead of a space for unrecognized en-
> tities, thus leaving single ampersand characters "as is" (which
> will affect document text as well!).
>
> - SGMLEntities::translateAndUpdate()
> Will restore the text pointer to the character after the ampersand
> for unrecognized entities.
This class is depreciated. If there are similar problems in the 3.2 tree
with HtSGMLCodec, then we need to take care of it.
As for the URL problems, I think we want to update htlib/URLTrans.cc to be
completely compatible with HTML 4.0 and the latest RFCs on URIs.
Personally, I've never been happy with the hack of translate_amp, etc. It
basically works, but it seems like it's the wrong style. Using HtSGMLCodec
(which has a few problems still since it doesn't translate &#nnn;) to
encode into the database and then decode for display seems the Right
Thing, IMHO.
-Geoff Hutchison
Williams Students Online
http://wso.williams.edu/
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
