Op 01-03-19 om 22:19 schreef Bart:
On Tue, Feb 26, 2019 at 10:49 AM Marco van de Voort
<c...@pascalprogramming.org> wrote:
If I look into e.g. registry.pp, the only use of utf8encode there is
like this:
var s : string;
u:unicodestring;
s:=utf8encode(u);
which, IF lazarus is used in the default utf8 mode is equivalent to
s:=u;
So currently this utf8encode only frustrates the situation for people
that don't set the default codepage to utf8?
Exactly.
It also breaks backwards compatibility.
Strings returned were encode in the systems codepage up to 3.0.4, now
thy are not.
The utf8encode should go, just like the utf8decode's that we fixed already.
Regards,
Joost.
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel