max / makeover-build

Re-export the webfont filenames, and drop a dash from the generated banner The filenames are half of an agreement the consumer's own build script holds the other half of, so they cross through here rather than through a second makeover pin.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: Max Johnson <me@maxj.phd> · 2026-08-17 16:25 UTC

Signed with PGP, not checked

Commit: 18d683a17e4d53490bdbc898ae45b66702aa3d23

Parent: cad4b30

1 file changed, +9 insertions, -1 deletion

M src/lib.rs +9 -1

			@@ -54,6 +54,14 @@
54	54		/// three. Nothing here wraps it; the emitter's options are the emitter's.
55	55		pub use makeover_webview::Emit;
56	56
	57	+	/// The filenames [`typography_css`]'s `@font-face` rules fetch.
	58	+	///
	59	+	/// Re-exported for the same reason as [`Emit`], and load-bearing for a further
	60	+	/// one: the consumer's own build script writes those two files, so the emitter
	61	+	/// and the writer have to agree on the name. Through this they agree on a
	62	+	/// constant rather than on a string typed in two repositories.
	63	+	pub use makeover::{WEBFONT_MONO_FILE, WEBFONT_SANS_FILE};
	64	+
57	65		/// Write the themes `makeover` ships into `dir`, as `<id>.toml`.
58	66		///
59	67		/// Clears stale `.toml` files first, so a theme removed or renamed upstream
			@@ -161,7 +169,7 @@
161	169		"/* Generated by makeover-build from makeover. Do not edit.\n \
162	170		Two needs, two names, then a system generic. The faces are cut by\n \
163	171		quasi-type from Atkinson Hyperlegible plus the house glyph set, and\n \
164		-	both are variable over wght 200-800 in one file — which is why the\n \
	172	+	both are variable over wght 200-800 in one file, which is why the\n \
165	173		@font-face rules name the range. The mono face opens at ExtraLight. */\n\n",
166	174		);
167	175		css.push_str(&makeover::font_face_css(font_url));