Follow-up Comment #37, bug #67207 (group groff): [comment #34 comment #34:] >> By contrast, we can still use _pfbtops_ to generate a PFA from >> "StandardSymSL.pfb", but we don't have to name the PFA in the "download" >> file. Not doing so makes the exercise a bit of a digression from >> "devpdf.am"'s mission, but I like the idea of shipping the font in both >> formats, and I strongly like the idea of actually exercising _pfbtops_'s >> code. > > Why do you like the idea?
I decided to do this instead.
commit f9a017fc434a4025e9186a600ce7fde729539337
Author: G. Branden Robinson <g.branden.robin...@gmail.com>
Date: Thu Jun 26 01:23:43 2025 -0500
[pfbtops]: Add test for `pfbtops` command.
* src/util/pfbtops/tests/smoke-test.sh: Do it.
* src/util/pfbtops//pfbtops.am (pfbtops_TESTS): Run test.
(TESTS): Add test to suite.
(EXTRA_DIST): Ship test in distribution archive.
However I'm also doing this:
commit 545633c2da201a9b25e12f62b869f124c9fa0dd3
Author: G. Branden Robinson <g.branden.robin...@gmail.com>
Date: Thu Jun 26 01:05:21 2025 -0500
[devpdf]: Ship source for StandardSymSL font.
* font/devpdf/generate/StandardSymSL.sfd: Add human-readable source
format for new font. Everything in groff is available under the GNU
GPL, so we should provide a "preferred form for modification". (We
already do so for "freeeuro.sfd".)
* font/devpdf/devpdf.am (EXTRA_DIST): ...and ship it in the distribution
archive. At this time, we also ship the "compiled" PFB file; the
build process does not perform any transformation of the source SFD
file. That can change in the future if we can tolerate a build-time
dependency on fontforge(1).
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67207>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
