Alternate encoding names recognized by .Net / IE

If you run the sample from https://msdn.microsoft.com/en-us/library/system.text.encoding.getencodings.aspx then you can get a list of what Microsoft .Net thinks each Encoding/Code Page's name is.  (WebName is more consistent to what's used in charset). eg:

using System;
using System.Text;

public class SamplesEncoding
{
   public static void Main()
   {
      // For every encoding, get the property values.
      foreach( EncodingInfo ei in Encoding.GetEncodings() )
      {
         Encoding e = ei.GetEncoding();
         Console.Write( "{0,-6} {1,-25} ", ei.CodePage, ei.Name );
      }
   }
}

There are several other names that are recognized by Encoding.GetEncoding() however, similar to what IE would recognize in a charset tag.  I'm not sure if there's a way to get at the full list of aliases programatically, but this is what you'd get for these input strings: 

There's one really egregious name here.  UnicodeFFFE is actually Big Endian UTF-16.  It's like the byte order mark (BOM) for UTF-16BE written in little endian order.  Try to use UTF-16BE instead :)

Note that historically lots of data on the web has been mis-tagged, or isn't tagged at all.  For data from windows machines that data is often in the windows system code page, such as windows-1252.  So sometimes browsers may attempt to use the current system code page, or try to guess (with varying degrees of success), the actual code page.  Additionally there are differences between different vendor's code page behavior causing further ambiguity.

See also:

• Code Pages, Unicode & Encodings
• The History of Code Pages.aspx
• Some Reasons to Make Your Application Unicode.aspx