Re: [fpc-devel] TRegistry and Unicode

2019-03-03 Thread Yuriy Sydorov
On 03.03.2019 17:45, Bart wrote: On Sun, Mar 3, 2019 at 11:17 AM Yuriy Sydorov wrote: This is good if you assign the result of ReadString() to a regular ansistring var. But if you assign it to a utf8string,unicodestring,widestring var - it will not return correct result for chars that are

Re: [fpc-devel] TRegistry and Unicode

2019-03-03 Thread Bart
On Sun, Mar 3, 2019 at 11:17 AM Yuriy Sydorov wrote: > This is good if you assign the result of ReadString() to a regular ansistring > var. But if you assign it to a > utf8string,unicodestring,widestring var - it will not return correct result > for chars that are missing in the current >

Re: [fpc-devel] Regressions on i386-win32 and x86_64-win64

2019-03-03 Thread Sven Barth via fpc-devel
Am 02.03.2019 um 22:57 schrieb J. Gareth Moreton: Hi Nikolai, I don't even know the testsuite URL myself - I just run the regression tests as found under "fpc/tests", which is fairly public given there's a readme file there explaining how to run them. Nikolai is talking about the result

Re: [fpc-devel] TRegistry and Unicode

2019-03-03 Thread Yuriy Sydorov
On 02.03.2019 18:53, Bart wrote: On Sat, Mar 2, 2019 at 3:48 PM Joost van der Sluis wrote: The utf8encode should go, just like the utf8decode's that we fixed already. Shall I post a patch in the bugtracker? If so: instead of SomeAnsiString := UTf8Encode(SomeUnicodeString) do I make it an