Re: Small error in install-font from Peter Schaffter

[Wim Stockman]

Hi Peter,
Thanks for taking the time to test it out.

Yes, you are right with your comment.
The only advantage it has is to reduce file size.
if you don't embed the font in the pdf and still want it to be correctly
rendered on a machine where the correct fonts are installed.
I often empty the download file in the devpdf so they don't get embedded.

Kind regards
Wim Stockman


Op ma 12 dec. 2022 om 22:20 schreef Peter Schaffter <peter@schaffter.ca>:

> Wim --
>
> On Mon, Dec 12, 2022, Wim Stockman wrote:
> > Here is the updated script to set the internalname in an interactive way.
>
> I performed some tests altering the internalnames in groff font
> files.  First I converted FreeSerif.otf and FreeSerifItalic.otf to
> groff fonts using the offical install-font.sh, then did the same
> thing with your updated script, answering the prompts for internalname
> with FreeSerif-Roman and FreeSerif-Italic.  (The FreeSerif family
> is already registered on my system from .deb fonts-freefont-ttf).
>
> As nearly as I can tell--someone please correct me if I'm
> wrong--changing internalnames like FreeSerif to FreeSerif-Roman or
> FreeSerifItalic to FreeSerif-Italic is only effective when the font
> is a registered system font.  What it does is trigger the pdf viewer
> (in my case, okular) to use the system font instead of downloading
> it (i.e. embedding it in the file).  However if you leave the name
> alone, the font gets embedded because the internalname matches the
> font as registered in the /devpdf/download file.  In either case,
> the output should be the same.
>
> More significantly, fonts that are not registered system fonts fail
> when you alter the internal name, so I can't at present see any
> advantage to giving users the option.
>
> --
> Peter Schaffter
> https://www.schaffter.ca
>
>