hi, the tests pass on 10.5.7... which just uses the unix function... (which uses fc-list).
I think it should be easier to figure out what to do for when fc-list isn't there (pre 10.5.x machines)... by looking at the out put that the fc-list using function uses. cu, On Wed, May 20, 2009 at 3:33 PM, Lenard Lindstrom <le...@telus.net> wrote: > I committed what I have so far. If OS X has an fc-list equivalent take a > look at the updates I made to the Unix section of sysfont.py for Python 3 > and unicode. Some of it may be relevant. > > Lenard > > > > René Dudfield wrote: > >> hello, >> >> ah, nice catch! That's annoying... all this time and it hasn't been >> working on OSX. >> >> Can you commit your tests? >> >> I can have a go at it... unless Brian you want to have a go? >> >> >> Here are the main font paths... the X11 one isn't there on most >> installs for 10.4.x ... but should be there on most 10.5.x installs. >> The last path is where OS9 used to install fonts, and some people >> still use that directory apparently. >> >> ~/Library/Fonts/ >> /Library/Fonts/ >> /System/Library/Fonts/ >> /usr/X11/lib/X11/fonts/TTF/ >> /Network/Library/Fonts/ >> /System Folder/Fonts/ >> >> >> cheers, >> >> >> >> >> On Wed, May 20, 2009 at 7:55 AM, Lenard Lindstrom <le...@telus.net> >> wrote: >> >> >>> Currently I am filling in the font unit tests. For OS X I noticed that >>> sysfont.py does not hunt down installed fonts. The relevant function is a >>> stub. I have no OS X access, so can't write it myself. Is someone else >>> willing to take care of it. Otherwise when I commit the completed unit >>> tests >>> they will fail for OS X. >>> >>> Lenard >>> >>> >>> >>> >> >
