Encoding - OEM to ANSI

[Yves Royer]

Hi all,

i'm currently writing an application which can read multiple formats of
textfiles and converts all of those to another one and the same. One of the
incoming type of textfiles are written in the OEM codepage. My question is,
how can i convert the OEM textfile to a textfile using the ANSI (Windows)
codepage? I've read something about the Encoding and Encoder classes in the
System.Text namespace but i can't figure it out how to do it... :-/

Can anybody help me with this one?

Thanks,

Yves

[Mattias Sjögren]

> Can anybody help me with this one?

The most direct way to do this would be to read the file into a byte array
and call OemToCharA (the ANSI version of the OemToChar Win32 API).

If you definitely want to use the Encoding classes I guess you could use the
GetOEMCP API to get the current OEM code page, construct an Encoding instance
from that, convert the OEM data to a Unicode string or char[], and then
finally back to an ANSI byte array with Encoding.Default. But this involves a
rather unnecessesary Unicode conversion as an intermediate step.

Note that there's not one OEM code page. There are a whole bunch of them and
which one GetOEMCP returns is system dependent.
Mattias

[Yves Royer]

Thanks for your answer.
But the thing about the Win32 API... I don't know exactly how you can do it
that way... any example mayby? I'm sorry about the (silly) question but i'm
rather new to C#.

Thanks,

Yves
"Mattias Sjögren" <Ma***********@discussions.microsoft.com> schreef in
bericht news:6D**********************************@microsof t.com...

Can anybody help me with this one?

The most direct way to do this would be to read the file into a byte array
and call OemToCharA (the ANSI version of the OemToChar Win32 API).

If you definitely want to use the Encoding classes I guess you could use
the
GetOEMCP API to get the current OEM code page, construct an Encoding
instance
from that, convert the OEM data to a Unicode string or char[], and then
finally back to an ANSI byte array with Encoding.Default. But this
involves a
rather unnecessesary Unicode conversion as an intermediate step.

Note that there's not one OEM code page. There are a whole bunch of them
and
which one GetOEMCP returns is system dependent.
Mattias

[Jon Skeet [C# MVP]]

Yves Royer <yv********@telenetSPAM.be> wrote:

I see... but isn't that the "unmanaged" way of coding in .NET?

I came to another possible difficulty... is there a simple way to determine
if the file is made with one of the OEM codepages or the ANSI codepage? This
way I know how i should read a file (OEM codepage or ANSI codepage).

No, there isn't. The file is just a sequence of bytes. It could be
valid in either code page.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[Yves Royer]

Ok.
Thanks a lot for the help and patience :-)

Yves
"Jon Skeet [C# MVP]" <sk***@pobox.com> schreef in bericht
news:MP************************@msnews.microsoft.c om...

Yves Royer <yv********@telenetSPAM.be> wrote:

I see... but isn't that the "unmanaged" way of coding in .NET?

I came to another possible difficulty... is there a simple way to
determine
if the file is made with one of the OEM codepages or the ANSI codepage?
This
way I know how i should read a file (OEM codepage or ANSI codepage).

No, there isn't. The file is just a sequence of bytes. It could be
valid in either code page.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too