I humbly suggest adding the fonts argument to the list of arguments recognized and processed by ps.options.
Here is my argument:
Currently, in Sweave it seems to be impossible to use multiple font families in <<fig=TRUE>> code chunks without additional moderately inconvenient coding.
The problem is that it is possible to use
par(family="xxx") in postscript and pdf devices
(which are the devices used by Sweave),
but the fonts used in par statements also have to be included in the fonts argument of the postscript or pdf device when the device is opened.
In normal mode, Sweave opens the device all by itself, therefore in this mode it seems not possible to change the fonts used by the postscript or pdf device. Instead, one has to explicitly open the device in one's own code chunk. That is possible, but then one has to manually take care of including the generated postscript and/or pdf files also.
The easiest solution would be that ps.options accepts the fonts parameter, which it currently does not. That way, one could set the fonts available by default when Sweave uses the postscript device.
-- Erich Neuwirth, Didactic Center for Computer Science University of Vienna Visit our SunSITE at http://sunsite.univie.ac.at Phone: +43-1-4277-39464 Fax: +43-1-4277-9394 ______________________________________________ Rfirstname.lastname@example.org mailing list https://stat.ethz.ch/mailman/listinfo/r-develReceived on Sat Aug 05 23:54:48 2006
Archive maintained by Robert King, hosted by
the discipline of
statistics at the
University of Newcastle,
Archive generated by hypermail 2.1.8, at Sun 06 Aug 2006 - 02:27:36 GMT.
Mailing list information is available at https://stat.ethz.ch/mailman/listinfo/r-help. Please read the posting guide before posting to the list.