Alexandre Julliard wrote:
Shachar Shemesh wine-devel@shemesh.biz writes:
Likewise, the Japanese sample text only has Aa (and not AaBb) of Romanji (latin characters). For similar reasons, I left AaBb in place (why remove it?).
The question should be why do we go to the trouble of having parts of the string handled in two different places, when we could simply store the full string in the sample text array. It would make the code simpler, more flexible, and more compatible. Is there a good reason for doing it the way it is now?
The reason is the unicode version of the dialog. In Unicode, you may need to display several "character sets" simultaniously. When that happens, you don't want to repeat the AaBb string over and over.
As for the strings themselves - they are 100% language independant, as far as I can tell. After all, they don't spell a word in any language that I actually speak (Arabic may be an exception here, as may Japanese). Even when they, do, it's a word in that language.
I failed to understand how you wanted to make it into a resource.
Shachar