[PD] Menlo in MacOS X

Fri Jan 8 02:41:10 CET 2021

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.

> On Jan 7, 2021, at 15:07 PM, pd-list-request at lists.iem.at wrote:
> 
> Send Pd-list mailing list submissions to
> 	pd-list at lists.iem.at
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.puredata.info/listinfo/pd-list
> or, via email, send a message with subject or body 'help' to
> 	pd-list-request at lists.iem.at
> 
> You can reach the person managing the list at
> 	pd-list-owner at lists.iem.at
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Pd-list digest..."
> 
> 
> Today's Topics:
> 
>   1. Re: Declare library path on windows? (Kylee Kennedy)
>   2. fluid~ for Pd-Vanilla - test version (Alexandre Torres Porres)
>   3. Re: linking libs with pd-lib-builder (was Re: fluid~)
>      (Alexandre Torres Porres)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Wed, 6 Jan 2021 18:48:41 -0800
> From: Kylee Kennedy <kmkennedy at gmail.com>
> To: Christof Ressi <info at christofressi.com>
> Cc: Pd-List <pd-list at lists.iem.at>
> Subject: Re: [PD] Declare library path on windows?
> Message-ID:
> 	<CADD61nVbR8Je=YbpGKB-D_JLFZdPGYgOL29P+kk-_WN3=yWYxw at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> Brilliant. That works perfectly now. I was really trying to keep an eye on
> the case sensitivity since I am more used to that myself.
> fftease loads right up also with the proper [declare -path fftease -lib
> fftease]
> 
> I've been loving deken and pd's latest intelligent patching improvements!
> 
> Back to patching,
> Kylee
> 
> 
> On Wed, Jan 6, 2021 at 6:29 PM Christof Ressi <info at christofressi.com>
> wrote:
> 
>> Ok, I see the problem. Try [declare -path Pd_Spectral_Toolkit -lib
>> pd_spectral_toolkit]. *ugh*
>> 
>> The author uses capitalization for the library folder name
>> (Pd_Spectral_Toolkit) , but the file name and the setup function are all
>> lower case (pd_spectral_toolkit[_setup]). Since the Windows filesystem is
>> not case sensitive, this creates extra weirdness.
>> 
>> Generally, for Pd libraries containg a single binary should, folder and
>> file name should be the same! Please contact the project author and tell
>> them to change the folder name to all lower case.
>> 
>> Christof
>> On 07.01.2021 03:09, Kylee Kennedy wrote:
>> 
>> Thanks for the reply Christof, Hope you have a happy new year.
>> 
>> When I declare on WinX 0.51-3 I get: "load_object: Symbol
>> "Pd_Spectral_Toolkit_setup" not found
>> then a list of all the abstractions I used in that library that
>> ...couldn't create.
>> 
>> Thanks again for the help,
>> Kylee
>> 
>> 
>> 
>> 
>> 
>> 
>> On Wed, Jan 6, 2021 at 5:50 PM Christof Ressi <info at christofressi.com>
>> wrote:
>> 
>>> Same thing. "Pd_Spectral_Toolkit" is distributed as a single binary
>>> library, which means you have to load it. If the library also contains
>>> abstractions, you also have to add the path. In your case that would be
>>> [declare -path Pd_Spectral_Toolkit -lib Pd_Spectral_Toolkit].
>>> 
>>> ---
>>> 
>>> I really think we finally need a uniform [declare] syntax as proposed by
>>> https://github.com/pure-data/pure-data/pull/440. The binary format of
>>> library should be an implementation detail which the user shouldn't have to
>>> care about. For example, Kylee would only need to write [declare
>>> Pd_Spectral_Toolkit].
>>> 
>>> Christof
>>> On 07.01.2021 02:40, Kylee Kennedy wrote:
>>> 
>>> Hey list,
>>> 
>>> What is the proper way to declare libraries on Windows 10? I'm unable to
>>> declare and right slash the path like the wiki suggests. I'm working with
>>> fftease~ and Pd_Spectal_Toolkit a bunch lately.
>>> "declare -path Pd_Spectral_Toolkit" doesn't seem to work. If I put the
>>> full path and right slashes, they disappear when I switch back from edit
>>> mode. The only process that works is if I open the extensions object list
>>> first.
>>> 
>>> Thanks,
>>> Kylee
>>> 
>>> _______________________________________________Pd-list at lists.iem.at mailing list
>>> UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
>>> 
>>> _______________________________________________
>>> Pd-list at lists.iem.at mailing list
>>> UNSUBSCRIBE and account-management ->
>>> https://lists.puredata.info/listinfo/pd-list
>>> 
>> _______________________________________________
>> Pd-list at lists.iem.at mailing list
>> UNSUBSCRIBE and account-management ->
>> https://lists.puredata.info/listinfo/pd-list
>> 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20210106/41068532/attachment-0001.html>
> 
> ------------------------------
> 
> Message: 2
> Date: Thu, 7 Jan 2021 00:14:56 -0300
> From: Alexandre Torres Porres <porres at gmail.com>
> To: Pd-List <pd-list at lists.iem.at>
> Subject: [PD] fluid~ for Pd-Vanilla - test version
> Message-ID:
> 	<CAEAsFmiiN+X_mKH_s8+zOGUE8homTMky+uCbc98V0A=-L8mhng at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> Ok, we made lots of progress and now we have tests versions for macOS and
> Windows (32 and 64 bits).
> 
> Here's for everyone to test if all the links for dynamic libraries are
> working :)  https://github.com/porres/pd-fluidsynth/releases/tag/test-1
> 
> we still need to sort this for linux, write a better readme with build
> instructions and reorganize things so then we can upload it to deken as a
> final/oficial release.
> 
> thanks for everyone who helped.
> Alex
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20210107/1b7301ed/attachment-0001.html>
> 
> ------------------------------
> 
> Message: 3
> Date: Thu, 7 Jan 2021 03:07:13 -0300
> From: Alexandre Torres Porres <porres at gmail.com>
> To: Christof Ressi <info at christofressi.com>
> Cc: Pd-List <pd-list at lists.iem.at>
> Subject: Re: [PD] linking libs with pd-lib-builder (was Re: fluid~)
> Message-ID:
> 	<CAEAsFmh4fr3y-_BgZtZu+CFyK-dF5WFscyWtOktT=z+g4aAUPA at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> The license is being respected (I think?). I didn't touch it, see
> https://github.com/porres/pd-fluidsynth/blob/main/LICENSE.txt and, well, I
> do think I could make a variation of this in my ELSE library, but I'd keep
> the license untouched anyway. Thus, the bump in the way is still learning
> how to statically link a complex project like this...
> 
> So, I started a new thread to announce the test builds for mac/windows, but
> it all seems fine. Now, what about Linux? There's mo magical scripts for
> linux, why? I guess Linux handles the dependencies nicely via apt-get and
> stuff, but what about sharing this via deken?
> 
> cheers
> 
> Em qua., 6 de jan. de 2021 às 09:43, Christof Ressi <info at christofressi.com>
> escreveu:
> 
>>> static linking has *legal* implications:
>>> you cannot just distribute a binary that statically links a GPL-library
>> under another license (eg the dwtfyw license).
>> For the sake of clarity, the same is also true for dynamic linking!
>> 
>> IOhannes knows this, of course, I just figured his comment could've
>> accidentally left some people with the impression that it's ok to
>> dynamically link a GPL library to a permissively (or even commerically)
>> licensed project.
>> 
>> Now, libfluidsynth is actually LGPL v2 licensed. The LGPL has an
>> exception which allows to link a LGPL library to a permissively (or
>> commercially) licensed project. Many people seem to think that LGPL only
>> allows for dynamic linking, but it's also possible to link statically
>> under certain (more strict) conditions:
>> 
>> https://www.gnu.org/licenses/gpl-faq.html#LGPLStaticVsDynamic
>> 
>> ***DISCLAIMER***: This is just my understanding of the situation.
>> Anybody feel free to correct me on this!
>> 
>> Christof
>> 
>> On 06.01.2021 09:52, IOhannes m zmölnig wrote:
>>> Am 6. Jänner 2021 03:39:00 MEZ schrieb Alexandre Torres Porres <
>> porres at gmail.com>:
>>>> Personally, I strongly prefer static linking for plugins (like Pd
>>>>> externals).
>>>>> 
>>>> seems best for me too!
>>>> 
>>> well, apart from bloat (speaking with my system packager hat on), static
>> linking has *legal* implications:
>>> you cannot just distribute a binary that statically links a GPL-library
>> under another license (eg the dwtfyw license).
>>> 
>>> are you prepared for doing your homework here?
>>> 
>>> 
>>> 
>>> mfg.hft.fsl
>>> IOhannes
>>> 
>>> 
>>> _______________________________________________
>>> Pd-list at lists.iem.at mailing list
>>> UNSUBSCRIBE and account-management ->
>> https://lists.puredata.info/listinfo/pd-list
>> 
>> 
>> 
>> _______________________________________________
>> Pd-list at lists.iem.at mailing list
>> UNSUBSCRIBE and account-management ->
>> https://lists.puredata.info/listinfo/pd-list
>> 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20210107/514b7d9d/attachment.html>
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> Pd-list mailing list
> Pd-list at lists.iem.at
> to manage your subscription (including un-subscription) see
> https://lists.puredata.info/listinfo/pd-list
> 
> 
> ------------------------------
> 
> End of Pd-list Digest, Vol 190, Issue 28
> ****************************************