<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.0.10">
You can use CDATA blocks to prevent interpretation of XML special characters such as "<", ">" and "&" (this avoids having to explictly encode these characters). When outputting the stuff you would have to prevent the CDATA markup itself from being written out, but just its content. That way the output would contain the required markup.<BR>
A better approach would be to use "HTML Tidy" to convert "standard HTML" (SGML) to XHTML (XML) before you use it.<BR>
See <A HREF="http://tidy.sourceforge.net/">http://tidy.sourceforge.net/</A>.<BR>
On Thu, 2004-04-22 at 11:09, Eric VERGNAUD wrote:
<PRE><FONT COLOR="#737373"><I>le 22/04/04 11:41, Phil Weighill-Smith à firstname.lastname@example.org a
> Can you not write XHTML instead?
Believe me, I would if I could. But I'm not the writer. The HTML is written
by end users, stored in my app, and sent to other apps on which I have no
> A common way around browser
> incompatibility between HTML (SGML) and XHTML (XML) is to ensure that
> there is a space before the "/>", e.g. "<br>" is written as "<br />".
> This works in most browsers.
But I also need to support <b>Hello</b>, where both tags must be part of the
Currently I convert the "<" to "&lt;" and ">" to "&gt;". I copied this
method from Adobe's xmp format, but I find it rather heavy, and I don't know
if it's official.
To control your jdom-interest membership:</FONT>
<PRE><TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
Phil Weighill-Smith <<A HREF="mailto:email@example.com"><U>firstname.lastname@example.org</U></A>><BR>