Skip to content

src: warn about odd UTF-16 decoding function signature

Using a uint16_t sequence for UTF-16 processing would typically imply that the sequence already contains the correct 16-bit code units.

However, our API does not account for that. The previous comments were somewhat misleading, since endianness is typically applied to sequences of bytes, which is not something that this API works with.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • documentation is changed or added
  • commit message follows commit guidelines

Merge request reports

Loading