Matching UTF16 (Windows) chars

[NWoodsman]

When looking at raw hex in Windows, I can see strings of text that look interesting but they are likely UTF 16, i.e. native Windows char and therefore are two bytes wide, which means in 99% of cases where you are only interested in ASCII strings, the empty second byte needs to be ignored.

It's not clear in the documentation how to account for the two byte size when searching. Matching a string would need to match both the ASCII byte and the empty byte.

Also, in the same subject, it would be really useful to have a right-click context option "Copy as UTF8 string" or "Copy as UTF16 string"

[NWoodsman]

For those encountering the same issue, the solution was to Find -> Sequences Tab -> Type Dropdown -> UTF16-LE or UTF16-BE. Then a string will be found respecting the empty byte.