blocks|key|352202|text|根据我收到的评论，我对此进行了更深入的研究。目前看来，的最佳实践是放弃使用HTML，而使用实际的UTF8字符代替。列出的原因如下：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|352203|对于那些理解字符含义并知道如何键入字符的人来说，|352204|UTF-8编码更易于阅读和编辑。对于不理解字符的人来说，|ordered-list-item|352205|UTF-8编码与HTML+8编码一样难以理解，但它们的优点是可以呈现为特殊字符，而不是难以理解的十进制或十六进制编码。|352206|352207|只要页面的编码正确设置为UTF-8，就应该使用实际的字符，而不是HTML实体。我读了几篇关于这个主题的文档，但最有帮助的是：|352208|352209|UTF-8:+The+Secret+of+Character+Encoding|unordered-list-item|352210|Wikipedia+Special+Characters+Help|352211|352212|摘自UTF-8:字符编码的秘密文章：|352213|对于最初使用|352214|+-8859-1的应用程序来说，used是一个很好的案例，但当它变得太麻烦而无法支持外语时，就切换到了UTF8。出于用户友好性和可搜索性的考虑，机器人现在实际上将遍历文章并将字符实体转换为相应的真实角色。|blockquote|352215|352216|352217|那篇文章还给出了一个关于中文编码的很好的例子。这是一个为了懒惰而缩写的例子：|352218|UTF-8:|352219|這兩個字是甚麼意思|CODE|352220|超文本标记语言实体|352221|&#36889;&#20841;&#20491;&#23383;&#26159;&#29978;&#40636;&#24847;&#24605;|352222|UTF-8和HTML实体编码对我来说都没有意义，但是至少可以将UTF-8编码识别为一种外语，并且它可以在编辑框中正确呈现。本文接着介绍了以下关于HTML实体编码版本的内容：|352223|352224|对于我们这些真正知道字符实体是什么的人来说是非常不方便的，对于不知道的可怜的用户来说是完全不能理解的！即使是像θ这样稍微更加用户友好、“易懂”的字符实体，也会让那些对学习HTML不感兴趣的用户感到挠头。另一方面，如果他们在编辑框中看到θ，他们就会知道这是一个特殊字符，并对其进行相应处理，即使他们自己不知道如何书写该字符。|352225|352226|352227|正如其他人所指出的，对于保留的XML字符(与号、小于、大于)，仍然必须使用HTML实体。|352228|entityMap|0|LINK|mutability|MUTABLE|url|http://htmlpurifier.org/docs/enduser-utf8.html|1|http://meta.wikimedia.org/wiki/Help:Special_characters^0|R|T|0|0|0|0|0|0|0|0|13|0|0|0|X|1|0|0|0|0|20|U|0|0|0|0|12|0|0|6|0|0|9|0|9|0|0|9|0|0|20|0|20|0|0|2E|0|0|0|4H|0|0|0|0|18|0^^$0|@$1|2|3|4|5|6|7|1Z|8|@$9|20|A|21|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|22|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|23|8|@]|D|@]|E|$]]|$1|K|3|L|5|J|7|24|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|25|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|26|8|@]|D|@]|E|$]]|$1|P|3|-4|5|6|7|27|8|@]|D|@]|E|$]]|$1|Q|3|R|5|S|7|28|8|@]|D|@$9|29|A|2A|1|2B]]|E|$]]|$1|T|3|U|5|S|7|2C|8|@]|D|@$9|2D|A|2E|1|2F]]|E|$]]|$1|V|3|-4|5|6|7|2G|8|@]|D|@]|E|$]]|$1|W|3|X|5|6|7|2H|8|@]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|2I|8|@]|D|@]|E|$]]|$1|10|3|11|5|12|7|2J|8|@$9|2K|A|2L|B|C]]|D|@]|E|$]]|$1|13|3|-4|5|6|7|2M|8|@]|D|@]|E|$]]|$1|14|3|-4|5|6|7|2N|8|@]|D|@]|E|$]]|$1|15|3|16|5|6|7|2O|8|@$9|2P|A|2Q|B|C]]|D|@]|E|$]]|$1|17|3|18|5|6|7|2R|8|@$9|2S|A|2T|B|C]]|D|@]|E|$]]|$1|19|3|1A|5|6|7|2U|8|@$9|2V|A|2W|B|C]|$9|2X|A|2Y|B|1B]]|D|@]|E|$]]|$1|1C|3|1D|5|6|7|2Z|8|@$9|30|A|31|B|C]]|D|@]|E|$]]|$1|1E|3|1F|5|6|7|32|8|@$9|33|A|34|B|C]|$9|35|A|36|B|1B]]|D|@]|E|$]]|$1|1G|3|1H|5|6|7|37|8|@$9|38|A|39|B|C]]|D|@]|E|$]]|$1|1I|3|-4|5|6|7|3A|8|@]|D|@]|E|$]]|$1|1J|3|1K|5|12|7|3B|8|@$9|3C|A|3D|B|C]]|D|@]|E|$]]|$1|1L|3|-4|5|6|7|3E|8|@]|D|@]|E|$]]|$1|1M|3|-4|5|6|7|3F|8|@]|D|@]|E|$]]|$1|1N|3|1O|5|6|7|3G|8|@$9|3H|A|3I|B|C]]|D|@]|E|$]]|$1|1P|3|-4|5|6|7|3J|8|@]|D|@]|E|$]]]|1Q|$1R|$5|1S|1T|1U|E|$1V|1W]]|1X|$5|1S|1T|1U|E|$1V|1Y]]]]

Based on the comments I have received, I looked into this a little further. It seems that currently the best practice is to forgo using HTML entities and use the actual UTF-8 character instead. The reasons listed are as follows:

<ol>
<li>UTF-8 encodings are easier to read and edit for those who understand what the character means and know how to type it.</li>
<li>UTF-8 encodings are just as unintelligible as HTML entity encodings for those who don't understand them, but they have the advantage of rendering as special characters rather than hard to understand decimal or hex encodings.</li>
</ol>

As long as your page's encoding is properly set to UTF-8, you should use the actual character instead of an HTML entity. I read several documents about this topic, but the most helpful were:

<ul>
<li><a href="http://htmlpurifier.org/docs/enduser-utf8.html" rel="noreferrer">UTF-8: The Secret of Character Encoding</a></li>
<li><a href="http://meta.wikimedia.org/wiki/Help:Special_characters" rel="noreferrer">Wikipedia Special Characters Help</a></li>
</ul>

From the UTF-8: The Secret of Character Encoding article:

<blockquote>
 Wikipedia is a great case study for an
 application that originally used
 ISO-8859-1 but switched to UTF-8 when
 it became far too cumbersome to support
 foreign languages. Bots will now
 actually go through articles and
 convert character entities to their
 corresponding real characters for the
 sake of user-friendliness and
 searchability.
</blockquote>

That article also gives a nice example involving Chinese encoding. Here is the abbreviated example for the sake of laziness:

UTF-8:

<code>這兩個字是甚麼意思</code>

HTML Entities:

<code>&amp;#36889;&amp;#20841;&amp;#20491;&amp;#23383;&amp;#26159;&amp;#29978;&amp;#40636;&amp;#24847;&amp;#24605;</code>

The UTF-8 and HTML entity encodings are both meaningless to me, but at least the UTF-8 encoding is recognizable as a foreign language, and it will render properly in an edit box. The article goes on to say the following about the HTML entity-encoded version:

<blockquote>
 Extremely inconvenient for those of us
 who actually know what character
 entities are, totally unintelligible
 to poor users who don't! Even the
 slightly more user-friendly,
 "intelligible" character entities like
 &amp;theta; will leave users who are
 uninterested in learning HTML
 scratching their heads. On the other
 hand, if they see θ in an edit box,
 they'll know that it's a special
 character, and treat it accordingly,
 even if they don't know how to write
 that character themselves.
</blockquote>

As others have noted, you still have to use HTML entities for reserved XML characters (ampersand, less-than, greater-than).

blocks|key|356005|text|如果你的页面被正确地编码为utf-8，你应该不需要html实体，只需要直接使用你想要的字符。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|356006|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If your pages are correctly encoded in utf-8 you should have no need for html entities, just use the characters you want directly.

blocks|key|3347349|text|实体可能会为你带来一些与那些不能正确理解编码的脑死亡客户端的兼容性。我不相信这包括任何当前的浏览器，但你永远不会知道其他类型的程序可能会击中你。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3347350|不过，更有用的是，HTML实体可以保护您免受自己的错误的影响:如果您在服务器上错误配置了某些内容，并且最终使用HTTP头和META标记提供一个页面，说明它是ISO-8859-1和UTF-8，那么至少您的-es将始终有效。|offset|length|style|CODE|3347351|entityMap^0|0|1P|4|26|A|2H|5|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]|$D|N|E|O|F|G]|$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|I|$]]

Entities may buy you some compatibility with brain-dead clients that don't understand encodings correctly. I don't believe that includes any current browsers, but you never know what other kinds of programs might be hitting you up.

More useful, though, is that HTML entities protect you from your own errors: if you misconfigure something on the server and you end up serving a page with an HTTP header that says it's <code>ISO-8859-1</code> and a <code>META</code> tag that says it's <code>UTF-8</code>, at least your &amp;mdash;es will always work.

blocks|key|353477|text|如果您的编辑器支持Unicode，则通常不需要使用HTML字符实体。在以下情况下，实体可能非常有用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|353478|353479|您的键盘不支持您需要键入的字符。例如，许多键盘没有破折号或版权符号。|unordered-list-item|353480|你的编辑器不支持Unicode+(几年前很常见，但今天可能不支持)。|353481|你想在源代码中明确说明正在发生的事情。例如，&nbsp;代码比相应的空白字符更清晰。|offset|length|style|CODE|353482|您需要转义<、&或HTML等特殊字符|353483|353484|entityMap^0|0|0|0|0|M|6|0|5|1|7|1|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|V|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|W|8|@$J|X|K|Y|L|M]]|9|@]|A|$]]|$1|N|3|O|5|E|7|Z|8|@$J|10|K|11|L|M]|$J|12|K|13|L|M]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|R|$]]

You don't generally need to use HTML character entities if your editor supports Unicode. Entities can be useful when:

<ul>
<li>Your keyboard does not support the character you need to type. For example, many keyboards do not have em-dash or the copyright symbol.</li>
<li>Your editor does not support Unicode (very common some years ago, but probably not today).</li>
<li>You want to make it explicit in the source what is happening. For example, the <code>&amp;nbsp;</code> code is clearer than the corresponding white space character.</li>
<li>You need to escape HTML special characters like <code>&lt;</code>, <code>&amp;</code>, or <code>"</code>.</li>
</ul>

blocks|key|3347375|text|对于视觉上容易混淆的字符，我不会使用UTF-8。例如，很难区分emdash和减号，特别是不间断空格和空格。对于这些字符，一定要使用实体。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3347376|对于视觉上容易理解的字符(例如上面的中文示例)，如果愿意，可以使用UTF-8。|3347377|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I would not use UTF-8 for characters that are easily confused visually. For example, it is difficult to distinguish an emdash from a minus, or especially a non-breaking space from a space. For these characters, definitely use entities.

For characters that are easily understood visually (such as the chinese examples above), go ahead and use UTF-8 if you like.

blocks|key|353501|text|之前的所有答案对我来说都是有意义的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|353502|此外:这主要取决于您打算使用的编辑器和文档语言。作为编辑器的最低要求是它支持文档语言。这意味着，如果你的文本是日语的，要小心使用不显示它们的编辑器(即文档本身没有实体)。如果它是英文的，你甚至可以使用一个旧的类似vim的编辑器，只对相对较少的©和朋友使用实体。当然：>+for+>和其他HTML-specials仍然需要转义。但即使使用其他拉丁语-1语言(德语、法语等)写作是一种痛苦，你知道在哪里……|353503|此外，我个人为看不见的字符和那些看起来与标准ascii相似的字符编写实体，因此很容易混淆。例如，有u1173+(在某些字符集中看起来像破折号)或u1175，它看起来像竖线。在任何情况下，我都会对这些内容使用实体。|353504|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

All of the previous answers make sense to me.

In addition: It mostly depends on the editor you intent to use and the document language. As a minimum requirement for the editor is that it supports the document language. That means, that if your text is in japanese, beware of using an editor which does not show them (i.e. no entities for the document itself). If its english, you can even use an old vim-like editor and use entities only for the relative seldom &amp;copy; and friends.
Of course: &amp;gt; for > and other HTML-specials still need escapes.
But even with the other latin-1 languages (german, french etc.) writing &auml; is a pain in you know where...

In addition, I personally write entities for invisible characters and those which are looking similar to standard-ascii and are therefore easily confused. For example, there is u1173 (looking like a dash in some charsets) or u1175, which looks like the vertical bar. I'd use entities for those in any case.

blocks|key|3347448|text|当您想要生成将(动态地)包含到具有(几种)不同编码的页面中的内容时，HTML实体非常有用。例如，我们有包含在ISO-8859-1和UTF-8编码网页中的白标内容...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3347449|如果从UTF-8到UTF-8的字符集转换不是那么糟糕(您总是被一些不能正确转换的字符和工具绊倒)，那么对UTF-8进行标准化将是可行的。|3347450|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

HTML entities are useful when you want to generate content that is going to be included (dynamically) into pages with (several) different encodings. For example, we have white label content that is included both into ISO-8859-1 and UTF-8 encoded web pages...

If character set conversion from/to UTF-8 wasn't such a big unreliable mess (you always stumble over some characters and some tools that don't convert properly), standardizing on UTF-8 would be the way to go.

blocks|key|3134716|text|就我个人而言，我使用utf-8做所有事情，因为很长一段时间以来，在html页面中，您总是需要将与号(+&+)、大于(>)和小于(<)字符转换为它们等效的实体&、>和<|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3134717|此外，如果您打算使用utf-8文本进行一些编程，有几件事需要注意。|3134718|当使用实体时，|3134719|XML需要一些额外的行来验证。|unordered-list-item|3134720|一些库与utf-8不能很好地配合。例如，在一些Linux发行版本中，PHP在其正则表达式库中放弃了对utf-8的完全支持。|3134721|限制使用html实体的文本中的字符数变得更加困难，因为单个实体使用了许多字符。此外，总是存在将实体切成两半的风险。|3134722|3134723|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|H|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|H|7|U|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

Personally I do everything in utf-8 since a long time, however, in an html page, you always need to convert ampersands (&amp;), greater than (&gt;) and lesser then (&lt;) characters to their equivalent entities, &amp;amp;, &amp;gt; and &amp;lt;

Also, if you intend on doing some programming using utf-8 text, there are a few thing to watch for.

<ul>
<li>XML needs some extra lines to validate when using entities.</li>
<li>Some libraries do not play along nice with utf-8. For instance, PHP in some Linux distributions dropped full support for utf-8 in their regular expression libraries.</li>
<li>It is harder to limit the number of characters in a text that uses html entities, because a single entity uses many characters. Also there's always the risk of cutting the entity in half.</li>
</ul>

This has been confusing me for some time. With the advent of UTF-8 as the de-facto standard in web development I'm not sure in which situations I'm supposed to use the HTML entities and for which ones should I just use the UTF-8 character. For example,

<ul>
<li>em dash (–, <code>&amp;emdash;</code>)</li>
<li>ampersand (&amp;, <code>&amp;amp;</code>)</li>
<li>3/4 fraction (¾, <code>&amp;frac34;</code>)</li>
</ul>

Please do shed light on this issue. It will be appreciated.

When should one use HTML entities?

服务器

Linux

这让我困惑了一段时间。随着UTF-8作为web开发的事实标准的出现，我不确定在哪些情况下应该使用HTML实体，以及在哪些情况下应该只使用UTF-8字符。例如,分数em破折号( &frac34;)，&emdash;)ampersand (&，&amp;)3/4 -请务必阐明这个问题。我会很感激的。

问什么时候应该使用HTML实体？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问什么时候应该使用HTML实体？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问什么时候应该使用HTML实体？
EN