<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
xhtml is nothing more than html that uses all lower case and can be
validated as xml.<br>
(i.e. tags have to be closed and attributes have to have values and the
values must be quoted).<br>
<br>
It does mean that the file is much more parseable and can be
transformed with xslt, but as was<br>
noted earlier, the document needs to be marked up structurally in a
consistent manner.<br>
<br>
If it is not marked up well then all bets are off.<br>
<br>
David Blue (Mailing List Addy) wrote:
<blockquote cite="mid200411261240.46145.davidslists@gmx.net" type="cite">
<pre wrap="">On Friday 26 November 2004 09:10 am, <a class="moz-txt-link-abbreviated" href="mailto:chrislit@crosswire.org">chrislit@crosswire.org</a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">There is no "easy" way to convert HTML to GBF, ThML, or OSIS in a useful
and meaningful way. HTML is presentational markup. GBF & OSIS deal with
structural markup. ThML mixes the two, but to use it for module import
would require some structural markup.
It is impossible to generalize a method for converting HTML to any
structural markup language.
</pre>
</blockquote>
<pre wrap=""><!---->
What about XHTML? It seems to be more focused on structural and doing
presenation in style sheets.
_______________________________________________
sword-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
</pre>
</blockquote>
</body>
</html>