<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 11.12.2015 09:10, "Jürgen
Hestermann" wrote:<br>
</div>
<blockquote
cite="mid:trinity-92cadec7-5183-4e4d-84e8-b3d5a09c1f4d-1449821442234@3capp-gmx-bs37"
type="cite">
<div style="font-family: Verdana;font-size: 12.0px;">
<div>
<div name="quote" style="margin:10px 5px 5px 10px; padding:
10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap:
break-word; -webkit-nbsp-mode: space; -webkit-line-break:
after-white-space;">UTF8Delete probably takes an AnsiString
(or String) as var parameter and for var parameters the
static codepages have to match exactly (String has CP_ACP
while Utf8String has CP_UTF8).</div>
<div>
<div> </div>
<div>Just please help me understanding this:</div>
<div>The unit LazUTF8 unit is for manipulating UTF8 strings
only, correct?</div>
<div>Is there any reason that all functions are declared
with</div>
<div>parameter type STRING instead of UTF8String?</div>
<div>For what else should I use UTF8delete if not for
UTF8strings?</div>
<div>And what happens if the string has a different encoding
than UTF8?</div>
<div>I doubt that the function will produce any useful
result in this case</div>
<div>because it expects UTF8.<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
IMO it's a valid issue. Please create a feature request in the bug
tracker and - best - create a patch that introduces function
overloads that accept UTF8Strings.<br>
<br>
Ondrej<br>
</body>
</html>