On Fri, Feb 12, 2016 at 6:52 PM, Michael Schnell <[email protected]> wrote: > I think that it is *very* desirable to provide configuration options to > provide full backwards compatibility (while still allow to use as many of > the new features as possible when explicitly writing coding for this).
Uhhh... Michael Schnell, how is it possible you behave like a complete newbie with FPC's String encoding issues, after so many years of arguing about it in various mailing lists? Please show some respect to the people who made it work and even documented it. For example these questions : > That would mean that the type "String" is 8 Bit ? > That would mean that 8 bit Strings are used in TStrings and hence in > TStringList ? > That would mean that (e.g.) storing 8 bit "String"s in a TStringList would > not do any conversion at all ? > And it would mean that pos() and friends work on 8 bit Strings (and wist > simple byte-positions and length) ? ... were answered in the wiki pages I linked to you, and they are obvious after just minimal testing. If you find a bug then let us know, otherwise please show some positive attitude. The new UTF-8 system "just works" in most situations. I remember you repeated the same arguments against FPC's new String type in FPC lists during many years again and again. Let's not do the same here. Juha -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
