News for hackers. Stuff that matters.

A comment on UTF-8 history (2003). Parent comment

Re:UTF-8 history (2003) by kstenerud on Thursday October 10, 2019 @05:59AM (#21212652)
VLQ can also be backward scanned, since the high bit is the continuation bit. Just scan for the next cleared high bit, which marks the end of a glyph.
[ Parent | on HN ]
Re:UTF-8 history (2003) by SamReidHughes on Friday October 11, 2019 @12:51AM (#21221642)
Provided that you know where the string boundary is, so you don't scan off the front into differently encoded data. So it can't be backward scanned for some miscellaneous encoded number.
[ Parent | on HN ]
Re:UTF-8 history (2003) by lifthrasiir on Thursday October 10, 2019 @06:42AM (#21212895)
Ah, good point. I'm still confusing which one is which. I was specifically thinking of UTF-1 that is definitely not synchronized nor backward scannable.
[ Parent | on HN ]