LXGW Bright: one Han font with three regional glyph sets and a Latin companion

A Latin family and a Han family welded into one file

LXGW Bright is a merge, and the merge is the whole idea. The project description says it is a merged font of Ysabeau and LXGW WenKai, and the documentation adds the tooling detail: the two families were combined with the Warcraft Font Merger tool. The result is a single family that carries Han glyphs and Latin glyphs in the same file, which solves a practical problem for bilingual documents. Setting Chinese and Latin text in two unrelated typefaces produces mismatched weights, different x heights and an uneven colour on the page, and a merged family sidesteps that because both scripts share one weight axis and one set of metrics. The audience is writers and designers working in mixed Chinese and Latin text, typically on the web or in long form documents. The output ships in TrueType and WOFF2 format, and the repository keeps the built fonts in three top level directories, one per glyph variant, alongside the OFL.txt licence file and a set of preview images.

Three glyph sets aimed at three kinds of Chinese text

The project offers three variants, and the difference between them is which regional glyph shapes are used, not which characters are covered. LXGW Bright proper takes its half mainland-standard forms from LXGW WenKai Lite, and keeps the print characteristics of that source, things like straight dots and broken strokes that separate it from a handwriting style. LXGW Bright GB takes the mainland standard forms from LXGW WenKai GB, and fills any characters that source lacks from LXGW WenKai Lite. LXGW Bright TC takes traditional forms from LXGW WenKai TC. All three use Ysabeau Office for the Latin part, and the reasoning given is that Ysabeau's old-style figures do not sit well next to Han characters, while Ysabeau Infant leans towards handwriting and this family is deliberately print oriented. For a reader, the practical question is which script conventions your source text follows, since the same string of characters will render with visibly different shapes depending on which directory you install.

Only three weights, and the weight axis is not the fonts' own

Weight coverage is narrow on purpose. The documented mapping between the upstream families and the merged family runs Light, Regular and Medium, and it is stated that the weight settings follow Ysabeau Office, which is also how LXGW WenKai is set up. There is no Black, no Thin, no SemiBold in this family, so if your design calls for a heavier display weight you will need a different face. The narrower range also has a practical consequence for pairing: because the merged file is generated from both upstreams, a change on either side moves the merged family, and the version numbering exists to make that visible. The document also points out a small typographic aside, that Ysabeau's old-style numerals are the reason the Latin part was swapped for the Office variant, since lining figures mix badly with Han text at small sizes.

The version number is an arithmetic sum of two upstreams

Release tags for this project look unusual, and the explanation is given plainly: in general the release version number is the Ysabeau Office version plus the LXGW WenKai version plus 2. The plus two comes from the merge itself. Because the GB, TC and Lite variants of LXGW WenKai all update at the same time, their numbers are not counted separately, so the tag tracks the two upstreams that actually change the output. The release history shows tags such as v5.528, v5.527 and v5.526, with dates spread across 2025 and 2026, the most recent being 2026-03-23. Installation is a download rather than a build: the documentation points you at the Releases page on the project repository, where the packaged font files are published, and there is no build step to run and no package to install. The same cadence appears elsewhere: the project states it updates within one month of a LXGW WenKai series release, and the Magisk module distributed through the linked cloud storage is updated within 48 hours of a project update. The last push to the repository was on 2026-06-24.

Three things the project refuses to ship

The documentation opens with a set of exclusions that matter more than any feature list, because they tell you where the font will fail you. First, the font is not suitable for vertical typesetting. Second, the OTF version is no longer provided, and has not been since v5.330, because OTF rendering had problems. Third, there is no full character set version. The stated reasons are that the full set would be inconvenient to embed in applications, and that the complete LXGW WenKai contains a large number of rough glyphs generated by AI, so it was left out of this derivative. There is also a related project rather than a variant here: the monospaced build is planned to pair with Monaspace Argon and will be named LXGW Bright Code, with its own repository, so if you need fixed width Latin you are looking at a separate download rather than a toggle in this one.

SIL OFL 1.1 terms that constrain derivative work

The licence is SIL Open Font License 1.1, and the font is built on three open projects, Klee, LXGW WenKai and Ysabeau. The permission side is generous: personal and commercial use is allowed with no fee, no obligation to notify the author, and no requirement to credit the author, though credit is welcome. Redistribution, sharing, installing the font into a system, a piece of software or an app, bundling it with other software, and selling it as part of a larger product are all permitted. Modification and derivative fonts are allowed as well. The restrictions are the standard OFL ones and they are worth reading carefully if you plan to fork. A derivative font cannot reuse the reserved name of the original. The font file itself may not be sold on its own as an OTF or TTF, which is the clause that trips up people selling single font files. And the font may not be distributed under any licence other than SIL OFL 1.1, so a derivative has to keep the same licence.

Where LXGW Bright is the wrong choice

The exclusions from the documentation become concrete failures in real projects. If your publication needs vertical text, this family simply cannot set it, and the documentation says so without offering a workaround. If your application embeds a font and needs a broad character coverage for user generated content, the absence of a full version is a hard stop, because you would have to source the missing glyphs elsewhere and then deal with the OFL terms of that source. If your pipeline is built around OpenType CFF outlines, the lack of OTF files forces a conversion or a change of pipeline. And if you need a heavy weight for a poster or a title, three weights do not get you there. On the positive side, the family is a good fit for bilingual reading and writing on screen, and one application is documented as using it as its default font, a mobile writing app listed under the name Pure Writer.

Editorial conclusion

Choose LXGW Bright if you write Chinese and Latin in the same document, want a print oriented typeface rather than a handwriting one, and need the three regional glyph sets available under one name with a permissive licence. Do not pick it for vertical typesetting, for embedding in an app that needs the full character set, or for workflows that require OTF files, since all three are excluded by the project on purpose. Verify first which of the three glyph sets your text needs, and check the version arithmetic in the release page, because the tag number is a sum of two upstream projects rather than a straightforward sequence.

Frequently asked questions

Official sources

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