IMO the Insert procedure should change the encoding of the
string-to-insert into the CP of the target string. Else the target
string can become unusable, containing an mix of characters from
different codepages. While a RawByteString can have any encoding, it
cannot have two encodings at the sa
On 12/05/2014 10:51 AM, Hans-Peter Diettrich wrote:
IMO the Insert procedure should change the encoding of the
string-to-insert into the CP of the target string. Else the target
string can become unusable, containing an mix of characters from
different codepages. While a RawByteString can have