You might check to see what font is actually used by looking at the developer tools browser. Most browsers use F12 to activate the developer tools or it's in the menu.
On Mon, Apr 5, 2021 at 5:00 PM richard maliszewski <[email protected]> wrote: > Dug through that. The font referenced for unit_label_font_path in > skin.conf for Seasons is "font/OpenSans-Bold.ttf", which does exist. > Thinking it might not have full support for the Unicode math symbols, I > changed that to "/usr/share/fonts/truetype/dejavu/DejaVuSans.ttf", which > supposedly covers all 256 symbols. And I still have the weird unit > label...nothing there changed. I see no error messages WRT rendering in > the log as described in the User's Guide. > > What's quite odd is that the rendered text contains both the "micro" and > the "cubed" symbols...it just has the extra garbage as well. > > And I found where this unit value gets defined: in > /usr/share/weewx/unit.py: "microgram_per_meter_cubed": u"µg/m³". In the > HTML for the "current" line, this looks reasonable: "µg/m³". > But I have yet to make the image generator happy. > > --Richard > > > > On Monday, April 5, 2021 at 2:39:06 PM UTC-7 gjr80 wrote: > >> Hi, >> >> Nothing to do with drivers or extensions, it’s a font issue. Have a read >> of the section Funky symbols in plots >> <http://weewx.com/docs/usersguide.htm#funky_symbols> in the User’s Guide. >> >> Gary >> On Tuesday, 6 April 2021 at 07:31:17 UTC+10 [email protected] wrote: >> >>> This is a minor annoyance, but I am failing to figure out where this is >>> being done, or how to fix it. Units for PM2.5 are micrograms per meter >>> cubed. I've got a "current" where the units look as expected: µg/m³. >>> >>> But in the generated history images, the units in the upper show as >>> shown in this image: [image: Screen Shot 2021-04-05 at 2.27.13 PM.png] >>> Station data is coming from the WX1000 extension and in this case, some >>> of it from the PurpleAir extension. Looking through both extensions, I am >>> not seeing who/what is choosing the unit string for these values, nor where >>> it's getting sucked into the image generator. Hints? I am a week into >>> using WeeWX, and am quite impressed, but finding where the bodies are >>> buried for this sort of magic. >>> >>> --Richard >>> >>> -- > You received this message because you are subscribed to the Google Groups > "weewx-user" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/31dd2730-21d9-4e86-85a2-8a42d3e339b3n%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/31dd2730-21d9-4e86-85a2-8a42d3e339b3n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Peter Quinn (415)794-2264 -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAA1SM22dHJod7cf_pgq%3DOBwPZ277yg2ti32qh5yh0Ad3TzGQWg%40mail.gmail.com.
