Yogesh OjhaandClaude Opus 5 7b05d3fbf5 fix(reports): one font file per face, because a split subset printed Greek as Latin ...

The Google Fonts css2 API answers a modern user agent with one @font-face per
script, all sharing a family and weight and separated only by unicode-range.
WeasyPrint then shapes a run against one subset file and rasterises it from
another: the PDF's text layer read back correctly while the page showed
"ΨΗΦΙΑΚΗ ΥΠΗΡΕΣΙΑ" as "N ĂN ĐỀ ẤU NẤGĂNG". Every non-Latin page title in a
report was gibberish.

Ask the API with a user agent that predates unicode-range and it answers with
one whole file per family, weight and style; subset that here with fontTools
and save it as woff2. The vendoring script now refuses to write a face whose
block still carries a unicode-range, so the split cannot come back unnoticed.

131 files and 3.3 MB become 23 files and 1.2 MB — smaller as well as correct.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AW5pitnosX8LEFEYxH8gFS

2026-09-06 16:26:23 +05:30

..

fetch_port_registry.py

feat(scan): name and describe the long tail of ports, with brand marks

2026-09-04 02:59:14 +05:30

fetch_report_fonts.py

fix(reports): one font file per face, because a split subset printed Greek as Latin

2026-09-06 16:26:23 +05:30

fetch_subdomain_wordlist.py

feat(subdomain): discovery guesses names as well as asking for them

2026-09-06 07:48:37 +05:30