Thanks for the appreciation; the next Korean Konundrum will focus on multilingualism under KDE/Linux and how to implement SCIM to change the text language in word processors - and a few of the problems I have encountered.
I think the point is a valid one. The original XP Pro disc was pressed in Malaysia, the installation is entirely in Korean and I have little idea how "safe" any of the following installations were. Text boxes and menus are all in Korean unless I install something which I know will be in English.
And I suppose that in the end, there is a message in all of this. When an OS moves from one area of language preference to another, the underlying software should not change any of its functionality - the only necessary change should be the language packs, which are essentially "text" rather than "software" (in the sense of things which can or cannot be executable) and in an age when whole OSes can be transferred rapidly via the Internet, why oh why can I (or anyone else) not simply opt for whatever my own language preference is and have it installed in a flash? What's the problem?
This is all part of the licensing disease which has struck so many (particularly American) businesses; even music now comes with a "licence", it's just pathetic. These businesses want to restrict the flow of their proprietary software across borders. Haven't they ever stopped to think about the consequences of this? When you can't have the computer running the OS of your choice using your own language preference, this poses an unacceptable security risk when that OS is the target of almost all of the viruses and malware out there, and as I put it in the article, that effectively meant that Microsoft had left me no choice: either Linux or no security on my PC.
Hmm . . . I can feel a rant coming on . . . time for some more coffee . . .