Follow-up Comment #12, bug #61423 (project groff): [comment #11 comment #11:] > if we do, it suggests another bug report needs to be filed > against whatever tool is putting full paths there.
The (good? bad?) news is that this tool is part of groff: afmtodit. All my font description files produced by install-font.sh have a comment at the top saying "This file has been generated with GNU afmtodit" (followed by version numbers ranging from 1.20.1 to 1.22.3) and a "name" directive containing only the basename. So install-font.sh is calling afmtodit in a way that does not put a full path there. The problematic font description file also has the comment crediting afmtodit (specifically version 1.22.2), but this file I generated using a script Tadziu posted (http://lists.gnu.org/r/groff/2013-11/msg00042.html). Thus, afmtodit does not routinely include paths in the "name" directive, but can be coaxed into doing so. So if groff now disallows a path here, afmtodit ought to at least squawk if the user asks for one, if not omit it entirely. Whether this warrants a separate bug report will depend, I think, on what decisions are made of the choices offered in comment #10 and comment #9. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?61423> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
