Closed zturtleman closed 9 years ago
iostvef removes the filters.
I made string value more than 127 networkable. '%' is still not, and is not required for UTF-8 (aside from '%' itself). And no, cannot cover it to %% as that only works if it's the format string which is not suppose to happen.
UTF-8 doesn't use 0xFF, I didn't think about removing it until re-reading this issue. Though I do not know why World of Padman removes it.
In msg.c, ioq3 filters out characters > 127 and '%' (replaced with '.'). World of Padman allows char != 0xFF and != '%'. I think all values would be needed for UTF-8.
The comments say they're filtered out because "because old clients don't like them".
Should '%' be replaced with "%%" to avoid format issues? Would msg.c need to be aware of UTF-8 for this?