Recent

Author Topic: more UTF8 confusing  (Read 2650 times)

Bogen85

  • Hero Member
  • *****
  • Posts: 572
Re: more UTF8 confusing
« Reply #30 on: February 05, 2023, 07:53:31 pm »
EDIT: If it just went to the end of the string, then my utf8 string displayable character "splitter" function would not work, as I'm setting the max look ahead to maxint.
It doesn't go to the end of the string if there are no more marks. Though I would suggest to set MaxLookAhead to the actual remaining bytes of the string. Otherwise it could go beyond.

However, with an ansistring it would hit the null-terminating character, which would fail the checks for being a diacritical marker. So it would return without including the null as part of the byte count.

circular

  • Hero Member
  • *****
  • Posts: 4001
    • Personal webpage
Re: more UTF8 confusing
« Reply #31 on: February 05, 2023, 08:05:14 pm »
Indeed.
Conscience is the debugger of the mind

 

TinyPortal © 2005-2018