<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>
</head>
<body>
<p style="margin: 0;">
<span>
<span></span>
</span>
</p>
<p style="margin: 0px;"> </p>
<div style="margin: 5px 0px 5px 0px;">
<br/>
Michael Schnell <mschnell@lumino.de> hat am 13. Oktober 2011 um 10:18 geschrieben:
<br/>
<br/>
> On 10/13/2011 04:27 AM, Hans-Peter Diettrich wrote:
<br/>
> >
<br/>
> > I don't see a speed penalty in using UTF-16. In contrast to UTF-8 it
<br/>
> > simplifies (and consequently speeds up) all string handling.
<br/>
>
<br/>
> If doing code heavily doing GUI handling (such as the LCL in Lazarus)
<br/>
> and the GUI's API is not UTF-16, all strings passing the API need to be
<br/>
> converted. This will slow down things a lot.
</div>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">That's non sense. Prove: some LCL backends work in UTF-16. </p>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">Maybe you confused that with the IDE?</p>
<p style="margin: 0px;">The IDE does heavy string handling. In fact so much that many parts were replaced with PChar. </p>
<p style="margin: 0px;"> </p>
<div style="margin: 5px 0px 5px 0px;">
<br/>
> So quite obviously projects like the LCL need to use a "variable" Type
<br/>
> (either dynamic or static) throughout the complete code in some way.
</div>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">Mattias</p>
<p style="margin: 0px;"> </p>
</body>
</html>