mirror of
https://github.com/storytold/effectcraft.git
synced 2026-10-29 04:26:55 -06:00
FeiLiuEM
55ba002acf
`style_variations_change_advances_and_outlines` picked `wdth`, else `wght`, else the first axis with a range, and then asserted that the advance moves. That assumes the chosen axis changes advances, which a monospaced family does not: Google Sans Code - the first variable face on a machine where it is installed, and the one this check met on Linux - moves its outlines along `wght` but keeps its advances fixed by design, so the test failed with "wght 300..800: advances 780 vs 780" while `measure` and the font were both right. The test now tries the axes in order and uses the first one whose advance actually moves (Google Sans Code answers on its own MONO axis, Bahnschrift on `wdth`), and skips with a message on a machine whose variable faces never move an advance - the same shape as the "no variable font installed" skip next to it. The outline assertion keeps its teeth: the axis is picked for moving the advance, but whether the outline follows it is still checked. On Linux with Google Sans Code and Bahnschrift installed: `cargo test -p effectcraft-text` reported 43 passed / 1 failed before and 44 passed after. `cargo fmt --all --check` and `cargo clippy -p effectcraft-text --all-targets -- -D warnings` are clean.