# LXGW WenKai GB for Simplified Chinese Typography > LXGW WenKai GB is an OFL-1.1 Simplified Chinese font derived from Klee One, with mainland-oriented glyph revisions and broad Unicode coverage. It suits everyday text that values standard forms, but the project warns against demanding educational publishing uses. **lxgw/LxgwWenkaiGB** — An open-source Simplified Chinese font derived from Klee One. - Repository: https://github.com/lxgw/LxgwWenkaiGB - Stars: 1,569 · Forks: 36 - Language: Shell - License: OFL-1.1 - Published: 2026-10-16 · Updated: 2026-10-16 · Language: en - Canonical page: https://hysenlabs.com/projects/lxgw-lxgwwenkaigb ## Why LXGW WenKai GB Exists LXGW WenKai GB addresses a specific gap between visual character and regional language standards. It began with Klee One, an open-source Japanese font from FONTWORKS, then continued through the earlier LXGW WenKai project. The GB edition modifies forms within GB/T 2312-1980 and the scope of the Standard Form Table of Modern Chinese, aiming for glyphs closer to conventions used in mainland China. This is not simply a renamed upstream build. The project further adjusts forms and strokes using the Standard Form Table of Modern Chinese and the education ministry's GF 0023-2020 stroke-order specification. The intended users are people producing modern Simplified Chinese text who care about normalized regional forms, especially developers embedding a Chinese font in an application or teams preparing ordinary documents. The complete edition contains 8,105 characters from the 2013 Standard Form Table of Modern Chinese, 7,000 from the 1988 table, and 6,763 covered by GB/T 2312-1980. It also adds some frequently requested characters outside those sets. That positioning comes with a blunt warning. The authors do not consider this a universal standard Kai font. They retain stylistic differences from conventional Kai calligraphy, including inherited treatment of enclosing components and the absence of a distinction between hanging-needle and dewdrop vertical strokes. The README specifically says it may be unsuitable for compulsory-education books, children's reading, and copybooks where glyph correctness is held to a very high standard. ## How the GB Glyph Revision Differs The font retains recognizable elements of Klee One's printed style. Its modifications are regional rather than stylistic. Earlier LXGW WenKai forms were brought closer to mainland Chinese conventions, while features such as direct dots and interrupted stroke corners could still conflict with ordinary Kai writing habits. LXGW WenKai GB pushes the revision further in an attempt to remove more of those traditional printing features. Coverage expands beyond the central Simplified Chinese use case. Since v1.0, the project has added traditional and IICore Chinese support. Since v1.320, its stated collection has covered the complete CJK Unified Ideographs block and Extension A, which corresponds to the character collection level described for GB 18030-2022 implementation level 2. It also includes the complete set of Hangul syllables recognized by Unicode at the time of the documentation, JIS X 0213 characters, Adobe-Japan1-6 mappings, selected seal-script characters, and additional forms retained from named character tables. The expanded repertoire should not be mistaken for uniform typographic authority. The README says about 1,000 CJK glyphs in the full edition were produced by zi2zi deep learning and therefore have coarser forms. Japanese-oriented characters retain Japanese forms rather than being inferred into Chinese forms. For serious publishing, this mixed coverage is a boundary that must be checked against the exact document, not treated as interchangeable with every other font carrying the same names. ## Downloading and Installing a Release The README's primary installation path is a prebuilt TTF file from the project's GitHub Releases page. Choose a release, download its TTF, and install it through the font controls of the target operating system. The documentation does not provide operating-system-specific installation commands, so none are invented here. After installation, select "霞鹜文楷 GB" in a word processor, browser, design application, or application that accepts system fonts, then type a representative Simplified Chinese sentence. The documented mirror sites are 永硕 E 盘个人下载站 and 蓝奏云, with password `e0zt`. The README says these mirrors update within 48 hours after a project update. 猫啃网 and 字加 are also listed, although their updates may arrive later. Other sites may carry older builds, so a release downloaded from one of them should be checked against the GitHub release before deployment. A first production check should include the actual text, not only the font name. Review common Han characters, punctuation width, punctuation position, Latin `I` and lowercase `l`, and any rare characters used by the application. The project changes lowercase `l` to Klee One's straight form for Chinese pinyin conventions and gives uppercase `I` crossbars so it is more distinct from lowercase `l`. ## Building WenKai from Source on Unix Source builds are documented for Unix-like systems with Python 3 and the `LxgwWenKai-shared` submodule. The repository declares `fontmake`, `fontbakery`, `gftools`, `ufomerge`, and `tzdata` in `requirements.txt`. The documented build command creates a virtual environment, installs those dependencies, merges source data, exports the font, and runs a post-processing script. From the repository root, run the complete documented target: ```bash make build ``` The resulting font files are placed in the repository's `fonts/` directory. According to the Makefile, `make build` depends on `venv`, `merge`, and `export`. The virtual environment target creates `venv/` with Python 3 if needed, activates it, and installs the requirements. The source workflow also exposes separate targets, but the README only documents `make build` as the complete process. Its middle stages run the merge script and invoke `gftools builder sources/project.yaml` before the final Python post-processing step. Use the complete target unless you specifically need to reproduce one stage of that pipeline. ## Unicode Variation Sequences and Punctuation One technically useful feature is support for Unicode Variation Sequences, abbreviated UVS in the README. For this font, that support is used to select alternative widths and positions for punctuation. The project publishes a separate `documentation/uvs.pdf` table, which is more useful for adoption than the fact of support alone. A typesetting system must be able to send the appropriate variation selector if the intended alternate punctuation form is to appear. This is a narrower capability than broad OpenType shaping support. The README says `mark` and `mkmk` complex layout behavior is not planned because it would require complicated OpenType scripts and increase rendering risk. Those features matter for positioning combining marks, including Latin accented letters and Indic text. Their absence does not directly block ordinary Simplified Chinese paragraphs, but it narrows the font's suitability as the principal font for multilingual material. Variable fonts are also outside the stated development plan. The project attributes this to unresolved outline compatibility, node interpolation, and weight-axis design work, as well as the maintainer's lack of variable-font experience. Community derivatives may offer different weight strategies, but those are separate projects and should not be attributed to LXGW WenKai GB. ## Licensing, Distribution, and Organizational Review The repository identifies `OFL-1.1`, and the root includes `OFL.txt`. That matters for organizations and theme stores because the README documents practical problems beyond casual font installation. It warns that sellers on platforms such as Taobao and Xiaohongshu have been reselling font files in ways the author considers inconsistent with the restriction on selling the font files by themselves. Such purchases may provide neither an update path nor support. The README goes further than a general license reminder. It advises organizations whose legal departments do not recognize OFL-1.1, or require a conventional authorization certificate, to choose another freely usable font that can provide the requested documentation or a commercial font. It also says domestic mobile-brand theme stores commonly permit font uploads only to enterprises, while some stores accepting individual submissions may demand copyright-registration evidence. The author notes uncertainty around ownership in derivative open-source font work. This is not a declaration that the font is unusable. It is a warning that an open-source file and an organization's procurement requirements may not align. Before embedding it in a product, website, application bundle, or theme submission, administrators need to match the planned distribution method to the actual license and obtain whatever internal confirmation their submission channel requires. ## Release Cadence and the Full-versus-Lite Choice The repository is not archived, and its last push was on 2026-10-16. Recent release records include `v1.530-rc1` on 2026-10-13, `v1.522` on 2026-03-17, and `v1.522-rc4` on 2026-03-13. This recent activity does not remove upgrade work. Font files can be embedded in applications, websites, operating-system images, documentation themes, and design source files, so replacing one release can require rebuilding products and checking text layout again. The complete edition is the broad choice when coverage beyond common Simplified Chinese matters. For application embedding, the project offers a separate LXGW WenKai GB Lite edition that removes less common characters. The README identifies Lite as the easier option for applications, but it does not provide a universal size threshold or a formal rule for deciding which characters are safe to remove. Teams should compare their own content against Lite's character inventory rather than rely on the word "Lite" as a guarantee. Upgrades also deserve glyph review because the project's purpose is continuing adjustment toward mainland Chinese forms. A new release may change more than packaging. Product owners should keep the chosen release, its source, and its license text together, then validate affected interfaces and documents before replacing an existing file. ## Conclusion Adopt LXGW WenKai GB for Simplified Chinese interfaces, documents, and applications that value mainland-oriented glyphs without claiming absolute typographic compliance. Do not choose it as the sole font for school books, children's material, or calligraphy copy. Verify the required character coverage, glyph standards, target platform embedding rules, and whether downstream users will recognize OFL-1.1 before publishing the font. ## FAQ ### How do I install LXGW WenKai GB on Windows or macOS? The README directs users to download a TTF file from the project's GitHub Releases page. It does not document operating-system-specific commands, so the TTF must be installed through the font controls of the chosen system and selected from the target application. ### Can I build LXGW WenKai GB from source? Yes. The README documents `make build` for Unix-like systems with Python 3 and the `LxgwWenKai-shared` submodule. The build installs the packages in `requirements.txt` and places the resulting fonts in the `fonts/` directory. ### Is LXGW WenKai GB suitable for Chinese school textbooks? The README says it may not be suitable for compulsory-education books, children's reading, or copybooks because some details remain different from standard Kai forms and some stroke distinctions are absent. Teams with strict publishing requirements need a font whose compliance process matches that requirement. ### What is the difference between LXGW WenKai GB and Lite? The complete edition includes the broadest documented character collection, including the complete CJK Unified Ideographs block and Extension A. The Lite edition removes less common characters and is intended to make application embedding easier. ### Does LXGW WenKai GB support variable weights or complex mark positioning? The project lists variable weight support and `mark` or `mkmk` complex layout behavior as features it does not plan to support. It does support Unicode Variation Sequences for punctuation width and position selection. ## Sources - [Issues](https://github.com/lxgw/LxgwWenkaiGB/issues) - [License: OFL-1.1](https://github.com/lxgw/LxgwWenkaiGB/blob/main/LICENSE) - [lxgw/LxgwWenkaiGB on GitHub](https://github.com/lxgw/LxgwWenkaiGB) - [README](https://github.com/lxgw/LxgwWenkaiGB/blob/main/README.md) - [Releases](https://github.com/lxgw/LxgwWenkaiGB/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/lxgw-lxgwwenkaigb