I know Lazarus itself is UTF8 and ZeosLIB to is UTF8 , my first problem was I was loosing characters when sending to sql for example
čćšđ would become ccsd .
Controls codepage for ZeosLIB was CCP_UTF8 , with autoencodestring turned on. Then I've tried to used CCP_UTF16 (which is as far as I understood
Unicode, or is supposed to be ) , but it still did not work, I've got ? marks.
So I finally found the solution by mistake :
cGET_ACP ( I read somewhere it's ANSI ) , and AutoEncodeString is turned OFF . Now in Lazarus I see characters displaying normally , and even my queries work, and stored procedures don't complain. But in SQL the names display strangely ( I can live with it , if it won't be a bigger problem later )
For example :
Bad Wünnenberg - Bad Wünnenberg
Gütersloh - Gütersloh
Hövelhof - Hövelhof
I only plan to use Lazarus with this SQL database nothing else , I am planning to try it out from a Windows 2000 professional maschine , to see if the characters are displayed correctly.... then from a Hungarian Windows XP machine as well. On Windows 7 all is fine.
Any ideas for possible dangers I might be facing in the future because of this?
Greetings
Robert
UPDATE 08:21 20.05.2014
I did try it under Windows XP Professional, it to is Unicode and plain English it was (my Win7 is german) . I've went around characters displayed correctly...I've added a few
new MileageLog's they to were with Unicode characters..and it displays correctly on both WinXP and Windows 7 , so I guess, I can be safe as far as I use Lazarus + ZeosLIB... probably I would have a hell of a time if I would try to view this from Delphi...
UPDATE 22.05.2014
If I set it to CP_UTF16 , it inserts correct characters into SQL, with select I get back every character correctly... but the same characters from within lazarus are not visible
