[Lazarus] Debugging fixed strings in UTF8 encoding

Mattias Gaertner nc-gaertnma at netcologne.de
Mon Apr 1 12:18:49 CEST 2013


On Mon, 01 Apr 2013 11:03:31 +0100
Martin <lazarus at mfriebe.de> wrote:

> On 01/04/2013 10:53, Mattias Gaertner wrote:
> > On Mon, 01 Apr 2013 10:13:22 +0100
> > Martin <lazarus at mfriebe.de> wrote:
> >
> >> [...]
> >> It could do a heuristic, checking if the result has such invalid chars,
> >> and if there is one then do all as #123. But an ascii sting may be a
> >> valid utf8 string sometimes, yet the utf8 would map to entirely
> >> different chars. In this case the heuristic would show a utf8 without
> >> warning that the content is wrong (well it already does/would do)
> > How likely is this case?
> >
> 
> This wasn't a case against it, as more a general observation... And it 
> is already happening.

Do you mean, there were already real cases where a string had bytes
#191..#254 and is valid UTF-8, but was windows codepage?

Mattias




More information about the Lazarus mailing list