XHTML and PHP?

J

John Salerno

I got the following error message when I tried to use a PHP include() in
my XHTML file:

------
PHP Parse error: syntax error, unexpected T_STRING in
C:\Domains\johnjsal.com\wwwroot\g_camera_move.php on line 1
------

The top of my html file is:

-------
<?xml version="1.0" encoding="utf-8"?>
<!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" xml:lang="en" lang="en">
<head>........
-------

Is something in this heading causing a problem? I removed the first line
but still got the same message. Then I created a new HTML page with no
heading at all (I started with the <html> tag) and the include() worked.

So obviously something about my heading is causing problems, but I don't
understand what it is.
 
T

Toby Inkster

John said:
<?xml version="1.0" encoding="utf-8"?>

Replace this with:

<?= '<?xml version="1.0" encoding="utf-8"?>'."\n" ?>

(or remove it altogether -- it's optional, and pushes IE/win into quirks
mode)
 
J

John Salerno

Toby said:
Replace this with:

<?= '<?xml version="1.0" encoding="utf-8"?>'."\n" ?>

(or remove it altogether -- it's optional, and pushes IE/win into quirks
mode)

Well, I could have sworn I tried this already and it didn't work, but
now it does. Thanks!

Btw, what does that first option do, with <?= ?> ?
 
M

Mike Massonnet

Toby said:
Replace this with:

<?= '<?xml version="1.0" encoding="utf-8"?>'."\n" ?>

(or remove it altogether -- it's optional, and pushes IE/win into quirks
mode)

it is also optional when using UTF-8 or UTF-16 encoding.
 
A

Alan J. Flavell

Or indeed ASCII, as that is a subset of UTF-8.

It's quite amusing really: if you send content which is strictly
us-ascii, undeclared, over HTTP, then RFC2616 says it should be
assumed to be iso-8859-1, while XML can assume it's utf-8, and neither
of them are actually wrong :-}

This is not really advisable, though. Depending on the contents of
the ASCII data stream, MSIE might unilaterally decide that it's utf-7,
and CERT CA-2000-02 warns about cross-site scripting security flaws
which can be exploited. An appropriate explict encoding should always
be advertised, as the CERT alert recommends.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,744
Messages
2,569,484
Members
44,903
Latest member
orderPeak8CBDGummies

Latest Threads

Top