search for: metricinfo

...TextUTF8' If set, you need to supply functions textUTF8 and strWidthUTF8 which are just like text and strWidth but will be passed text in UTF-8. Note that these are alternatives: the graphics engine will only use the UTF-8 versions when this avoids re-encoding. Another thing I see is with metricInfo: in a multibyte locale this is passed the Unicode point, and it seems almost all third-party graphics devices are ignoring that. To make things a little simpler, if hasTextUTF8 is set, Unicode points are sent to metricInfo as negative values. Examples can be seen in e.g. the postcript, pdf and...

...t;clip(%lf,%lf,%lf,%lf)\n", x0, y0, x1, y1); } static void NULL_Deactivate(NewDevDesc *dev) { Rprintf("deactivate\n"); } static void NULL_Mode(int mode, NewDevDesc *dev) { } static Rboolean NULL_Locator(double *x, double *y, NewDevDesc *dev) { return FALSE; } static void NULL_MetricInfo(int c, R_GE_gcontext *gc, double* ascent, double* descent, double* width, NewDevDesc *dev) { *ascent = 0.0; *descent = 0.0; *width = 0.0; } static void NULL_Size(double *left, double *right,...

I've been testing plotmath. But I'm getting some funny output one one computer. The problem is that characters are 'jumbled' and overstrike when symbols are introduced. Sample code: mu <- 440.0 sigma <- 12.5 myx <- seq( mu - 4*sigma, mu+ 4*sigma, length.out=500) myDensity <- dnorm(myx,mean=mu,sd=sigma) # Here's one way to retrieve the values of mu and sigma and