{"id":71862,"date":"2014-08-28T21:53:37","date_gmt":"2014-08-28T19:53:37","guid":{"rendered":"http:\/\/onsoftware.en.softonic.com\/?p=71862"},"modified":"2025-07-02T00:30:45","modified_gmt":"2025-07-02T07:30:45","slug":"how-to-fix-chrome-64-bit-japanese-korean-unicode-text-error-1","status":"publish","type":"post","link":"https:\/\/cms-articles.softonic.io\/en\/how-to-fix-chrome-64-bit-japanese-korean-unicode-text-error-1\/","title":{"rendered":"How to fix Chrome 64-bit Japanese &amp; Korean unicode error"},"content":{"rendered":"<p>The release of <a title=\"Chrome update brings 64-bit for Windows, offers security and speed\" href=\"http:\/\/news.en.softonic.com\/chrome-64-bit-for-windows-offers-security-and-speed-available-now\" target=\"_self\" rel=\"noopener noreferrer\">Chrome 64-bit<\/a> brought support for modern hardware and promises &#8220;fewer crashes, better performance, and security.&#8221; But with such a dramatic update, some things got broken, one of which is displaying unicode characters for Asian languages.<\/p>\n<p>There is a bug within Chrome 64-bit <strong>Version 37.0.2062.94<\/strong> that can change font settings and remove the ability to <strong>display Japanese and Korean text<\/strong>. This also affected some Chinese text, but is not as widespread. The bug isn&#8217;t easily reproduced on every computer, but you&#8217;ll know if you have it. I have Chrome 64-bit installed on different computers and I have the display error on one install of Chrome but not the other.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-large wp-image-71874\" title=\"chrome facebook korean error\" src=\"https:\/\/articles-img.sftcdn.net\/sft\/articles\/auto-mapping-folder\/sites\/3\/2014\/08\/facebook-01-504x446.png\" alt=\"chrome facebook korean error\" width=\"504\" height=\"446\" srcset=\"https:\/\/articles-img.sftcdn.net\/auto-mapping-folder\/sites\/3\/2014\/08\/facebook-01.png 504w, https:\/\/articles-img.sftcdn.net\/auto-mapping-folder\/sites\/3\/2014\/08\/facebook-01-256x226.png 256w\" sizes=\"auto, (max-width: 504px) 100vw, 504px\" \/><\/p>\n<p>The major sites where people reported the problem is <strong>Facebook<\/strong> and popular Asian language sites. If you&#8217;re experiencing this bug, the steps below should get Japanese and Korean to display again in Chrome.<\/p>\n<h3>Auto detect encoding in Chrome<\/h3>\n<p>Open the\u00a0Chrome menu (three bars) and locate <em>Tools<\/em>. In the menu, find <em>Encoding<\/em> and make sure that <em>Auto detect<\/em> is selected. This option will automatically check to make sure the page has the right encoding.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-large wp-image-71868\" title=\"chrome tools encoding auto-detect\" src=\"https:\/\/articles-img.sftcdn.net\/sft\/articles\/auto-mapping-folder\/sites\/3\/2014\/08\/chrome-tools-encoding-auto-detect-500x568.png\" alt=\"chrome tools encoding auto-detect\" width=\"500\" height=\"568\" srcset=\"https:\/\/articles-img.sftcdn.net\/auto-mapping-folder\/sites\/3\/2014\/08\/chrome-tools-encoding-auto-detect-500x568.png 500w, https:\/\/articles-img.sftcdn.net\/auto-mapping-folder\/sites\/3\/2014\/08\/chrome-tools-encoding-auto-detect-225x256.png 225w, https:\/\/articles-img.sftcdn.net\/auto-mapping-folder\/sites\/3\/2014\/08\/chrome-tools-encoding-auto-detect.png 568w\" sizes=\"auto, (max-width: 500px) 100vw, 500px\" \/><\/p>\n<h3>Font settings in Chrome<\/h3>\n<p>Another place to check is in <em>Web content<\/em> and the <em>Customize fonts<\/em> menu. Open the\u00a0Chrome menu (three bars) and open the <em>Settings<\/em> menu. <em>Web content<\/em> is found by clicking on <em>Show advanced settings.<\/em> Open the menu and scroll to the bottom and make sure that <strong>Unicode (UTF-8)<\/strong> is selected. UTF-8 is the most common setting for websites.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-large wp-image-71869\" title=\"chrome settings web content\" src=\"https:\/\/articles-img.sftcdn.net\/sft\/articles\/auto-mapping-folder\/sites\/3\/2014\/08\/chrome-settings-web-content-568x261.png\" alt=\"chrome settings web content\" width=\"568\" height=\"261\" srcset=\"https:\/\/articles-img.sftcdn.net\/auto-mapping-folder\/sites\/3\/2014\/08\/chrome-settings-web-content.png 568w, https:\/\/articles-img.sftcdn.net\/auto-mapping-folder\/sites\/3\/2014\/08\/chrome-settings-web-content-256x117.png 256w\" sizes=\"auto, (max-width: 568px) 100vw, 568px\" \/><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-large wp-image-71870\" title=\"chrome settings web content encoding\" src=\"https:\/\/articles-img.sftcdn.net\/sft\/articles\/auto-mapping-folder\/sites\/3\/2014\/08\/chrome-settings-web-content-encoding-532x152.png\" alt=\"chrome settings web content encoding\" width=\"532\" height=\"152\" srcset=\"https:\/\/articles-img.sftcdn.net\/auto-mapping-folder\/sites\/3\/2014\/08\/chrome-settings-web-content-encoding.png 532w, https:\/\/articles-img.sftcdn.net\/auto-mapping-folder\/sites\/3\/2014\/08\/chrome-settings-web-content-encoding-256x73.png 256w\" sizes=\"auto, (max-width: 532px) 100vw, 532px\" \/><\/p>\n<h3>Disable DirectWrite<\/h3>\n<p>If the above options didn&#8217;t work or text is hit-or-miss, the best fix is to <strong>disable DirectWrite<\/strong>. To access this option, in the address bar type in <a title=\"Chrome experimental flags\" href=\"\/\/flags\/\" target=\"_blank\" rel=\"noopener noreferrer\">chrome:\/\/flags<\/a>. This will bring you to the experimental features within Chrome. It&#8217;s recommended you don&#8217;t mess with these options, but in this case, this is the best fix.<\/p>\n<p>Click on <em>Enable<\/em> to disable DirectWrite in Chrome. To apply changes, click the <em>Relaunch Now<\/em> button at the bottom of the tab. Chrome will relaunch with all the same tabs that were previously open.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-large wp-image-71872\" title=\"chrome disable directwrite\" src=\"https:\/\/articles-img.sftcdn.net\/sft\/articles\/auto-mapping-folder\/sites\/3\/2014\/08\/chrome-disable-directwrite-568x483.png\" alt=\"chrome disable directwrite\" width=\"568\" height=\"483\" srcset=\"https:\/\/articles-img.sftcdn.net\/auto-mapping-folder\/sites\/3\/2014\/08\/chrome-disable-directwrite.png 568w, https:\/\/articles-img.sftcdn.net\/auto-mapping-folder\/sites\/3\/2014\/08\/chrome-disable-directwrite-256x217.png 256w\" sizes=\"auto, (max-width: 568px) 100vw, 568px\" \/><\/p>\n<p>Disabling DirectWrite should solve any problems with displaying text. Now you can browse sites that contain a lot of Asian text without missing any important information.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-large wp-image-71875\" title=\"chrome facebook korean \" src=\"https:\/\/articles-img.sftcdn.net\/sft\/articles\/auto-mapping-folder\/sites\/3\/2014\/08\/facebook-02-506x446.png\" alt=\"chrome facebook korean \" width=\"506\" height=\"446\" srcset=\"https:\/\/articles-img.sftcdn.net\/auto-mapping-folder\/sites\/3\/2014\/08\/facebook-02.png 506w, https:\/\/articles-img.sftcdn.net\/auto-mapping-folder\/sites\/3\/2014\/08\/facebook-02-256x225.png 256w\" sizes=\"auto, (max-width: 506px) 100vw, 506px\" \/><\/p>\n<p>On the <a title=\"Multi-byte characters not displayed in Chrome\" href=\"https:\/\/code.google.com\/p\/chromium\/issues\/detail?id=407945\" target=\"_blank\" rel=\"noopener noreferrer\">Chrome product forums<\/a>, the development team is aware of the issue and there should be a fix coming soon, but there isn&#8217;t a release date. For right now, this is the only way to have a more permanent fix for the display error for unicode text.<\/p>\n<h3>Related Articles<\/h3>\n<p><a title=\"Chrome update brings 64-bit for Windows, offers security and speed\" href=\"http:\/\/news.en.softonic.com\/chrome-64-bit-for-windows-offers-security-and-speed-available-now\" target=\"_self\" rel=\"noopener noreferrer\">Chrome update brings 64-bit for Windows, offers security and speed<\/a><\/p>\n<p><a title=\"16 must-have apps for every teacher\" href=\"http:\/\/features.en.softonic.com\/16-must-have-apps-for-every-teacher\" target=\"_self\" rel=\"noopener noreferrer\">16 must-have apps for every teacher<\/a><\/p>\n<p><a title=\"Stop ignoring Android app permissions\" href=\"http:\/\/features.en.softonic.com\/stop-ignoring-android-app-permissions\" target=\"_self\" rel=\"noopener noreferrer\">Stop ignoring Android app permissions<\/a><\/p>\n<p style=\"text-align: right\"><em>Follow me on Twitter: <a title=\"Chris Park on Twitter\" href=\"http:\/\/www.twitter.com\/chrislikesrobot\" target=\"_blank\" rel=\"noopener noreferrer\">@chrislikesrobot<\/a><\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>The release of Chrome 64-bit brought support for modern hardware and promises &#8220;fewer crashes, better performance, and security.&#8221; But with such a dramatic update, some things got broken, one of which is displaying unicode characters for Asian languages. There is a bug within Chrome 64-bit Version 37.0.2062.94 that can change font settings and remove the &hellip; <a href=\"https:\/\/cms-articles.softonic.io\/en\/how-to-fix-chrome-64-bit-japanese-korean-unicode-text-error-1\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;How to fix Chrome 64-bit Japanese &amp; Korean unicode error&#8221;<\/span><\/a><\/p>\n","protected":false},"author":2030,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","wpcf-pageviews":1},"categories":[2441],"tags":[2767,1045],"usertag":[],"vertical":[],"content-category":[],"class_list":["post-71862","post","type-post","status-publish","format-standard","hentry","category-how-to","tag-app-subdomain-redirectionchrome-64-bit","tag-google-chrome"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/posts\/71862","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/users\/2030"}],"replies":[{"embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/comments?post=71862"}],"version-history":[{"count":1,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/posts\/71862\/revisions"}],"predecessor-version":[{"id":330259,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/posts\/71862\/revisions\/330259"}],"wp:attachment":[{"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/media?parent=71862"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/categories?post=71862"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/tags?post=71862"},{"taxonomy":"usertag","embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/usertag?post=71862"},{"taxonomy":"vertical","embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/vertical?post=71862"},{"taxonomy":"content-category","embeddable":true,"href":"https:\/\/cms-articles.softonic.io\/en\/wp-json\/wp\/v2\/content-category?post=71862"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}