Axismundi Japanese Font Provider
Active Installs
0+
Last Updated
September 18, 2026
First Released
August 22, 2026
Download History (Last one month)
Contributors
Axismundi Japanese Font Provider supplies the Noto Sans JP and Noto Serif web fonts and fills the Axismundi theme’s regional CJK fallback slot for
JP
Japanese-language content (lang="ja", on the document root or an inline
subtree).
Two roles:
- Provider. On activation the plugin enqueues
@font-facerules (front end
and block editor) for the two families. For Japanese-tagged content it sets the
theme’s--axismundi-cjk-sans/--axismundi-cjk-serifslots. Latin keeps
rendering in Roboto Flex / Roboto Serif because the theme lists Roboto ahead of
the slot. - Font Library collection. The families are also registered as the
“Axismundi Japanese Font Provider” collection. The Japanese fallback above works
without installing anything. Installing from the collection adds a separate
font limited to the same Japanese character range, for places where you choose
it; it does not recreate the theme’s Roboto Flex / Roboto Serif fallback stack.
Because the slot is keyed on :lang(ja), this plugin coexists with the Korean
(and future Chinese) regional packages without competing in a fixed font-family
list: each language run resolves to its own regional font, so shared CJK
ideographs render in Japanese glyph forms on Japanese text. Without any regional
plugin the Axismundi theme falls back to the operating system’s CJK font.
This plugin bundles no tracking and contacts no external service.
Copyright
Axismundi Japanese Font Provider, Copyright 2026 KIM JIWOON.
Plugin code is distributed under the GNU General Public License, version 3 or
later.
This plugin bundles the following third-party resources:
Fonts
The original font files were converted and subset to WOFF2 for Japanese web-font
delivery.
Noto Sans JP
Copyright 2014-2021 Adobe, with Reserved Font Name “Source”.
License: SIL Open Font License, 1.1
License URI: https://openfontlicense.org/open-font-license-official-text/
Source: https://github.com/google/fonts/tree/main/ofl/notosansjp
Noto Serif JP
Copyright 2012 Google Inc.
License: SIL Open Font License, 1.1
License URI: https://openfontlicense.org/open-font-license-official-text/
Source: https://github.com/google/fonts/tree/main/ofl/notoserifjp
The verbatim license text and conversion provenance are preserved under each
family directory in assets/fonts/. See NOTICE.txt.
- Install and activate the Axismundi theme.
- Upload and activate this plugin.
- Japanese text now renders in Noto Sans JP / Noto Serif JP. Optionally manage
the families under Appearance > Editor > Styles > Typography.
Automatic fallback-slot integration requires Axismundi 0.1.3 or later. Other
themes can still select the registered Noto families explicitly from the Font
Library or reference their family names in CSS.
No. The @font-face rules are scoped to the Japanese and CJK unicode ranges, so
Latin and numerals continue to use the theme’s primary family.
The public document language (<html lang>), normally derived from Site
Language, selects it; an inline lang="ja" subtree selects it for that run only.
A multilingual plugin may set the document language per request. The logged-in
user’s profile language translates wp-admin and does not select the font used for
published content.
Yes. Unlike the Korean package, the bundled WOFF2 files include the shared CJK
ideographs (CJK Unified Ideographs, Extension A, and Compatibility Ideographs)
alongside Hiragana and Katakana, so Japanese Kanji renders in Japanese glyph
forms. The files are correspondingly larger than a Kana-only subset.
Changelog
0.1.1
- The Font Library collection now declares the same
unicode-rangeas the
automatic fallback, so a family installed from it takes only Japanese text
and other characters fall through to the next font in its stack. The collection and readme say that
installing is optional and does not recreate the theme’s fallback stack. - The Japanese fonts are rebuilt from pinned upstream files (google/fonts
commit a54f744) by scripts/build-noto-cjk.py, with a generated manifest.
Coverage is unchanged. - Tested up to WordPress 7.1.
Earlier releases are listed in changelog.txt.
