Update of bug #62150 (project groff):
Status: In Progress => Fixed
Open/Closed: Open => Closed
Planned Release: None => 1.23.0
_______________________________________________________
Follow-up Comment #6:
[comment #5 comment #5:]
> Hmm, it now occurs to me: is this script guaranteed to be run on a file
system that uses "/" as the directory separator?
I think so. At some point, MS-DOS support was dropped, and all ports to
Windows in the past 20-odd years or so seem to have been done on top of a
POSIX emulation layer.
> If it needs to be more general, perl has a basename() function in its
standard File::Basename module <http://perldoc.perl.org/File::Basename> that
is aware of the OS's conventions.
If this turns out to be an issue, I'm happy to adapt it. But I think we have
a lot of other places that assume '/' as a directory separator.
Meanwhile:
commit 9c46247e568d15f7badaed7774af8c2673bdc1ea
Author: G. Branden Robinson <[email protected]>
Date: Wed Mar 9 12:09:15 2022 +1100
[afmtodit]: Fix Savannah #62150.
* src/utils/afmtodit/afmtodit.pl: Stop writing full file name to the
generated font description file as the "name" (i.e., don't include
directory components).
Fixes <https://savannah.gnu.org/bugs/?62150>. Thanks to Dave Kemper for
the discussion and code review.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?62150>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
