Zhuque Fangsong: an open source Fangsong typeface built on a 1932 letterpress original

What Zhuque Fangsong solves, and who it is for

Chinese typography treats Song, Hei, Fangsong and Kai as the four basic categories. Fangsong has the thinnest open source presence of the four. The README states this directly: Fangsong has long lacked choices under an open licence, and the project exists to fill that gap for open source software and the TeX community. That is the audience. People setting Chinese books, academic PDFs, journal layouts or documentation in LaTeX, and anyone who needs a body-text face that is neither a Song nor a Hei, and who cannot license a commercial Fangsong.

The design target is narrower than "a Fangsong". Most Fangsong on the market descend from a single lineage, Huafeng Zhensong, which is the shape most readers recognise today. Zhuque Fangsong instead recuts Nansong, a Republican-era metal type released in 1932 by the Baisong Type Casting and Printing Bureau, with the original drawings by Han Youzhi and the punches cut by Zou Genpei. The README describes Nansong's traits: the optical centre sits slightly low and to the right, the inner counters are tight, the pie and na strokes extend freely, and stroke weight varies strongly. The project reduces that stroke contrast somewhat and regularises the structure while keeping what the README calls the face's scholarly quality.

So the fit is specific. If you want a neutral, familiar Fangsong, this is deliberately not that. If you want a body face with visible letterpress character and you are willing to track a pre-release project, it is aimed at you.

How the project is organised and how releases are produced

The repository is small at the top level: .github/, docs/, src/, LICENSE.txt, README.md and .gitignore. There is no build system described in the README, no compiler invocation, and no documented pipeline that turns source into a shipping font. The README points readers to the Releases page for versions and download links, and mentions an AtomGit mirror repository. That is the whole distribution story as documented.

What the README does describe is the production method. TrionesType says it is testing a new design mode for Chinese typefaces in which designers use AI directly as a design tool, which lets the team develop Zhuque iteratively. The README is explicit that this is an experiment in process, not only in output. A survey was run during the testing phase; 335 people responded and 72 professional opinions were counted as valid, and the results informed both the shapes and the planning of later work. The survey conclusion is linked from the repository.

The team list separates roles: Yu Junyi as lead designer, Han Yongsi on kana and symbols, and Yin Yehang, Yu Junyi and Li Jianqiao on production. Kana and symbol work being a named role matters, because the project's stated goal is a multilingual body Fangsong, not a Chinese-only one. The README also credits Siphercase for adding some International Phonetic Alphabet glyphs, and names Lxgw WenKai, Fontworks Klee One and Source Han Serif as writing references used during design. Those are references for the human and machine process, not source material merged into the font.

Getting the font and setting it in a document

There is no package manager step and no installer. The README gives exactly one place to get builds: the Releases page on GitHub, with an AtomGit mirror repository listed as well. Download the font file from the release you want, then install it the way your operating system installs any font file. On macOS and Windows that is opening the file and confirming the install; on Linux it means placing it in the user font directory and refreshing the font cache.

The README does not publish a LaTeX, CSS or CLI example, and it does not document a build command, so there is no project-supplied snippet to copy. What follows is what the README does tell you about getting the font into use, without inventing commands.

The only documented source of the font is the Releases page, and the README also lists an AtomGit mirror repository at atomgit.com/TrionesType/zhuque. Download the release file from one of those two places, then install it the way your system installs a font file. Once installed, the font is referenced by the family name the file reports to the operating system, which is the name you will type into LaTeX, CSS or a desktop application. The README does not state what that family name is, so check it in your font manager rather than assuming.

What you should see, once the font is applied, is a body face with tighter counters and stronger stroke contrast than a typical Song, with the low-right optical centre the README describes. If the Latin letters look like a serif with a distinctly different temperament from the Chinese, that is expected: the README states the Western letters and symbols currently use Alegreya, by Juan Pablo del Peral of Huerta Tipográfica, also under OFL 1.1.

It is pre-release, and the README says so

The licence section contains a request that is unusual enough to quote: the project asks readers not to widely circulate versions of the font modified by anyone other than the Zhuque team before the official release. That is a request, not a licence term, and it does not restrict what OFL 1.1 permits. But it tells you how the maintainers view the current builds. They are iterations, not a finished family.

The practical consequence is that glyph coverage and shape quality are moving. The README frames the whole project as an experiment in an AI-assisted design method, and the survey was run precisely to guide later work. A release you embed today may not match the next one. There is no documented versioning policy, no compatibility promise, and no statement about how glyph sets change between versions.

There is also a gap in the documentation that matters for adoption. The README does not document a build process, so you cannot reproduce a release from src/ by following the repository. It does not document rollback, so if a new release regresses a glyph you rely on, the README gives you no path back other than downloading the older release yourself. And it does not state how many glyphs a given release contains. If your text includes rare characters, variant forms or a non-Chinese script, you have to test the actual file rather than trust a coverage figure, because no coverage figure is given.

Finally, the Latin is a dependency, not part of the design. Alegreya is a good face, but it was not drawn to sit with Nansong's low optical centre. If you need a matched Latin, you are assembling a font stack, not adopting a family.

Zhuque Fangsong against Source Han Serif and Lxgw WenKai

The obvious alternatives are the open source CJK faces the README itself names as references. Source Han Serif, from Adobe, is a Song face with an enormous, well-documented glyph set and a stable, long-published release process. If your requirement is coverage and predictability, Source Han Serif wins on both, and it is a Song, so it will not give you Fangsong stroke behaviour at all. Choosing between them is choosing a category, not a quality tier.

Lxgw WenKai is closer in spirit: it is a Kai face, and it also carries a strong historical temperament rather than aiming at a neutral default. The difference in approach is the source of the shapes. WenKai derives from an existing open font lineage and extends it, which is why its release history is easier to reason about. Zhuque Fangsong recuts a 1932 metal type and is explicit that AI tools are part of the design method, which is why its README describes an ongoing experiment rather than a settled product. If you want a Kai with a long track record, WenKai is the safer pick. If you specifically need Fangsong, and specifically the Nansong lineage rather than the Huafeng Zhensong one that dominates the market, neither alternative substitutes for this project.

That is the honest boundary: Zhuque Fangsong is not competing on coverage or release discipline with Source Han Serif. It is competing on being the open Fangsong with this particular historical source.

Licence terms and what they mean for shipping

Zhuque Fangsong is released under SIL Open Font License 1.1, and the README states the English text of the licence is authoritative. The README's own summary of what you may do is broad: commercial use of the font is permitted, including print, logos, software, web pages, video and embedding in software, and you may copy and redistribute the font. What you may not do, per the README, is sell the original or modified font on its own.

That last point is the one to read carefully in the licence itself rather than the summary, because OFL 1.1 has specific conditions around selling and around reserved font names. This is not legal advice and the README points to the licence text for a reason. If you are embedding the font in a product, redistributing it, or modifying it, read LICENSE.txt and the OFL text, and check whether any reserved font name applies to the release you are using.

The Alegreya component is a separate work under the same licence, by a different author. If you modify or redistribute the font, that component carries its own attribution history. The README credits it explicitly, and keeping that credit is the straightforward path.

On upgrade cost: the maintenance burden is low in the normal case, because installing a newer release is replacing a file. The cost that is not low is verification. Because no coverage figures are published and no build process is documented, every upgrade means re-checking the characters your document actually uses, plus the Latin behaviour, plus any layout metrics that shifted when the Chinese shapes changed.

Where the project stands

The repository is not archived. The last push was on 2026-07-23, which is recent enough that the project is still being worked on. The most recent release listed is v0.212 from 2025-07-07, following v0.211 and v0.210 in December 2024. The version numbers are still in the 0.2xx range, which is consistent with the README's own framing of pre-release iterations.

What is documented is a design argument and a licence. What is not documented is a build, a coverage table, a versioning policy, or a rollback path. Anyone evaluating this font should treat the Releases page as the source of truth for what exists, and the README as the source of truth for what the project intends. The two are not yet the same thing, and the README says as much when it asks readers to hold off on spreading modified versions before the official release.

Editorial conclusion

Adopt Zhuque Fangsong if you need a body-text Fangsong under a permissive font licence for print, web, video or embedding, and you accept that the project is still pre-release and that the README asks you not to spread modified versions widely before the official release. Do not adopt it if you need a finished, frozen family, a variable font, or a face with a Latin component you control: the Western letters and symbols currently come from Alegreya. Before shipping anything, check the Releases page for the current version, read LICENSE.txt rather than the README summary, and confirm which glyph coverage the release you downloaded actually contains.

Frequently asked questions

Official sources

1. Issues
2. License: OFL-1.1
3. README
4. Releases
5. TrionesType/zhuque on GitHub