Stack Overflow 한국어 (Korean)

Install it and open stackoverflow.com; the content script runs at document_start and the interface is already Korean by the time the page paints, with no language setting to pick first. If you want English back, flip the switch in the toolbar popup.

No, and that's the point of how it's built. Post bodies, comments, code blocks, kbd and pre elements, question titles and excerpts, tag names, user cards and search results are all matched by an ignore-selector list and skipped along with everything inside them. Only interface strings — nav items, buttons, filters, metadata labels — get replaced.

Only on stackoverflow.com. Both the host permission and the content script match https://stackoverflow.com/* and nothing else, so meta.stackoverflow.com, Server Fault, Super User and the rest of the network stay in English. The dictionary was written against Stack Overflow's own DOM, so it wouldn't line up with those sites anyway.

A string is replaced only when the whole trimmed text matches a dictionary entry exactly, or matches one of the pattern rules for counts and relative timestamps. Anything outside that list is left as-is rather than machine-translated into something wrong. Text with no Latin letters in it is skipped outright, which keeps already-Korean strings and pure numbers from being touched.

Two entries: the storage permission, and a single host permission for https://stackoverflow.com/*. Storage is what holds the two booleans behind the popup switches — translation on/off and particle correction on/off — in chrome.storage.local, so your choices survive a restart. The host permission is the scope the content script is allowed to run in, and it matches the same single origin, which is why the extension has no effect on any other site. The Korean dictionary is bundled in the extension package, and the swap happens on text nodes in the page you're viewing.