LXGW Neo ZhiSong: a Chinese serif rebuilt from a Japanese Mincho for mainland shapes

What the font is, and the maintenance notice that comes first

LXGW Neo ZhiSong is a Chinese serif font derived from IPAex Mincho and IPAmj Mincho. The project description puts it plainly: it is an attempt to turn a font written in Japanese writing conventions into one using the standardised forms of mainland China.

The notice at the top of the documentation is the most important paragraph for anyone deciding whether to depend on it. The project has entered a stable maintenance period, and the current scope of maintenance is limited to three things: fixing serious defects such as glyph corruption or compatibility problems, adding characters as required when a new Unicode version is released, and updating names and metadata when the branding strategy changes.

It goes on to say that day to day iteration has slowed but that this does not mean the project is finished. New character additions and major adjustments will be evaluated carefully against the evolution of the Unicode standard and real usage needs, but there is no promise of immediate response or adoption. That last clause is the one that matters for planning, because it means you cannot ask for a character and expect it on a date.

The release history shows the cadence that has actually happened. The tags are v1.067 on 2026-08-20, v1.066 on 2026-07-14 and v1.065 on 2026-06-19, and the version numbers are formatted with the year, month and day, so v1.067 is the 26/08/20 release. Two releases in two months is consistent with the stated maintenance scope rather than with active glyph work.

The repository is not archived, the last push came on 2026-10-18, and the primary language is not recorded because the repository contains almost no source code. The top level listing is LICENSE.md, LICENSE_CHS.md, README.md, documentation/ and projects/. That is a font project: the deliverable is a set of outlines, not a program.

The topics are chinese-simplified, font and typeface, which is the honest scope: this is a simplified Chinese font, and the traditional repertoire is a separate question handled below.

The character coverage, and what the Plus variant adds

The character set is described precisely, and the numbers matter if you are typesetting real documents.

The font currently contains 22,000 characters, comprising 20,992 characters in the CJK Unified Ideographs basic block plus scattered characters from the extension A through I blocks.

Within that, it includes the 8,105 characters of the General Standard Chinese Characters table, and adds characters outside the standard tables as needed according to a preliminary table of non-standard characters maintained by the same author in a separate repository.

There is also a Plus variant, LXGW Neo ZhiSong Plus, which completes all of the extension A block on top of the base font, so that the character set reaches the coverage scope of GB 18030-2022 implementation level 2.

So the decision is between two shapes. The base font gives you the full basic block, which covers essentially every character in ordinary simplified Chinese text, and the Plus variant additionally gives you every character in extension A, which is where the rarer and historical characters live. The base block at 20,992 characters is the practical floor for modern Chinese, and extension A is where a name, a place name or a classical text quotation can still fail to render.

The commented-out block in the documentation is a design history worth noting, because it shows what the project deliberately gave up. It lists an original plan with two parts, the first simplified Chinese oriented and the second traditional and variant characters oriented, with checkboxes for the modern Chinese common characters table at 3,500 characters, GB/T 2312-1980, the general standard characters table, the modern Chinese common characters table, and then a second part for Hong Kong and Taiwan common characters including the 4,808 Taiwan education standard common characters, GB/T 12345-1990, BIG5 level 1, traditional forms from the standard characters table, and completion of the 9,810 characters collected by IICore. The final goal listed there was to complete the CJK Unified Ideographs basic block of 20,992 characters plus the other characters in GBK.

That entire block is commented out, and the visible text has moved on to a simplified Chinese scope. The traditional Chinese material moved to the sister font, LXGW Neo XiHei, whose own repository holds the non-standard character tables. So if you need traditional Chinese, the answer is a different font from the same author rather than a different build of this one.

The IPA Font License, and the embedding question the project flags

The licensing is the part that needs actual reading, and the project is unusually direct about the risk.

This project is derived from the IPA fonts and follows the IPA Font License 1.0. The documentation says that if you plan to use the font for embedded purposes you must read the IPA Font License 1.0 terms carefully, and to refer to the embedding notes published in the lxgw repository to assess the compliance cost yourself.

The phrase assess the compliance cost yourself is the point. The IPA Font License is not a permissive open source licence, and embedding is exactly the use case where its conditions bite. The repository carries LICENSE.md and LICENSE_CHS.md, the second presumably the Chinese translation, and the licence identifier in the repository metadata is a custom one that GitHub could not classify, which is what a bespoke licence looks like to a licence detector.

This is worth putting in context. The upstream IPA fonts are the basis, and the derivation is substantial, but the licence travels with the derivation. A web font served to browsers is an embedded use, and so is a font shipped inside an application. For ordinary desktop use the terms are less demanding, but for anything you distribute you need to know what the licence actually requires of you, and the project deliberately does not summarise that for you.

There is a second reason the terms matter here specifically, and it is technical rather than legal. The font covers 22,000 characters, which is a large subset of CJK, and CJK fonts are large. The embedding clause is the one that can turn into an obligation that changes your product. The project's advice to read the embedding notes and evaluate the cost is therefore practical advice, not boilerplate.

For anyone publishing on the web, the alternative is to check whether the derived fonts in this family have a different arrangement, or to use a font whose licence is a standard permissive one. The name of the family, LXGW, is the Lxgw project, and the sibling font documentation is where the embedding notes live.

Beyond Chinese: Greek, Cyrillic, Vietnamese and a pile of symbols

The font is not only a Chinese face, and the non-Chinese coverage is a deliberate set of choices rather than an accident.

The Greek and Cyrillic alphabets were redrawn, with the note that the result is basically consistent in style with the original font's Latin part, which makes it more suitable for modern Greek and Cyrillic typesetting. Displaying Vietnamese Latin characters is newly supported.

The symbol coverage is the more unusual part. The font supports the Yijing bagua and sixty-four hexagram symbols, the eighty-one stanza symbols of the Taixuanjing, mahjong tiles, Chinese chess pieces, counting rods, the zheng tally character, and similar special symbols. These are not decorative extras, they are characters that exist in the Chinese typographic tradition and that most general purpose fonts do not carry, and a reader who needs them would otherwise have to fall back to another font mid-line.

The font also supports Unicode Variation Sequences, used to select the width and position of punctuation marks, with a table of the sequences in the documentation as a PDF. That is a real typographic feature rather than a curiosity, because CJK punctuation has width and positioning variants, and selecting the right one per context is what stops a full stop at the end of a line from sitting in the wrong place relative to the character before it.

The sister font relationship is worth noting for anyone choosing between them. LXGW Neo ZhiSong is the Song style, the serif, and its sister is LXGW Neo XiHei, the sans. The Song style is the traditional Chinese printing face with modulated stroke contrast and triangular serifs, and it is the style that reads as formal and literary, which is why it survives in books where a sans would not be used for body text.

One detail about the overview images is a small lesson in documentation. The samples are rendered in two colours, a pale rice beige and a crane grey, both taken from a collection of traditional Chinese colours. That is presentation, but it is presentation that shows the font the way it is meant to be read, at reading size rather than as a wall of specimen.

Where to get it, and the honest note about the glyph quality

There are five documented ways to obtain the font, and one of them is aimed squarely at people who want to modify it.

The first is the Releases page on GitHub. The second is a Chinese font site, the maoken.com entry, which the README badges link to. The third is another font site, zijia.com.cn. The fourth is a pair of Chinese file hosting services, with a note that the seven-zip archive there contains the TTF font files and a password given for the second one. And the fifth is the projects/ folder in this repository, which contains FCP format font project files so you can do secondary development of the font itself, with two named files, MixMincho-ExtA.fcp holding the extension A block glyphs added for the Plus version and MixMincho-ExtB.fcp which held the original font's extension B glyphs and now mainly provides the compatibility ideograph block. Doing that requires FontCreator 15.0.0.3048 or later.

Shipping the source project files is the unusual and generous part. It means the font is genuinely modifiable rather than a binary you have to take or leave, and the naming reveals the structure of the work, since the base font's glyphs come from a file that is not in the listing at all, and the two FCP files hold the additions.

The last section of the documentation is a note about quality, and it is unusually frank. The author says they are not a professional designer and did not consider aesthetic quality, so the structure may look a little ugly, and a modified character may feel slightly out of place with the original. Because the work was done in a hurry there was not enough time to fine-tune, so the joining of components in some characters is stiff, but it is better than nothing. Feedback on glyph optimisation goes to a specific issue, Issue #2, and urgent requests for added characters are directed elsewhere in the same paragraph.

That note tells you what to expect and what to do. This is a mechanically rebuilt Japanese Mincho reshaped to Chinese conventions, so the awkwardness of a hand conversion is expected, the known problem areas are the composite characters whose radicals were assembled rather than drawn, and the project tells you that Issue #2 is the place to raise them. For a font that has been at version 1.067 and is explicitly in maintenance mode, the honest engineering position is that glyph quality issues are accepted rather than fixed, and the issue tracker is where you would raise them if you care.

Editorial conclusion

LXGW Neo ZhiSong fits a designer or developer typesetting simplified Chinese who wants a Song style face with mainland rather than Japanese glyph shapes, and who is content with the aesthetic of a mechanically rebuilt Mincho. It is the wrong choice if you need a full traditional Chinese repertoire, since the base font covers the CJK Unified Ideographs basic block with only scattered characters from the extension blocks, and it is the wrong choice for anything embedded in a product until you have read the IPA Font License and the embedding notes. Before shipping it, check the licence terms for embedding specifically, and if you need the full extension A block, use the Plus variant rather than the base font.

Frequently asked questions

Official sources

1. Issues
2. lxgw/LxgwNeoZhiSong on GitHub
3. README
4. Releases