Per Jessen wrote:
I don't use any of them, but I thought even IE6 was able to deal with
xml.
What happens is IE6 (and I believe IE7) asks the user what application
they want to open the file with if it receives an xml+xhtml header.
IE does parse xhtml but only if sent with an incorrect ht
Michael A. Peters wrote:
> Per Jessen wrote:
>> Michael A. Peters wrote:
>>
>> [anip]
>>> and you can use DOMDocument to completely
>>> construct the page before sending it to the browser - allowing you
>>> to translate xhtml to html for browsers that don't properly support
>>> xhtml+xml.
>>
>>
Per Jessen wrote:
Michael A. Peters wrote:
[anip]
and you can use DOMDocument to completely
construct the page before sending it to the browser - allowing you to
translate xhtml to html for browsers that don't properly support
xhtml+xml.
I suspect you meant "translate xml to html"? I publish
Michael A. Peters wrote:
[anip]
> and you can use DOMDocument to completely
> construct the page before sending it to the browser - allowing you to
> translate xhtml to html for browsers that don't properly support
> xhtml+xml.
I suspect you meant "translate xml to html"? I publish everything in
Paul M Foster wrote:
On Mon, Feb 23, 2009 at 01:39:51PM -0800, Daevid Vincent wrote:
http://startuplessonslearned.blogspot.com/2009/01/why-php-won.html
I *like* the way this guy thinks.
Paul
It was a decent page.
Point #2 though - you can use mod_rewrite to do wonders with respect to
ur
On Mon, Feb 23, 2009 at 01:39:51PM -0800, Daevid Vincent wrote:
> http://startuplessonslearned.blogspot.com/2009/01/why-php-won.html
>
I *like* the way this guy thinks.
Paul
--
Paul M. Foster
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.p
6 matches
Mail list logo
