Is the page on the web? If not, can you post it?

On Thu, Feb 4, 2021 at 3:26 PM [email protected] <[email protected]> wrote:

> Tom,
> It shows up in Edge, Chrome, and Firefox.  All I changed was the "encoding
> = utf8" for the NOAA reports (cheetagenerator in skin.conf) as was
> discussed in this thread.
> I don't have any special characters in use but now see the degree symbol
> along with the other odd addition   (°F) .
> Thanks.
> BG
> see* http://grattans.org/wx <http://grattans.org/wx>* under month of
> Feb.  It's not showing in Jan as that report was created before my change
> to utf8.
> On Thursday, February 4, 2021 at 5:37:23 PM UTC-5 [email protected] wrote:
>
>> Are you seeing this in a browser? If so, this is generally caused by the
>> browser using the wrong encoding. For example, it's probably expecting
>> Latin-1 (or Windows-1252) instead of the actual utf-8.
>>
>> As for why, did you add anything else to your NOAA page? Such, as an
>> encoding directive?
>>
>> If no encoding directive, then which browser are you using? Chrome
>> autodetects the encoding, but generally gets it right. For others, you must
>> set the encoding manually.
>>
>> -tk
>>
>> On Thu, Feb 4, 2021 at 2:15 PM [email protected] <[email protected]> wrote:
>>
>>> Gary,
>>> My upgrade to 4.4.0 was not a new install and I need to change manually
>>> to utf8. I made changes in skin.conf but must have missed something. My
>>> NOAA daily now shows:
>>> TEMPERATURE (°F), RAIN (in), WIND SPEED (mph)
>>>
>>> old form with html_entities encoding was:
>>> TEMPERATURE (F), RAIN (in), WIND SPEED (mph)
>>>
>>> Is there something I need to delete and rebuild?
>>>
>>> Thanks
>>> BG
>>>
>>>
>>>
>>> On Wednesday, February 3, 2021 at 1:53:47 AM UTC-5 gjr80 wrote:
>>>
>>>> Just by way of background up until v4.3.0 WeeWX shipped with
>>>> strict_ascii encoding for NOAA reports. v4.4.0 changed that to utf8 but for
>>>> new installs only, upgrades or earlier versions need to be changed 
>>>> manually.
>>>>
>>>> Gary
>>>>
>>>> On Wednesday, 3 February 2021 at 16:27:31 UTC+10 [email protected]
>>>> wrote:
>>>>
>>>>> Hi Gary,
>>>>>
>>>>> thanks again. Works now.
>>>>> [image: DustPM10.png]
>>>>>
>>>>> On Wednesday, February 3, 2021 at 7:18:43 AM UTC+1 Calo Geyer wrote:
>>>>>
>>>>>> Hi Gary,
>>>>>>
>>>>>> thanks. Yes, you are right. Got this in my skins.conf and it is even
>>>>>> written in the explanation. Will change and report back.
>>>>>>
>>>>>>
>>>>>> [CheetahGenerator]
>>>>>>
>>>>>>     # Possible encodings are 'html_entities', 'utf8', or
>>>>>> 'strict_ascii'
>>>>>>     encoding = html_entities
>>>>>>
>>>>>>     [[SummaryByMonth]]
>>>>>>         # Reports that summarize "by month"
>>>>>>         [[[NOAA_month]]]
>>>>>>             encoding = strict_ascii
>>>>>>             template = NOAA/NOAA-%Y-%m.txt.tmpl
>>>>>>
>>>>>>     [[SummaryByYear]]
>>>>>>         # Reports that summarize "by year"
>>>>>>         [[[NOAA_year]]]
>>>>>>             encoding = strict_ascii
>>>>>>             template = NOAA/NOAA-%Y.txt.tmpl
>>>>>>
>>>>>> On Wednesday, February 3, 2021 at 7:11:51 AM UTC+1 gjr80 wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> What encoding are you using for the NOAA format reports in your
>>>>>>> skin.conf? If you have the old encoding = strict_ascii then no you won’t
>>>>>>> see the mu character, you should see it though if you have encoding = 
>>>>>>> utf8.
>>>>>>>
>>>>>>> Gary
>>>>>>>
>>>>>>> On Wednesday, 3 February 2021 at 16:00:13 UTC+10 [email protected]
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi, I added my SDS011 data (which I read-in using file-pile)
>>>>>>>> however the unit in the header is not shows as microgramm per cubic 
>>>>>>>> meter.
>>>>>>>> I changed the unit in units.py to see if it also is adapted in the 
>>>>>>>> report
>>>>>>>> and was working however using the default pm10_0 unit shows as g/m
>>>>>>>> This is my entry in .tmpl
>>>>>>>> DUST PM10 ($unit.label.SDS011_PM10.strip())
>>>>>>>>
>>>>>>>>
>>>>>>>>  [image: NOAA Dust PM10.png]
>>>>>>>>
>>>>>>>> Any idea?
>>>>>>>>
>>>>>>> --
>>> 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/e8c77f07-a140-4cd0-a5c4-23d80dc182f0n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/e8c77f07-a140-4cd0-a5c4-23d80dc182f0n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
> 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/37264028-a1af-4424-8a78-ed39f0adcb13n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/37264028-a1af-4424-8a78-ed39f0adcb13n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CAPq0zEApeXMg_XQQ-DkSZvjFRtpbMx7zzfE6wXcz9arBr0XExQ%40mail.gmail.com.

Reply via email to