http://www.kriesi.at/support/tags/w3-validator Support Forum - Tag: w3 validator - Recent Posts en-US Thu, 23 May 2013 22:42:45 +0000 http://bbpress.org/?v=1.0.2 q http://www.kriesi.at/support/search.php http://www.kriesi.at/support/topic/validatorw3org-error#post-28407 Sun, 02 Oct 2011 15:47:21 +0000 Dude 28407@http://www.kriesi.at/support/ <p>Glad that you found the "bad boy" :) </p> http://www.kriesi.at/support/topic/validatorw3org-error#post-28402 Sun, 02 Oct 2011 15:11:14 +0000 brouge 28402@http://www.kriesi.at/support/ <p>hey dude - i found it.<br /> it was the functions.php that had only utf8. all the other files are fine.<br /> maybe because i inserted a few lines from the wordpress backend.<br /> it was enough to convert the functions.php to "utf8 without BOM". now everything is strict without a warning.</p> <p>thanks and best regards </p> http://www.kriesi.at/support/topic/validatorw3org-error#post-28400 Sun, 02 Oct 2011 14:01:22 +0000 Dude 28400@http://www.kriesi.at/support/ <p>Try to save header.php, footer.php and sidebar.php with "iso8859-1" - maybe one of them effects the coding too. If you're using a plugin/shortcode on this page check if its code causes the warning. </p> http://www.kriesi.at/support/topic/validatorw3org-error#post-28394 Sun, 02 Oct 2011 12:05:55 +0000 brouge 28394@http://www.kriesi.at/support/ <p>hey dude - that's a nice editor!<br /> where do i exactly change the php to iso western. i tried to go to "kodierung"-"zeichensatz"-"westeuropäisch"<br /> and took "iso8859-1"</p> <p>i replaced the template_contact.php but revalidating still brings up the warning.<br /> regards </p> http://www.kriesi.at/support/topic/validatorw3org-error#post-28393 Sun, 02 Oct 2011 11:22:58 +0000 Dude 28393@http://www.kriesi.at/support/ <p>You can use tools like notepad++ to save your php files in standard iso format (in your case template_contact.php is saved as utf-8 file instead iso western) - this will resolve the error. However it won't effect search engines, etc. anyway. </p> http://www.kriesi.at/support/topic/validatorw3org-error#post-28392 Sun, 02 Oct 2011 11:16:31 +0000 brouge 28392@http://www.kriesi.at/support/ <p>cool i don't know why but now the error is gone!<br /> how do i fix this warning at <a href="http://www.mathemitnullplan.de/impressum" rel="nofollow">http://www.mathemitnullplan.de/impressum</a></p> <pre><code>Byte-Order Mark found in UTF-8 File. The Unicode Byte-Order Mark (BOM) in UTF-8 encoded files is known to cause problems for some text editors and older browsers. You may want to consider avoiding its use until it is better supported.</code></pre> <p>best regards </p> http://www.kriesi.at/support/topic/validatorw3org-error#post-28342 Sat, 01 Oct 2011 23:18:11 +0000 Chris Beard 28342@http://www.kriesi.at/support/ <p>Hi,<br /> please see <a href="http://validator.w3.org/check?uri=http%3A%2F%2Fwww.kriesi.at%2Fdemos%2Fdisplay%2F&amp;charset=%28detect+automatically%29&amp;doctype=Inline&amp;group=0">this</a>. No errors come up. </p> http://www.kriesi.at/support/topic/validatorw3org-error#post-28340 Sat, 01 Oct 2011 20:46:41 +0000 brouge 28340@http://www.kriesi.at/support/ <p>hey i checked the <a href="http://www.kriesi.at/demos/display/" rel="nofollow">http://www.kriesi.at/demos/display/</a> theme and i get 1 error saying</p> <pre><code>DOCTYPE Override in effect! The detected DOCTYPE Declaration &quot;&lt;!DOCTYPE html PUBLIC &quot;-//W3C//DTD XHTML 1.0 Strict//EN&quot; &quot;http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd&quot;&gt;&quot; has been suppressed and the DOCTYPE for &quot;XHTML 1.0 Strict&quot; inserted instead, but even if no errors are shown below the document will not be Valid until you update it to reflect this new DOCTYPE.</code></pre> <p>and<br /> <pre><code>The document located at &lt;http://www.kriesi.at/demos/display/&gt; was tentatively checked as XHTML 1.0 Strict. This means that with the use of some fallback or override mechanism, we successfully performed a formal validation of it. In other words, the document would validate as XHTML 1.0 Strict if you changed the markup to match the changes we have performed automatically, but it will not be valid until you make these changes.</code></pre> <p>can you change something to avoid this error? </p>