Open jcmoraisjr opened 11 years ago
Submitted by joaolevada
I'm a little bit confused, now.
After some tests, I've noticed if you change the encoding of PressMessages_ptbr to UTF8, you'll need to use PressDecodeString to fix those corrupted strings.
Now I'll wait patiently for your position. :-)
Submitted by jcmoraisjr
Hello Joao. The inc files use ISO-8859-1 charset and need to be encoded to UTF-8 in order to work properly with lcl. I cannot use another approach and decode an UTF string because of Delphi, which, nativelly, does not know what unicode is.
Submitted by joaolevada
Hmm... Johnny, my friend.
So, I really don't know how to fix this...
Check out the image I've attached.
Submitted by jcmoraisjr
Now I see. The framework is duplicating calls to the encode routine. Thinking about the problem at this moment... Thanks for reporting this one.
Converted from SourceForge issue 3056022, submitted by joaolevada
Hello Morais.
I saw you've changed PressMessages.inc to fix charset issues with FPC, calling the PressEncodeString function.
That looks ok. But it's missing an update on resource string files. They're still on CP1252 codepage, and that's end on corrupted strings after the PressEncodeString function.
Can you verify this?
I've personally checked the PressMessages_ptbr.inc file.
Let me know, if I can help somehow.