Follow-up Comment #1, bug #62572 (project groff): I'm not sure how to do this, it is quite permissable to have a blank download file, just as it is in grops. The file in grops lists those fonts which require to be embedded since they are not part of the 35 base fonts for postscript. In gropdf a missing entry also means that the font does not need to be downloaded, i.e. it is one of the base pdf fonts, but because I implemented the -e flag in gropdf I do need to know from where the base fonts can be downloaded. This is why some of the filenames in download have a leading asterisk, they are base files which don't need to to be included in the pdf except when the -e flag is present.
Gropdf should not be expected to work without a valid download file, which is why I consider removing BuildFoundries from groff executables was a mistake. It was intended as a tool for the user to use if there were changes to his system which resulted in new positions for the needed fonts, i.e. new version of ghostscript. This is why the program attempts to preserve local changes to download while looking for the URW fonts. It could similarly be used if a user messed up his download file. Gropdf could have a moan if the -e flag is present and the required font is not mentioned in the download file, but without the flag it just means that no download is required, the same as grops. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?62572> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/