[fpc-pascal] TListBox bug in LCL of Lazarus?
juergen.hestermann at gmx.de
Sun Dec 21 16:19:03 CET 2008
> You don't need the AnsiToUTF8 if you encode your source file as UTF-8
> without a BOM.
Well, I installed and started Lazarus in the standard way so why isn't
it using UTF-8 by default if that's the only way to store strings? Why
let the user step into this trap? And how do I change my current code to
> The difference from Delphi is caused by Lazarus supporting unicode and
> also some limitations of Free Pascal, but nothing which prevents the
> correct development of unicode apps if you follow the documentation:
Thanks for the link. But why isn't it documented in the Help of
TListBox? No word there that the strings may be UTF-8 only (and that you
somehow have to store your code files in that coding if you use stings
> Delphi 7 doesn't support unicode, so I doubt you were using unicode
> routines there. Isn't that correct?
Yes, of course that's correct. That's the reason I didn't use Unicode
for Lazarus either. But that failed. So I had a hard time to find out
myself that I have to use AnsiToUTF8 for each and every constant string
I use. A quite distracting first contact with Lazarus/FPC.
More information about the fpc-pascal