我需要补充飞机吗？
我认为问题很简单，除了基本平面之外，我还需要 Unicode 中的所有其余内容吗？ 其中包括哪些内容以及真正需要的内容吗？ （以及出于什么目的？）
谢谢。
I think the question is pretty simple, do I need all the rest of the stuff in Unicode after the basic plane? What kind of stuff is included and is that really needed? (and for what purposes?)
Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
如果你打算在中国销售任何东西，那么GB 18030标准是强制性的，并且要求字符超出BMP（基本多语言平面）。 该标准是强制执行的，为了在那里销售，您需要通过 GB 18030 认证。
日本和香港也有国家标准，要求使用 BMP 以外的字符。
即使这些标准不像中国标准那样强制执行，支持它们也可能会给你带来一些优势。
所以简单的答案是：你需要那里的一些东西。
=== 2016 ===
那是 7 年前的事了。 现在每个人都在谈论表情符号。 好吧，大多数表情符号都超出了 BMP 范围:-)
If you intend to sell anything in China, then the GB 18030 standard is mandatory, and requires characters beyond BMP (Basic Multilingual Plane). The standard is enforced, and in order to sell there you need to pass a GB 18030 certification.
There also national standards in Japan, and Hong Kong that require characters beyond BMP.
Even if these standards are not enforced like the Chinese one, supporting them might give you some edge.
So the simple answer would be: you need some of the stuff there.
=== 2016 ===
That was 7 years ago. Now everybody talks about emojis. Well, most emojis are beyond BMP :-)
这取决于您是否控制您的数据。 如果您使用除您自己以外的任何人的 Unicode 数据，您通常必须假设它可能包含增补字符，这又意味着您需要处理 4 字节 UTF-8、UTF-16 代理字符等。
It depends on whether you control your data or not. If you are using Unicode data from anyone other than yourself, you generally must assume that it may include supplementary characters, which in turn means you need to deal with 4-byte UTF-8, UTF-16 surrogate characters, and so on.
如果可能的话，您应该尝试支持所有 Unicode，包括补充平面。 现在有一些活语言位于补充平面，例如 苗语。 未来将添加其他现有语言，部分语言目前需要补充私人使用区域。 然后还有 Mihai Nita 在他的回答中所说的。
MySQL 从 5.5 开始，还支持补充平面。
现在最好花一点时间来完全支持 Unicode，这样将来如果您确实需要它，就不会遇到问题。 而且您不知道谁将使用您的软件以及他们将来将使用哪些脚本。 现在大多数渲染引擎、GUI 工具包、浏览器、操作系统等都会毫无问题地支持这一点。
虽然这个问题是几年前提出的，但我在搜索时遇到了这个问题，从那时起事情就发生了变化。 我目前正在处理一些问题，程序员要么认为不需要补充平面支持，要么仍未经过测试。
You should try, if at all possible, to support all of Unicode including supplementary planes. There are now living languages sitting in the supplementary planes such as Miao. Other living languages will be added in the future and some languages currently need the supplementary private use area. Then there is also what Mihai Nita said in his answer.
MySQL, starting with 5.5, also supports supplementary planes.
It's better to take the little bit of time now to fully support Unicode so that in the future you won't have problems if you actually do need it. And you don't know who will be using your software and what scripts they will be using in the future. Now most of the rendering engines, GUI toolkits, browsers, operating systems, etc., will support this without troubles.
Although this question was asked several years ago, I ran across this on a search, and things have changed since then. I am currently dealing with problems where programmers either assumed there would be no need for supplementary plane support, or it remained untested.
请参阅完整的字符图表列表。
补充字符目前包含古代文字。 除非您有一个应用程序可以处理古代文字，例如 Kharoshthi、Old Persion 和 Cuneiform，那么可能不会。
我想只有当您遇到不完整的 UTF-8 或 UTF-16 实现时，您才需要处理这个问题。 UTF-8 的某些实现不支持 4 字节字符，即补充平面：U+10000 以上的字符。 我想到了MySQL。
See the complete list of character charts.
The supplementary characters currently contain ancient scripts. Unless you have an application that should handle ancient scripts such as Kharoshthi, Old Persion and Cuneiform, then probably not.
I guess you will only have to deal with this issue if you encounter a UTF-8 or UTF-16 implementation that is not complete. Some implementations of UTF-8 do not support 4-byte characters, which is the supplementary plane: the characters above U+10000. MySQL comes to mind.