R devel - Sep 2008 - family="mono" does not work (PR#12931)

Full_Name: Jaan Vajakas
Version: 2.7.2
OS: Windows XP
Submission from: (NULL) (193.40.5.245)


When I execute the following code in the R GUI, the text "mono" is
printed in
monotype font in the first plot, but in normal (sans-serif) font in the
remaining three plots:

op=par(mfrow=c(2,2))
for (i in 1:4) {
 hist(1:10,xlab="")
 mtext("normal",side=1,line=2)
 mtext("mono",side=1,line=3,family="mono")
}
par(op)

jaanvajakas at hot.ee wrote:
> Full_Name: Jaan Vajakas
> Version: 2.7.2
> OS: Windows XP
> Submission from: (NULL) (193.40.5.245)
>
>
> When I execute the following code in the R GUI, the text "mono"
is printed in
> monotype font in the first plot, but in normal (sans-serif) font in the
> remaining three plots:
>
> op=par(mfrow=c(2,2))
> for (i in 1:4) {
>  hist(1:10,xlab="")
>  mtext("normal",side=1,line=2)
>  mtext("mono",side=1,line=3,family="mono")
> }
> par(op)
>
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
>   
This seems to be specific to the Windows driver. I see it in R running 
under Wine on Fedora, but not in native R (X11), and not in the pdf 
driver either, even when run via Wine.

-- 
   O__  ---- Peter Dalgaard             ?ster Farimagsgade 5, Entr.B
  c/ /'_ --- Dept. of Biostatistics     PO Box 2099, 1014 Cph. K
 (*) \(*) -- University of Copenhagen   Denmark      Ph:  (+45) 35327918
~~~~~~~~~~ - (p.dalgaard at biostat.ku.dk)              FAX: (+45) 35327907

On 19/09/2008 7:10 AM, jaanvajakas at hot.ee wrote:
> Full_Name: Jaan Vajakas
> Version: 2.7.2
> OS: Windows XP
> Submission from: (NULL) (193.40.5.245)
> 
> 
> When I execute the following code in the R GUI, the text "mono"
is printed in
> monotype font in the first plot, but in normal (sans-serif) font in the
> remaining three plots:
> 
> op=par(mfrow=c(2,2))
> for (i in 1:4) {
>  hist(1:10,xlab="")
>  mtext("normal",side=1,line=2)
>  mtext("mono",side=1,line=3,family="mono")
> }
> par(op)
This was a windows() device driver bug, as Peter suspected.  Now fixed. 
  Thanks for the report!

Duncan Murdoch