[Fwd: [Jscodee-devel] Re: moving the xhtml back to html]

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

forwarding to get into the archive

-------- Original Message --------
Subject: [Jscodee-devel] Re: moving the xhtml back to html
Date: Sun, 19 Jan 2003 10:00:34 -0600
From: Gary Frederick <gar...@js...>
Reply-To: jsc...@li...
Organization: Jefferson Software
To: jsc...@li...
References: <3E2...@js...>

How to convert a page from xhtml to html

Pick a page - On.xhtml

1: convert from xhtml to html
       tidy -ashtml -wrap 128 -indent OnTidy.xhtml >OnTidyHTML.html

2: remove CDATA 'stuff' from around the JavaScript
<![CDATA[
    and
]]>

3: change the following in OnTidyHTML.html
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
    <head profile="http://jscodee.sourceforge.net/jscode/docs/#profile">

to

<html lang="en-US">
    <head>

4: tidy up after your changes
       tidy -wrap 128 -indent -m OnTidyHTML.html

=====
What we are doing.

The program tidy is a great utility for tidying up html. The first step
converts XHTML to html (-ashtml). It also wraps lines and makes sure
it's indented. It saves to OnTidyHTML.html.

Then we remove the CDATA from around the JavaScript. The XHTML version
has that around the JavaScript to 'protect' it. When we converted the
xhtml to html, we did not need it so we removed it.

we changed the file by removing the file's xml and doctype info and by
editing the <html> and <head> tag. We got all the other changes we
needed when we ran tidy.

We ran tidy again to make sure we got valid html. Good ol tidy also adds
the correct DOCTYPE for our html.
    <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

and then we email me the new file and I'll put it on sourceforge. We
will have things set up to do more effeciently soon.

Let me know where the above was not clear and start sending the html
version of the files.

Gary

Gary Frederick wrote:
 > I converted most of our pages to xhtml 1.1. Then I found out that
 > Internet Explorer does not recognize the mime type for xhtml. sigh.
 >
 > Back we go.
 >
 > What happens is when IE gets a page that is XHTML, it asks if you want
 > to download it or view it. When I view it, I get a copy that was
 > downloaded to a temporary file. That messes up any images, the
 > JavaScript and is just not right.
 >
 > Back to HTML.
 >
 > Gary
 >
 > some info:
 >
 >   XHTML 1.1 documents should use application/xhtml+xml.
 >   http://www.w3.org/TR/xhtml-media-types/
 >
 >   Someone's adventures with going to XHTML 1.1 - lots of good stuff
 >   Item 2 about MIME type application/xhtml+xml
 >   http://diveintomark.org/archives/2002/11/21.html
 >
 >   Another that told how he coped with IE.
 >   http://www.petesguide.com/
 >
 >   That pointed to this German site which had the links to translate into
 > English and good info.
 >   http://schneegans.de/tips/apache-xhtml.html
 >
 >   That site pointed to this site that had even more good info. Look at
 > the info about the content negotiation various browser have, the Accept:
 > stuff. AND be sure to look at the site using IE. You have been warned!!!
 > :-) :-) :-)
 >   http://kimihia.org.nz/articles/ieaccept/modify
 >   http://kimihia.org.nz/
 >
 >
 >

-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
Jscodee-devel mailing list
Jsc...@li...
https://lists.sourceforge.net/lists/listinfo/jscodee-devel