It looks like you are not accounting for internationalized characters. What you'll need to do is read up on the System.Globalization namespace and the CultureInfo class in particular. If the text file is ASCII based, you may want to strongly consider moving to UNICODE so you can handle any languages you need to handle.
Dig Deeper on .NET Framework 3.0 design and architecture tools
Related Q&A from John Robbins
What is a JAD session? This term is referred to often in job postings and seems like some kind of brainstorm you carry out with a client to define IT... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.