Doop
Doop: 오픈소스 멀티플레이어 디자인 캔버스 및 AI 에이전트용 MCP
저장소 정보는 아직 수집하지 않았습니다.
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
메이커가 쓴 소개는 위의 한 줄이 전부입니다. 더 자세한 내용은 저장소 README에서 읽을 수 있습니다. 저장소 README ↗
README 전체를 불러오는 중입니다.
README 전문 보기 ↗This document is about making the font: the Builder app and the engineering behind it.
For demo and info on how to use this font, please visit the JianZiPu Font Website.
The JianZiPu font system is designed for rendering traditional Chinese guqin notation 减字谱 or JianZiPu. The font supports Chinese characters and ASCII input.
The JianZiPu font uses a glyph layering system where each musical notation character is built by combining multiple component glyphs that stack and position themselves relative to each other. So each character is made of a series of glyphs, similar to how an English word is made of a series of letters.
The font is made in the JZP Font Builder, a web app (app/) served by a
small Python server. Everything you design happens there:
Start it on your machine:
cd builder
pip install -e . # once
python3 -m jzpbuild.webserver # open http://127.0.0.1:5713/
The app needs building once (cd app && npm install && npm run build), and the
base font builder/src_font/TW-Kai-98.ttf, which is not in the repo,
must be copied in once. Save in the Builder writes the files in
builder/inputs/ (design.json, components.csv, svg/), which you
then commit. Invited testers use a hosted copy where their work stays in a
private draft until it is reviewed; see builder/README.md "Hosted pilot".
site/ is the public font page at jianzipufont.com:
a static page that types in the released font. Cloudflare Pages deploys it from
main (output directory site, no build command). A new font is published as a
release from the local Builder's Release screen: it builds the font into
site/JianZiPu.ttf, tags it, and GitHub publishes it on the
releases page. See
docs/maintainers/releasing.md, and CHANGELOG.md for what each
version changed.
The Builder itself runs at builder.jianzipufont.com (see builder/README.md
"Hosted pilot").
Problems and ideas go in issues; font changes go through the online Builder as Change Requests; code takes pull requests. See CONTRIBUTING.md. Reviewing, releasing and the service setup are in docs/maintainers/.
The font is built by a Python pipeline in builder/ (no FontForge, no
hand-edited feature files). The Builder runs it for you; from the command line
it is cd builder && python3 -m jzpbuild (writes
builder/JianZiPu.ttf). See builder/README.md for the
architecture, the inputs, and how the build is verified (a HarfBuzz shaping
regression test against a golden font).
The old manual pipeline (FontForge + scripts.cjs, the .sfd sources and the
v3.x backups) lived in src-fontforge/ until 2026-10-18. It is kept in git
history under the tag fontforge-final.
builder/inputs/ (the glyph
outlines in svg/, design.json, components.csv, edge_cases.fea, glyphRename.csv,
layouts.json), site/JianZiPu.ttf, builder/tests/JianZiPu.ttf, and any font built from them.builder/jzpbuild/, builder/tests/ (apart from the .ttf above), app/, site/index.html,
Dockerfile and supabase/.builder/src_font/TW-Kai-98.ttf)
is not in this repository and is not redistributed as is.Copyright 2021–2026 Nancy Yi Liang, Nellodee LLC.