Therefore, if the VersionInfo string contains a 4-byte utf-16 character - it will not be treated properly.
It will result in 2 different forcefully casted Unicode characters.
Question
Am I wrong or do not know something?
Or it should be fixed in pefile?
I understand that frequency meeting characters taking 4-byte size might not be big.
But at the end of the day, it is not handled.
Given
utf-16-le
encodingget_string_u_at_rva
used https://github.com/erocarrera/pefile/blob/4b3b1e2e568a88d4f1897d694d684f23d9e270c4/pefile.py#L6476-L6517Problem
Therefore, if the VersionInfo string contains a 4-byte utf-16 character - it will not be treated properly. It will result in 2 different forcefully casted Unicode characters.
Question
Am I wrong or do not know something? Or it should be fixed in
pefile
?I understand that frequency meeting characters taking 4-byte size might not be big. But at the end of the day, it is not handled.