Skip to main content

Text Encoding and Decoding using .Net



Namespace: System.Text
To read a file, an application must write information about the encoding in which the file was written. So, the application that creates a file must write encoding information, otherwise viewer will see block and question marks in file.

Unicode UTF-32 encoding:
Represents a character as sequence of four bytes (32 bits). UTF32Encoding class can be used in that perspective.

Unicode UTF-16 encoding:
Represents a character in 16 bits. UnicodeEncoding class can be used to convert to and from UTF-16 encoding.

Unicode UTF-8 encoding:
Unicode UTF-8 uses 8-bit, 16-bit, 24-bit, and up to 48-bit encoding. Values 0 through 127 use 8-bit encoding and exactly match ASCII values, 128 through 2047 use 16-bit encoding, and values from 2048 and 65535 uses 24-bit encoding. UTF8Encoding class can be used to convert to and from UTF-8 encoding.

ASCII encoding:
ASCII encoding encodes Latin alphabets as single 7-Bit ASCII character. It is not well suited for internationalized applications. ASCIIEncoding class can be used to convert to and from ASCII encoding.

ANSI/ISO Encoding:
System.Text.Encoding provides support for a wide range of ANSI/ISO encodings.

Using Encoding class:
GetEncoding will return the specified encoding then GetByte or GetChar methods can be used.

Encoding e = Encoding.GetEncoding(“Korean”);

Byte[] encoded;

encoded = e.GetBytes(“Hello word!”);

for(int i=0;i<encoded.length;i++)
{
                Console.WriteLine(“Byte {0}:{1}”, i,encoded[i]);
}

Supported Encoding Types:
To get a list of supported Encoding one can iterate the EncodingInfo struct returned by Encoding.GetEncodings().

EncodingInfo[] eis = Encoding.GetEncodings();

foreach( EncodingInfo ei in eis)
                Console.WriteLine(“{0}:{1} , {2}” , ei.CodePage, ei.Name, ei.DisplayName);

To Specify Encoding type when writing Files:

StreamWrite sw = new StreamWrite(“SampleUTF.txt”, false, Encoding.UTF32);
Sw.WriteLine(“Hello Word!”);
Sw.close();

To Specify Encoding When Reading Files:

StreamReader sr = new StreamReader(“SampleUTF.txt”, false, Encoding.UTF32);
Console.WriteLine(“Output is : {0}”, sr.ReadLine());
Sr.Close();

Comments

Popular posts from this blog

Culture Information and Localization in .NET

Namespace: System.Globalization CultureInfo Class:                 It provides information like the Format of numbers and dates, Culture’s Calendar, Culture’s language and sublanguage (if applicable), Country and region of the culture. The Basic use of CultureInfo class is shown here: • How string Comparisons are performed • How Number Comparison & Formats are performed • Date Comparison and Formats. • How resources are retrieved and used. Cultures are grouped into three categories: Invariant Culture : It’s Culture Insensitive. It can be used to build some trial application. It can be also used to build an application with hard-coded expiry date that ignores cultures. But using it for every comparison will be incorrect and inappropriate. Neutral Culture : English(en), Frensh(fr), and Spanish(sp). A neutral culture is related to language but it’s not related to specific regi...

Exposing .NET Components to COM

Namespace: System.Runtime.CompilerServices Building .NET Components for use by COM .Net framework generates COM Proxies known as COM Callable Wrapper (CCW) to be used by COM. No matter how many COM clients consume a given managed object, .Net runtime will create a single CCW. Write down you class and before building it, Select the configuration form the project properties named “ Register for COM interop ”. Hiding public .NET Classes from COM To hide a class or member just use the following attribute: [ComVisible(true/false)] . Deploying COM-Enabled Assemblies :       Check the following necessaries before creating CCW: 1.        All class have default constructor (no parameter). 2.        Exposed Types should be public . 3.        Any member exposed should be public . 4.        Abstract classes will not b...

ASP.NET Working with Web Configuration Files

Our sites are configured based on hierarchy of XML configuration files. Machine.config is top level configuration file located in Config: %WINDIR%\Microsoft.NET\Framework\ <version> \Config\machine.config These settings are framework level and common to all Windows, Console, Class Library, and Web application. Some of them could be overridden in Web.config while others are protected. Next in hierarchy is Root.config. It’s located in Config: %WINDIR%\Microsoft.NET\Framework\ <version> \Config\web.config It contains default web server settings. Optionally one can add at root of all websites a web.config to provide general settings related to all sites. Optionally to provide more control on settings one can add web.config in each web site and for each folder in that web site. Processing the Configuration files:                       ...