>>18
C++? Isn't /prog/ flaming Sepples on every ocassion it has?
/prog/ is tsundere for C++. Every time it says anything bad about it, try to imagine it crossing its arms, looking away, and blushing.
Start by defining a set of features you want the engine to have. Then define how you want your users (scenario writers) to use those features. This includes defining the language. Then it's up to you how to continue. Some people prefer to implement from the bottom up, writing the lowest level infrastructure and building outwards; others prefer to implement from the top down, and write the upper level routines (such as the language interpreter or whatever you decide to use) first.
>>21
Locales are irrelevant for programs written to use Unicode (except for dates and such). What
>>15 said would be like the British complaining about the Spanish using the same codepoints to write "hola" that they use to write "hello". If the Japanese really do think that, they're just crazy if they think the Unicode committee is going to allocate another fifty thousand codepoints to accommodate the same glyphs twice.
Not that they care because they don't export their software to begin with.
Not that we care because their software is shit, anyway.