Skip to content

Instantly share code, notes, and snippets.

@tkanai
Last active November 10, 2015 06:33
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save tkanai/c9d64283ae14ecc5250f to your computer and use it in GitHub Desktop.
Save tkanai/c9d64283ae14ecc5250f to your computer and use it in GitHub Desktop.
CJK Font rendering gaps
<html>
<head>
<meta charset="utf-8">
<style type="text/css">
tr:nth-child(2){
background: skyblue;
}
</style>
</head>
<body>
<h2>1. Gaps between CJK glyphs</h2>
<p>Unicode Han characters, Kanji in Japanese, show different rendering results depending on local system settings. It is not just showing unfamiliar glyhs, but also showing identical glyphs with other codes, sometimes. For example, almost all Japanese would interpret the Chinese U+624d glyph as Japanese "オ" (Katakana, U+30AA), and get confused.</p>
<table>
<tr><th>language settings</th><th>U+5284</th><th>U+5784</th><th>U+585a</th><th>U+4e0e</th><th>U+624d</th></tr>
<tr><td>n/a (default)</td><td>劄</td><td>埴</td><td>塚</td><td>与</td><td>才</td></tr>
<tr lang="zh-CN"><td>Simplified Chineese (zh-CN)</td><td>劄</td><td>埴</td><td>塚</td><td>与</td><td>才</td></tr>
<tr lang="zh-TW"><td>Traditional Chinese (zh-TW)</td><td>劄</td><td>埴</td><td>塚</td><td>与</td><td>才</td></tr>
<tr lang="ja"><td>Japanese (ja)</td><td>劄</td><td>埴</td><td>塚</td><td>与</td><td>才</td></tr>
<tr lang="ko"><td>Korean (ko)</td><td>劄</td><td>埴</td><td>塚</td><td>与</td><td>才</td></tr>
</table>
<h2>2. The currency sign issue (specific to Windows)</h2>
<p> The Unicode character 'REVERSE SOLIDUS', a.k.a. backslash, is rendered as Japanese Yen sign on Japanese Windows PC, and the same code is rendered as Korean Won sign on Korean Windows PC.</p>
<table>
<tr><th>language settings</th><th>(U+005c) 1000</th></tr>
<tr><td>n/a (default)</td><td>\1000</td></tr>
<tr lang="ja"><td>Japanese (ja)</td><td>\1000</td></tr>
<tr lang="ko"><td>Korean (ko)</td><td>\1000</td></tr>
</table>
</body>
</html>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment