Skip to content

quartz fonts issue, ever resolved?

3 messages · Simon Jackman, Byron Ellis

#
Actually, I do have an answer. I just apparently forgot to write a
post on the subject. :-)

The problem is twofold. The first is that you don't have Arial on your
system and the hard coded fallback font is Arial (according to a note
I left to myself a problem with italics in Helvetica on 10.4 prompted
the decision).

The bigger problem is why you're falling back to that at all--it
should be a very rare occurrence. The problem looks to be that
par()$family is NULL by default which the font lookup code switches to
"default". Of course, when you look at "quartzFonts()" you'll notice
that it only includes valid values for par()$family which are "mono,"
"sans" or "serif." (Courier, Helvetica and Times-Roman respectively by
default).

A quick workaround is par(family="mono").

In the longer term, there appears to be a bug in the way
quartz.options()$family is used (it isn't as far as I can tell) that
I'm going to fix and write a patch for (probably falling back to that
before falling back to Arial).
On Thu, Jan 7, 2010 at 3:20 PM, Simon Jackman <jackman at stanford.edu> wrote: