mirror of
https://github.com/ezyang/htmlpurifier.git
synced 2024-12-22 16:31:53 +00:00
+ Well Supported
git-svn-id: http://htmlpurifier.org/svnroot/htmlpurifier/trunk@652 48356398-32a2-884e-a903-53898d9a118a
This commit is contained in:
parent
1cce367950
commit
c705e17a58
@ -587,8 +587,24 @@ instead. And, of course, you can't use this method for GET requests.</p>
|
|||||||
|
|
||||||
<h3 id="whyutf8-support">Well supported</h3>
|
<h3 id="whyutf8-support">Well supported</h3>
|
||||||
|
|
||||||
|
<p>Almost every modern browser in the wild today has full UTF-8 and Unicode
|
||||||
|
support: the number of troublesome cases can be counted with the
|
||||||
|
fingers of one hand, and these browsers usually have trouble with
|
||||||
|
other character encodings too. Problems users usually encounter stem
|
||||||
|
from the lack of appropriate fonts to display the characters (once
|
||||||
|
again, this applies to all character encodings and HTML entities) or
|
||||||
|
Internet Explorer's lack of intelligent font picking (which can be
|
||||||
|
worked around).</p>
|
||||||
|
|
||||||
|
<p>We will go into more detail about how to deal with edge cases in
|
||||||
|
the browser world in the Migration section, but rest assured that
|
||||||
|
converting to UTF-8, if done correctly, will not result in users
|
||||||
|
hounding you about broken pages.</p>
|
||||||
|
|
||||||
<h3 id="whyutf8-htmlpurifier">HTML Purifier</h3>
|
<h3 id="whyutf8-htmlpurifier">HTML Purifier</h3>
|
||||||
|
|
||||||
|
<p>And finally, we get to HTML Purifier.</p>
|
||||||
|
|
||||||
<h2 id="migrate">Migrate to UTF-8</h2>
|
<h2 id="migrate">Migrate to UTF-8</h2>
|
||||||
|
|
||||||
<h3 id="migrate-editor">Text editor</h3>
|
<h3 id="migrate-editor">Text editor</h3>
|
||||||
|
Loading…
Reference in New Issue
Block a user