FR version is available. Content is displayed in original English for accuracy.
The vector paths come directly from macOS's symbol renderer. Internally it reaches a private ivar on NSSymbolImageRep to get the CUINamedVectorGlyph, draws into a CGPDFContext, then walks the PDF content stream back out as SVG `d` commands. The output matches what the system draws, rather than an approximation traced from rasters.
A few things about it:
- Every subcommand accepts `--json`, and `sfsym schema` returns a machine-readable description of the whole CLI. - Symbol enumeration reads the OS's Assets.car BOM tree, so the list of 8,300+ names stays current with macOS updates without a version table in the binary. - Each SVG `<path>` carries a `data-layer` attribute, so you can retheme in CSS without touching geometry.
It's been saving me a bunch of clicking. Please let me know if you have any other ideas for it.

Discussion (7 Comments)Read Original on HackerNews
Genuine question: what’s your use case for having a single SF Symbols icon as a PDF file? Let alone having that as the default? In my own experience, I’d want SVG nearly every time.
https://developer.apple.com/sf-symbols/
This is not my iconset of choice, though.
Quick question, are you also planning on supporting animations?