Your convention of short/int/long/word/dword for signed is not just an x86-ism; it's a Windows-ism (SHORT/LONG/WORD/DWORD). I don't see why Windows programmers like them so much when the standard (u)intN_t types are more clear to pretty much everyone.
I don't think x86 naturally comes with "word" and "double word"; registers are al,ah (8-bit), ax (16-bit), eax (32-bit). I forget how you specify the size of a memory-memory move, though.
M68K instructions have .b (byte), .w (word), and .l (long) suffixes. No double/quad-word IIRC.
ARM has ldb (byte), ldh (halfword), ldr (register).
PPC has byte, halfword, word, and doubleword IIRC.
In general, it's pretty meaningless to talk about "word size", since it's highly architecture-dependent, and even then it tends to change (I doubt that modern x86 implements 16-bit arithmetic any faster than 32-bit arithmetic).
Then there's also the "pointer size" definition, but amd64 only has 48-bit virtual addresses (the top 17 bits are supposed to be all 1 or all 0).