Author |
xhtml wap sites |
craigjackson001 Joined: Nov 30, 2003 Posts: 48 PM, WWW
|
I have created an xhtml internet site at www.craigjackson001.pwp.blueyonder.co.uk/index.xhtml everything works fine in the SE wap emulator but when I try to view the site on my T610 I get nothing not even an error message.
can anybody please help me please as I want this site up and running soon. Thankx in advance
Craig Jackson |
|
stuartdb87 Joined: Nov 18, 2003 Posts: 468 From: Bolton, UK PM, WWW
|
Try e-mailing SonyEricsson and they might give you advice on uploading it.
This message was posted from a T610 |
mwright Joined: Jun 21, 2003 Posts: > 500 From: UK PM |
On my T610 - it just displays the source of the page!!
You might try naming the pages .html instead of .xhtml? |
weliem Joined: Mar 02, 2003 Posts: 10 PM |
Hi,
The 'xhtml' page that you have made is actually not XHTML. In fact, it should be 'xhtml mobile profile' rather than any xhtml. Your server must also be configured to return 'application/xhtml+xml' as the mimetype of the page. Here is a very short page that has the correct DTD in it.
Good luck!
Martijn
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//WAPFORUM//DTD XHTML Mobile 1.0//EN"
"http://www.wapforum.org/DTD/xhtml-mobile10.dtd" >
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<title>Test</title>
</head>
<body>
<h3>Test</h3>
</body>
</html> |
Dj Boyi Joined: Oct 05, 2002 Posts: > 500 From: Liberty City PM |
I get a pagefull of coding,orangeman is ur man to help u out tho :-)
This message was posted from a T610 |
superunknown Joined: Nov 21, 2002 Posts: > 500 PM |
xhtml is strict when it comes to character.
This message was posted from a T610 |
wapchimp Joined: Jun 09, 2002 Posts: > 500 From: Land of the chimps PM, WWW
|
U can use html tags. the index.xhtml may be the cause with the mimetype. Blueyonder doesnt have xhtml as preset file type. Look at my source code for my xhtml pwp site
This message was posted from a T610 |
craigjackson001 Joined: Nov 30, 2003 Posts: 48 PM, WWW
|
Thanks renaming the xhtml to html fixed the problem |
|