From 44b988f1f6fcc85838da77d7a7cc780bdcb16b38 Mon Sep 17 00:00:00 2001 From: "Edward Z. Yang" Date: Wed, 24 Jan 2007 03:00:48 +0000 Subject: [PATCH] Fix some editing mistakes. git-svn-id: http://htmlpurifier.org/svnroot/htmlpurifier/trunk@695 48356398-32a2-884e-a903-53898d9a118a --- docs/enduser-utf8.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/enduser-utf8.html b/docs/enduser-utf8.html index cd0dc7ec..12a114c0 100644 --- a/docs/enduser-utf8.html +++ b/docs/enduser-utf8.html @@ -275,7 +275,7 @@ your own php.ini file, ask your support for details. Use:

Non-PHP

-

You may, for whatever reason, may need to set the character encoding +

You may, for whatever reason, need to set the character encoding on non-PHP files, usually plain ol' HTML files. Doing this is more of a hit-or-miss process: depending on the software being used as a webserver and the configuration of that software, certain @@ -386,8 +386,8 @@ processing instructions. They look like:

For XHTML, this processing instruction theoretically overrides the META tag. In reality, this happens only when the -XHTML is actually served as legit XML and not HTML, which is almost -always never due to Internet Explorer's lack of support for +XHTML is actually served as legit XML and not HTML, which is almost always +never due to Internet Explorer's lack of support for application/xhtml+xml (even though doing so is often argued to be good practice).

@@ -398,7 +398,7 @@ for XML files is UTF-8, which often butts heads with more common ISO-8859-1 encoding (you see this in garbled RSS feeds).

In short, if you use XHTML and have gone through the -trouble of adding the XML header, be sure to make sure it jives +trouble of adding the XML header, make sure it jives with your META tags and HTTP headers.

Inside the process