js wrote: > The problem is Safari 1.3 is processing the page as an XML document, > even though, just as you pointed out, it's really a XHTML. > The server seems returning the right HTTP header, > "Content-Type: application/xhtml+xml; charset=utf-8", > so I think it's actually a Safari's problem.
This may be related to http://trac.macosforge.org/projects/macports/ticket/14062 Rainer _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
