Thank you Dan,
I confirmed that the changes in the develop branch
https://github.com/pure-data/pure-data/commit/0c13ecf3c89acaa212209dbe47d27f...
fixed the problem.
Cheers,
Julian.
On Jan 8, 2021, at 19:33 PM, Dan Wilcox danomatika@gmail.com wrote:
You can fix it in tcl/pd_menucommands.tcl by either trying the -fontmap option or changing the find-replace from "DejaVuSansMono" to "MenloRegular"
https://github.com/pure-data/pure-data/blob/master/tcl/pd_menucommands.tcl#L...
Right-click on the Pd-###.app and choose "Show package contents." The tcl scripts are in Contents/Resources/tcl. Edit the file and save, then (re)start the app to see any changes. Let us know what works.
On Jan 8, 2021, at 2:41 AM, pd-list-request@lists.iem.at wrote:
Date: Fri, 8 Jan 2021 10:41:10 +0900 From: Julián Villegas villegas.julian@gmail.com To: pd-list@lists.iem.at Subject: [PD] Menlo in MacOS X Message-ID: BD8528B6-C603-4EAE-ADCC-BF779338FD83@gmail.com Content-Type: text/plain; charset=utf-8
Hi,
I use the print option of Pd to create PS files that I then convert to PDF when I need to share a program in a presentation, paper, etc. I use Preview most of the time, but I have also used Ghostscript for this process too. No matter what tool I use, there’s always an error saying that the Menlo font file was not found and the resulting PDF is rendered with Courier fonts.
By looking at the Font Book, I know that the Postcript name of this font is “Menlo-Regular” so what I’m currently doing is to edit the ps file and replacing all instances of “Menlo” by “Menlo-Regular.” After saving it, I can then open it in whatever tool and the PDF is rendered with the intended font.
I could keep doing this, but it’s rather a hassle to add this extra editing step to the process. Is there any other way to fix this problem? For example, would this be worth of opening an issue in GitHub?
Thanks for the help, and have a nice weekend,
Julian.