Modern Windows versions are Unicode based, meaning that two bytes are used for each character. However, certain text utilities may not understand Unicode. I did have some problems when loading a CSV file I made with FTK Imager into an SQL database. All text strings looked as if all characters where separated with spaces, for example:
h e l l o , h o w a r e y o u t o d a y . c s v
instead of
hello, how are you today.csv
This was certainly not the result I was looking for. Fortunately, this is quite easy to solve. If you want to convert a multibyte CSV file to a one-byte-per-character version, type the following command:
TYPE unicodefile.csv > plaintextfile.txt
If your file contains "extended" ASCII characters like ë or à, you first have to type
CHCP 1252
after the dos prompt. 1252 is the most commonly used codepage for western languages in modern Windows versions.
The type command performs the conversion. It is useful if you're dumping out registry keys from regedit.exe, which writes out in Unicode format.
magnificent post, very informative. I'm wondering why the opposite experts of this sector do not realize this. You must proceed your writing. I'm confident, you have a huge readers' base already!
Posted by: appliance repair tampa service | November 14, 2013 at 08:05 PM