I have got around most of the problem, by taking the text and writing it
to file using a filestream and a unicode encoder... The problem I am
facing is that when pulling data out of a MSSQL Database table, with
columns using NVARCHAR I get some corruption on a few strings...
Basically I am looking
Are you complaining about the implementation of some particular .Net API
related to getting NVarchar data from a SQL Server database into .Net String
variables? Or the implementation of an API that writes String data to files in
the UTF-16 little Endian encoding?
If you told us what APIs you'r
Me again,
Right I have an explanation for my current problem with text to
unicode... Now I am quite p*ssed off that microsoft have created
nvarchar considering it corrupts itself when trying to output unicode
files :(
Does anyone know how to get around the UTF-16 litte Endian encoding
problems w
