System.Text.Encoding.GetEncoding（“ iso

本文介绍了System.Text.Encoding.GetEncoding（“ iso-8859-1”）引发PlatformNotSupportedException？的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

请参阅主题，请注意，此问题仅适用于.NET 紧凑型框架。 Windows Mobile 6 Professional SDK附带的仿真器以及我的英文HTC Touch Pro（所有.NET CF 3.5）上都会发生这种情况。 iso-8859-1代表西欧（ISO），这可能是除us-ascii之外最重要的编码（至少在按Usenet帖子数量统计时）。

See subject, note that this question only applies to the .NET compact framework. This happens on the emulators that ship with Windows Mobile 6 Professional SDK as well as on my English HTC Touch Pro (all .NET CF 3.5). iso-8859-1 stands for Western European (ISO), which is probably the most important encoding besides us-ascii (at least when one goes by the number of usenet posts).

我很难理解为什么不支持此编码，而同时支持以下编码（在仿真器和我的HTC上也是如此）：

I'm having a hard time to understand why this encoding is not supported, while the following ones are supported (again on both the emulators & my HTC):

• iso-8859-2（中欧（ISO））
• iso-8859-3（拉丁3（ISO））
• iso-8859-4（波罗的海（ISO））
• iso-8859-5（西里尔语（ISO））
• iso -8859-7（希腊文（ISO））

• iso-8859-2 (Central European (ISO))
• iso-8859-3 (Latin 3 (ISO))
• iso-8859-4 (Baltic (ISO))
• iso-8859-5 (Cyrillic (ISO))
• iso-8859-7 (Greek (ISO))

因此，支持说希腊语比支持德语，法语$ b更重要$ b和西班牙文？谁能对此有所启发？

So, is support for say Greek more important than support for German, French and Spanish? Can anyone shed some light on this?

谢谢！

Andreas

推荐答案

我会尝试使用 windows-1252作为编码字符串。 根据Wikipedia ，Windows-1252是ISO-8859-1的超集。

I would try to use "windows-1252" as encoding string. According to Wikipedia, Windows-1252 is a superset of ISO-8859-1.

System.Text.Encoding.GetEncoding(1252)