Shachar Shemesh <[EMAIL PROTECTED]> writes: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.
Likewise, the Japanese sample text only has Aa (and not AaBb) ofThe question should be why do we go to the trouble of having parts of
Romanji (latin characters). For similar reasons, I left AaBb in place
(why remove it?).
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?
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
-- Shachar Shemesh Open Source integration & consulting Home page & resume - http://www.shemesh.biz/
The opinions expressed in this mail are my own, and do not necessarily represent the opinions of my employer. Wait! I am self employed! Hmm...
