[fpc-devel] String handling in trunk (was utf8 in 2.6.0)

Michael Schnell mschnell at lumino.de
Mon Jan 7 12:50:38 CET 2013


On 01/05/2013 01:35 PM, Jy V wrote:
> I do vote for UTF-8
-1

Regarding that conversions in the RTL (or LCL) are a rather seldom 
runtime-task, GUI performance issues are not really necessary to be 
considered.

Viable issues seem to be Delphi compatibility, backward compatibility, 
usability, runtime-performance with time consuming complex string tasks 
(these seem to vote against UTF8, but for either static UTF 16 or 
(quasi-) dynamical (CE-alike) encoding; and memory usage and 
runtime-performance with time consuming simple string tasks (which vote 
for locale-based ANSI or UTF-8).

-Michael



More information about the fpc-devel mailing list