Re: [twsocket] pop3, buffer and character encoding

2010-07-02 Thread Zvone
> However, as long as this codepage was one of the windows-xyz, > single byte character sets converting back to Ansi with the > same codepage should work without data loss and give you back > the raw bytes (hopefully). This won't work, for example, with > Japanese locale settings. But there is a s

Re: [twsocket] pop3, buffer and character encoding

2010-07-02 Thread Arno Garrels
Zvone wrote: >> However, as long as this codepage was one of the windows-xyz, >> single byte character sets converting back to Ansi with the >> same codepage should work without data loss and give you back >> the raw bytes (hopefully). This won't work, for example, with >> Japanese locale settings.

Re: [twsocket] pop3, buffer and character encoding

2010-07-02 Thread Zvone
> TBytes was the datatype to be used. However that would break > backwards compatibility since historically "string" was used everywhere. > That all was no problem, however the rule is: "DO NOT BREAK BACKWARDS > COMPATIBILITY" and that is where the problems begin. Well you've already broken this r