Yes, I still recommend for anybody to study the topic because it is unbelievably complex. However talking about Lazarus and the new FPC brings some obvious new questions. Unicode is the main feature of FPC 3.0 after all.
The perfect world would be to see stable Lazarus 1.4 and stable FPC 3.0 released together.
Quote from: Человек_Борща on January 13, 2015, 07:24:19 amPlease, explain me, what about unicode support in Lazarus?It is supported by AnsiString + UTF8 specific functions. See : http://wiki.freepascal.org/LCL_Unicode_SupportLazarus 2.0 will improve things.
Please, explain me, what about unicode support in Lazarus?
The Windows unit won't really change in newer FPC versions, since that is the interface of Windows operating system, and windows won't suddenly start supporting utf8.On Windows, Utf8 is for textfiles only, not for APIs.The only change that still must happen is to switch the default names (e.g. GetCRC32OfFile) from the -A to the -W alias, similar like D2009 did
I would like to include here some extra information I read in other topic that I think is relevant to this discussion.
Why are those things relevant? Both myself and Marcov stated some well known facts for a new person who does not know them yet.For example LCL has supported Unicode maybe 7 or 8 years. Nothing new there.
This topic has been read 2494 times so far. It seems to me that it is interesting to many people, including new comers.
How far is FPC3.0 safe to use with Lazarus trunk version
Hello Guys,I have an alternative question. Will this FPC support Android developing?Regards,Sty
So it seems there actually may be real benefits of using FPC 3.0 and Lazarus 1.2.x together, if I got that correctly...