<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>That would great Tamas, Thanks.</div>
<div> </div>
<div>And Thanks to Ragi for you input.</div>
<div>I had a look at you workaround, but I think your ghetto fix is not quite correct.</div>
<div>The C# wrapper interprets the unmanaged string as being ANSI encoded, which changes the bytes of the string when converting from ANSI to UTF16 and not just fills in every second byte.</div>
<div> </div>
<div>Your workaround might work for many non-ASCII characters, but not for all. 'ß' is an example that does not work.</div>
<div>If want a workaround that gets the correct string retroactively you would need to use:</div>
<div>string faultyStr = feature.GetFieldAsString(..);</div>
<div>string correctStr = Encoding.UTF8.GetString(Encoding.Default.GetBytes(faultyStr));</div>
<div> </div>
<div>The reverse direction would be:</div>
<div>string faultyStr = Encoding.Default.GetString(Encoding.UTF8.GetBytes(correctStr));</div>
<div>feature.SetField(.., faultyStr);</div>
<div> </div>
<div>Hopefully Tamas will fix the C# wrapper and we won't need the workaround anymore.</div>
<div>Or to be more exact, the workaround will obviously break things again, when the C# wrapper is fixed.</div>
<div> </div>
<div>Tamas, please tell us, if we can be of assistance.</div>
<div> </div>
<div>Greetings,</div>
<div>Dennis</div></div></body></html>