Sure. char is not specified to support ASCII either but it's not really a problem in practice :)
If you start avoiding all the things that are not fully specified by the standard, your C programs will end up doing very little indeed.
Now, it might be that some environments targeted by Lua have very spartan C runtimes: consoles. Anyone
have a pointer to the C runtime docs for Xbox 360 and PS3?
Just out of curiosity: What is its replacement? If I remember correctly it began its life as the char type for multi-byte character sets and later found use for UTF-(16|32) code units.
Should Unicode strings forcibly be UTF-8 in all programs and use char again (thus suffering from the same problem that Python 2 had where bytestrings and Unicode strings weren't sufficiently distinguished, often leading to programmers using the former for text)?
Or should you use short/int arrays instead and have no support from the stdlib at all for handling them (not that the stdlib is particularly good at handling text)?