When switching from Windows to a Mac, your very first day of typing often introduces two baffling frustrations: you press CapsLock to switch to Korean or English and the keypress is dropped unless you press it deliberately slow, and files you send to Windows coworkers decompose into disjointed characters like ㅂㅗㄱㅗㅅㅓ.docx.
It is easy to assume your keyboard hardware is defective or that macOS has an annoying bug. In reality, both quirks stem from deliberate Apple firmware design choices and foundational Unicode normalization differences.
You do not need to install intrusive, battery-draining keyboard remapping software like Karabiner. With simple native settings, lightweight Terminal tweaks, and the right compression tool, you can establish an effortless typing and file sharing workflow.
Why CapsLock Feels Sluggish on Mac
The CapsLock key on Apple keyboards was originally designed exclusively for capital letter locking. To prevent typists from accidentally brushing the edge of the key and screaming in all-caps, Apple embedded a hardware firmware threshold that ignores quick taps.
For bilingual typists, however, CapsLock is toggled hundreds of times daily at blazing speed. If you tap the key too lightly between keystrokes, the keyboard controller discards the stroke as accidental contact.
The cleanest zero-latency fix is switching to the native shortcut:
Open System Settings ▸ Keyboard ▸ Keyboard Shortcuts ▸ Input Sources. Set "Select previous input source" to Control + Space. Unlike CapsLock, Control + Space carries exactly 0ms of firmware latency. No matter how fast you fly across the keys, input switching registers instantaneously without a single dropped stroke.
Unlocking Hidden Keyboard Repeat Rates in Terminal
If holding down Backspace or the Arrow keys feels sluggish, macOS's GUI slider limits how fast keys repeat. You can push response times past system preferences using two Terminal commands:
defaults write -g InitialKeyRepeat -int 10
defaults write -g KeyRepeat -int 1
After executing both lines, log out of macOS and log back in (or reboot). Holding down delete or cursor keys will now repeat at lightning speed, vastly accelerating text navigation and code editing.
The Mystery of Decomposing Filenames: NFD vs. NFC
Broken Korean filenames on Windows are caused by divergent Unicode normalization standards:
- macOS uses NFD (Normalization Form D): Korean syllables are decomposed and stored as discrete phonetic elements (initial consonant, medial vowel, final consonant). macOS combines them visually on the fly, so they look perfectly normal on a Mac.
- Windows uses NFC (Normalization Form C): Korean syllables are treated as precomposed, atomic Unicode code points.
When an NFD-formatted file arrives on Windows File Explorer, it parses each decomposed character literally, resulting in fragmented text like ㅂㅗㄱㅗㅅㅓ.zip that breaks search indexes and internal company file management systems.
Preventing Jamo Separation with Keka
Right-clicking a folder in Finder and selecting "Compress" packages files using macOS's native NFD convention, guaranteeing broken text on Windows machines.
The definitive fix is adopting the free, open-source archiver Keka (available for free on keka.io, or as an optional donation purchase on the Mac App Store).
Launch Keka and open its Preferences:
- Compression Tab: Check "Exclude Mac metadata". This prevents polluting archives with hidden
__MACOSXfolders and._resource fork files. - Keka automatically normalizes all text to the cross-platform **NFC standard** during archive creation.
Dragging files onto the Keka icon creates universally compatible zip archives that render flawlessly across Windows, Linux, and enterprise web portals without character fragmentation. Tuning your native input shortcuts and pairing them with Keka resolves nearly all everyday typing and sharing headaches on macOS.