cvs: phpdoc /en/faq using.xml

philip Tue Dec 11 16:40:44 2001 EDT Modified files: /phpdoc/en/faq using.xml Log: Update #7 Index: phpdoc/en/faq/using.xml diff -u phpdoc/en/faq/using.xml:1.11 phpdoc/en/faq/using.xml:1.12 --- phpdoc/en/faq/using.xml:1.11 Sat Nov 10 16:49:29 2001 +++ phpdoc/en/faq/using.xml Tue Dec 11 16:40:43 2001 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="iso-8859-1"?> -<!-- $Revision: 1.11 $ --> +<!-- $Revision: 1.12 $ --> <chapter id="faq.using"> <title>Using PHP</title> <titleabbrev>Using PHP</titleabbrev> @@ -169,19 +169,21 @@ </question> <answer> <para> - Very good question! ;) This is a tricky little issue and it has come up - twice in the past month as of this writing. Both times I ended up - spending a good 20 minutes trying to figure out what the heck was going - on. The answer is that both IE and Lynx ignore any NULs - (<literal>\0</literal>) in the HTML stream. Netscape does not. - The best way to check for this is to compile the command-line version - of PHP (also known as the CGI version) and run your script from the - command line and pipe it through 'od -c' and look for any - <literal>\0</literal> characters. (If you are on Windows you need to - find an editor or some other program that lets you look at binary files) - When Netscape sees a NUL in a file it will typically not output - anything else on that line whereas both IE and Lynx will. If this - issue has bitten you, congratulations! You are not alone. + Netscape is more strict regarding html tags (such as tables) then + IE. Running your html output through a html validator, such as + <ulink url="&faqurl.w3.validator;">validator.w3.org</ulink>, might + be helpful. For example, a missing &lt;/table&gt; might cause this. + </para> + <para> + Also, both IE and Lynx ignore any NULs (<literal>\0</literal>) in + the HTML stream, Netscape does not. The best way to check for this is + to compile the <link linkend="commandline">command line</link> version of + PHP (also known as the CGI version) and run your script from the + command line. In *nix, pipe it through <literal>od -c</literal> and look + for any <literal>\0</literal> characters. If you are on Windows you need + to find an editor or some other program that lets you look at binary files. + When Netscape sees a NUL in a file it will typically not output anything + else on that line whereas both IE and Lynx will. </para> </answer> </qandaentry>