ola too....
who said pidip does evil things ;-) It sounds like a pet.
no, i just meant font issue in general.......
I wonder how this step - taken from the OS-X note on installing pidip could be integrated into the build-system ------------------------------------------------------------
4. install the fonts on your system :
sudo mkdir /usr/X11R6/lib/X11/fonts/TTF sudo cp /usr/local/lib/pd/pdp_pidip_osx/fonts/* /usr/X11R6/lib/X11/ fonts/TTF -------------------------------------------------
i dont want to hack anything, unfortunately i cant ,-)
see you
Am 28.03.2007 um 19:58 schrieb ydegoyon@free.fr:
ola,
pidip doesn't do all these evil things, it just relies on imlib ( imlib_load_font ) to load the fonts, so you want to hack imlib?
ciao, sevy
IOhannes m zmoelnig wrote:
Luigi Rensinghoff wrote:
Well, i think you guys will find a solution.
It makes me think of the "pidip" installation, which we will come to at a point, since it uses Fonts, too.
I just wanted to remind you, that that's a similar problem and maybe can be solved with this one.
hmm, i think (but don't know exactly) that pidip needs low-level access to the font, instead of relying onto system-fonts. it just happens that pidip searches the system-font paths to get its fonts.
it should be similar to the case of Gem (though Gem does not even attempt to access the system fonts); one could hack pidip (if it doesn't already do so) to additionally use pd's search paths to search for fonts.
i don't think that this is that simple with tcl/tk (but then: why not?), which probably relies on the system's font manager.
mfg.asdr IOhannes
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev