Hello Zvone,
Yes, the Unicode implementation of the POP3 client is weak.
It converts the bytes received to Unicode with current Ansi
system codepage. This is direct result of ICS rule #1 to not
break backwards compatibility.
However, as long as this codepage was one of the windows-xyz,
single
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.
But
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 rule by
