{"id":254,"date":"2010-05-26T08:22:49","date_gmt":"2010-05-26T08:22:49","guid":{"rendered":"http:\/\/dev.gregbueno.com\/wp\/sakufu\/2010\/05\/26\/google_chromium\/"},"modified":"2010-05-26T08:22:49","modified_gmt":"2010-05-26T08:22:49","slug":"google_chromium","status":"publish","type":"post","link":"https:\/\/gregbueno.com\/sakufu\/2010\/05\/26\/google_chromium\/","title":{"rendered":"Google Chrome can&#8217;t handle this site, or why you gotta be difficult all your life?"},"content":{"rendered":"<p>Back when social media sites were cropping up left and right, I had a test to determine whether it could handle my more esoteric interests: Does it support Japanese characters?<\/p>\n<p>I signed up with Twitter a good six months before it took off at SXSW in 2007, and one of the first things I did was tweet in Japanese. Success! I signed up with Grooveshark around the same time and tried to share some upload some music tagged in Japanese. I saw question marks where there should have been text. Failure.<\/p>\n<p>Google Chrome is gaining market share, and even I have to admit I like its speed. But one thing prevents me from adopting it &#8212; it can&#8217;t handle the Japanese characters on my site.<\/p>\n<p>That&#8217;s not to say it can&#8217;t handle Japanese &#8212; I can visit <a href=\"http:\/\/www.hmv.co.jp\/\">HMV<\/a> with no problems, but <a href=\"http:\/\/www.tower.jp\/mag\/bounce\/\">Bounce<\/a> looks totally messed up.<\/p>\n<p><!--more--><\/p>\n<p>This case isn&#8217;t simply about installing a language pack and selecting the correct encoding &#8212; I&#8217;ve done all that because I visit sites in Japanese all the time.<\/p>\n<p>If you&#8217;re viewing this site on Google Chrome, you already see a number of these inconsistencies. First, the header of my site, which is named \u300c\u4f5c\u8b5c\u300d, is completely missing, although the &lt;h1\/&gt; space for it is allocated. But &quot;About this blog&quot; renders the blog name just fine.<\/p>\n<p>The side bar ought to have links to this site and my &quot;creative scrapbook&quot;, \u300c\u540d\u4f5c\u8a18\u300d, but they are gone. Trying to reproduce the errors is proving elusive. Here&#8217;s how the side bar is supposed to look like under the &quot;Links&quot; section labeled &quot;personal&quot;:<\/p>\n<p><a href=\"\/index.php\/sakufu\/\" title=\"A neglected blog\">\u4f5c\u8b5c<\/a><\/p>\n<p><a href=\"\/index.php\/meisakuki\/\" title=\"A creative scrapbook\">\u540d\u4f5c\u8a18<\/a><\/p>\n<p><a href=\"http:\/\/www.austin-stories.com\/\" title=\"An online journal portal\">austin stories<\/a><\/p>\n<p>It renders fine in this entry, doesn&#8217;t it?<\/p>\n<p>I&#8217;ve coded this site on the back end to do a bit of string processing to account for paragraph and line breaks, so while it&#8217;s a syntactic replica of the problem text, it&#8217;s not rendered the same way. But I suspect even if I do replicate the markup, encoding and response headers, I won&#8217;t get the same results.<\/p>\n<p>I&#8217;ve already sent bug reports through Chrome about this issue, and it&#8217;s been a persistent problem since the browser launched.<\/p>\n<p>It would probably help if I didn&#8217;t make such weird demands on browsers with all this mixed language content. Why must I be so difficult?<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Google Chrome is gaining market share, and even I have to admit I like its speed. But one thing prevents me from adopting it &#8212; it can&#8217;t handle the Japanese characters on my site.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[6],"tags":[],"class_list":["post-254","post","type-post","status-publish","format-standard","hentry","category-technophilia-professional"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p4Bkjq-46","_links":{"self":[{"href":"https:\/\/gregbueno.com\/sakufu\/wp-json\/wp\/v2\/posts\/254","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/gregbueno.com\/sakufu\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/gregbueno.com\/sakufu\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/gregbueno.com\/sakufu\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/gregbueno.com\/sakufu\/wp-json\/wp\/v2\/comments?post=254"}],"version-history":[{"count":0,"href":"https:\/\/gregbueno.com\/sakufu\/wp-json\/wp\/v2\/posts\/254\/revisions"}],"wp:attachment":[{"href":"https:\/\/gregbueno.com\/sakufu\/wp-json\/wp\/v2\/media?parent=254"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/gregbueno.com\/sakufu\/wp-json\/wp\/v2\/categories?post=254"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/gregbueno.com\/sakufu\/wp-json\/wp\/v2\/tags?post=254"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}