4

Does anyone know of a font that supports the unicode CJK extensions c, d, e? If you have such a font, do you know if it works with the MySQL utf8mb4 character set?

wpt
  • 4,355
  • 14
  • 24

1 Answers1

7

The Hanazono fonts (HanaMinA, HanaMinB) have full support for all 3 extensions and include 96k+ glyphs. Here is the glyph list (.pdf, 500 pages).

Babelstone Han claims to support all glyphs in Extension D, but only has partial support for C (37.1%) and E (19.5%).

EDIT:

Here's the download link (25.7MB) for HanaMinB (which supports these extensions). And here's a screenshot of a word processor with HanaMinB.ttf installed, displaying random glyphs from CJK Ext. E.

enter image description here

imrek
  • 7,188
  • 2
  • 21
  • 33
  • Hanazono really supports CJK-E? – Mou某 Jul 09 '15 at 07:21
  • @user3306356 See the screenshot in my updated answer. – imrek Jul 09 '15 at 08:53
  • Great font, but I'm still having trouble with Ext. E. After installing HanaMin A & B in Windows 7, I can now see the Ext. C and Ext. D glyphs in Wikipedia (using Firefox 39). However, I'm still unable to see any of the Ext. E glyphs on Wiki. In addition, when I go to the Unihan database, I can only see glyphs up to 2A6DF (i.e. Ext. B); C, D, and E don't show at all. I'll keep fiddling with it; any ideas? – wpt Jul 09 '15 at 09:18
  • Have you tried restarting your browser? I assume, yes. Open this page: https://en.wikipedia.org/wiki/CJK_Unified_Ideographs_Extension_E , right click on any of the glyphs in the table and select "Inspect Element" from the context menu. Check the font on the 'Fonts' tab. – imrek Jul 09 '15 at 09:36
  • Yes, shutdown and restarted computer to be sure. Inspect element shows HanaMinB font for glyphs in ext. c and d tables in wiki, but 'arial' for ext. e. How come? Also, tried to copy text to Word (2003), b ext is fine, but c, d, and e are no good. Same for copying to mysql tables (server 5.5.39) – wpt Jul 09 '15 at 10:00
  • 1
    Well, I can't reproduce the error, I am running Linux and things are fine. – imrek Jul 09 '15 at 10:26
  • Hm. Tried Chrome and IE 11 and the same story. Wonder if I have some sort of font conflict? I tried changing the default font for x-unicode in Firefox to HanaMin B; no soap. Anyone else got suggestions? – wpt Jul 09 '15 at 13:01
  • Have you tried Default font: serif? The wikipedia page with the CJK-E table is using font-family: sans-serif, on Windows your fallback font is probably a sans-serif one, like Arial. I have no idea if that should fall back to anything else on Windows, but it does resort to HanaMinB system in my browser. I haven't modified any font settings in Firefox. – imrek Jul 09 '15 at 13:12
  • 1
    It seems to be an individual problem for my system. Anyway, I'm sure this is the solution for most people – wpt Jul 10 '15 at 02:54
  • Mac OS X, Safari & Chrome: all are fine. – Stan Jul 10 '15 at 03:06
  • CJK Unified Ideographs Extension E is part of Unicode 8.0, it is not implemented in OS X, neither 10.10 Yosemite nor 10.11 El Capitan. Therefore, it does not show up, since it is not recognized by the system.

    However, a few characters in Extension E do show up, using Noto Sans CJK fonts. A contradiction in terms, but it may have to do with how these fonts are coded.

     –  Jul 10 '15 at 09:51
  • @倪阔乐 I'm using Yosemite, why can I see all the characters on this page? (I've installed HanaMin before.) – Stan Jul 10 '15 at 10:13
  • @Stan: I don't know, I am guessing it is not HanaMin but another font. Open TextEdit, Go to Edit/Emoji & Symbols, choose Unicode and scroll down the list. You will see that extensions B, C and D exist, followed by Compatibility Ideographs Supp. Extension E is not defined. Copy the first character of the wiki page and see if you can render it using HanaMin in TextEdit. I strongly believe it is another font rendered. –  Jul 10 '15 at 13:54
  • @倪阔乐 I tried, and the result showed in TextEdit HanaMinB could correctly display ext E characters. (Maybe you want to verify this by yourself?) Yes ext E isn't defined in "Emoji & Symbols", but it doesn't mean Unicode within that area cannot be tackled by the system -- that may be why we can see "squares" if no font provides a glyph on the specific Unicode code points. – Stan Jul 10 '15 at 15:00
  • 1
    @wpt I had the same problem, it turned out I had an old version on HanaMinA and HanaMinB installed on my computer! it was from '13 or something like that - the newest version is from '14 - I downloaded the newest version and everything was hunky doory – Mou某 Jul 15 '15 at 15:00
  • 1
    Yop, that's right, works just fine with the newest version, must have gotten the old version at scourgeforge. –  Jul 22 '15 at 14:54