[Lazarus] UTF8String and UTF8Delete

Jürgen Hestermann juergen.hestermann at gmx.de
Sun Dec 13 10:55:10 CET 2015


Am 2015-12-12 um 23:28 schrieb Juha Manninen:
 > On Sat, Dec 12, 2015 at 8:38 PM, <wkitty42 at windstream.net> wrote:
 >> especially those readers from the ancient past (TP/BP days) who are trying
 >> to catch up to the modern future...
 > LCL has supported UTF-8 for > 10 years. As a long time Lazarus user you should know it.

I think we all know this, but this is not the point.


 > For most cases things did not change very much. Earlier you had to use
 > the explicit UTF8...() functions, now you don't need them.

What does this mean?
If I use DELETE on a String type (that is an UTF-8 string)
does it now use UTF8Delete internally?
Does it delete bytes or code points?
Does LENGTH now give back the number of bytes or the
number of characters (when used on an UTF-8 String)?


 > Things are better!

Maybe, but without fully understanding the mechanism it is worse in the first place.





More information about the Lazarus mailing list