4 ms·

I lived in Korea between 2010 and 2015 and I never needed the Korean version of Windows. Even my work computer was running the en-US version. Your just need to

I lived in Korea between 2010 and 2015 and I never needed the Korean version of Windows. Even my work computer was running the en-US version. Your just need to switch the default locale and codepage for the occasional poorly written software (mostly old installers), it just takes a reboot.

gmueckl 7y ago
MS had completely separate custom builds of Windows (made out of completely different binaries) until XP at least. E.g. an English Windows and a German Windows would install completely different files and the only way tonswitch system language was a reinstall. Conponents to support CJK were not part of these installs, either. This changed with Vista or 7 (don't remember) where they were able to seperate Windows into a core plus a set of language packs for all regions. So depending on which version of Windows you are talking about you might both be right.
- mook 7y ago
  Actually I believe Windows 2000 had support for language packs (MUI if I remember correctly). You _had_ to start with an en-US install to use those, so the bit about different language versions installing different files was still correct. Components for CJK support was a check box in the Language & Region control panel, which required the Windows install disc to apply. I think the language packs might not have been available in all SKUs; not very sure about that part. The CJK support, I think, was. The default system locale thing (MBCS) was a separate issue.
  - gmueckl 7y ago
    How would the language packs have worked? Back then the translations were created by patching the resource tables of the compiled binaries. So notepad.exe with German localization would just contain the German strings instead of the English ones. There were no external string tables that I am aware of. That came with Vista, I believe. Since then, every language version is (finally!) the same base install plus the appropriate and exchangeable language pack.
- Kuraj 7y ago
  Vista had language packs, but they were exclusive to Ultimate.

gmueckl 7y ago

MS had completely separate custom builds of Windows (made out of completely different binaries) until XP at least. E.g. an English Windows and a German Windows would install completely different files and the only way tonswitch system language was a reinstall. Conponents to support CJK were not part of these installs, either. This changed with Vista or 7 (don't remember) where they were able to seperate Windows into a core plus a set of language packs for all regions. So depending on which version of Windows you are talking about you might both be right.

mook 7y ago
Actually I believe Windows 2000 had support for language packs (MUI if I remember correctly). You _had_ to start with an en-US install to use those, so the bit about different language versions installing different files was still correct. Components for CJK support was a check box in the Language & Region control panel, which required the Windows install disc to apply. I think the language packs might not have been available in all SKUs; not very sure about that part. The CJK support, I think, was. The default system locale thing (MBCS) was a separate issue.
- gmueckl 7y ago
  How would the language packs have worked? Back then the translations were created by patching the resource tables of the compiled binaries. So notepad.exe with German localization would just contain the German strings instead of the English ones. There were no external string tables that I am aware of. That came with Vista, I believe. Since then, every language version is (finally!) the same base install plus the appropriate and exchangeable language pack.
Kuraj 7y ago
Vista had language packs, but they were exclusive to Ultimate.