I'm not sure why you refer to XHTML as the successor to WML. WML was designed to work with WAP in very low bandwidth applications with minimal displays. XHTML on the other hand is simply targeted as the replacement for HTML 4.x. Its simply HTML 4.x which has been regularized to conform to XML syntax conventions. Most existing browsers more-or-less tolerate XHTML already (though they don't seem to implement some of the more XML-ish features...).
I certainly wouldn't consider XHTML as suitable for use with a cell phone for example. XML IN GENERAL when combined with CSS2/3 might be a different story at some point, but I don't think handheld devices generally have the level of support for CSS that would be required at this point, though honestly I have only done simple applications and its a market with a pretty wide variety of stuff... On Thursday 24 July 2003 10:17 am, Mark Cance wrote: > Hi, > I�m trying to knock together a quick WAP version of our web site. > > I�ve created the relevant style sheets and all would seem to be working as > planned behind the scenes. However whenever I let AxKit parse or produce > wml, my wap browser complains that the retrieved file is not wml. > > If I take a copy of the source and remove the AddHandler for .wml in my > AxKit conf. the wml works fine. I realise this has something to do with the > headers of the file but am not sure how to fix. Any help would be > appreciated. > > I�m also mulling over the use of wml vs. its successor xhtml, and the > implementation of a handler that can detect a mobile browsers capabilities. > Ideally I�d like to be able to serve xhtml over wml when a browser allows. > It would be great to hear any thoughts from anybody who�d come across a > similar problem. > > Best, > Mark. -- Giant Electronic Brain Internet/E-Commerce Consulting Services --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
