Yes it would but the current code base is limited to what we can do with the python string encode() function. However, I have an idea for something we could do to hopefully improve things, let me discuss with Tom.
Gary On Tuesday, 26 January 2021 at 17:55:23 UTC+10 [email protected] wrote: > wouldn't that make more sense to drop the umlaut and Düsseldorf = > Dusseldorf - that is what other webservices do that can't deal with > non-ascii characters. would be better than dropping the character completely > > On Tuesday, January 26, 2021 at 7:02:00 AM UTC+1 gjr80 wrote: > >> NOAA files use strict_ascii encoding >> <http://weewx.com/docs/customizing.htm#Specifying_template_files> so no >> umlauts or other accented characters unfortunately. You can change the >> encoding but as the NOAA format reports are tabulated reports it will mess >> up the format of the report. >> >> Gary >> >> On Tuesday, 26 January 2021 at 15:53:23 UTC+10 [email protected] wrote: >> >>> The staion name has a German umlaut in it. It shows correctly on the web >>> pages, but in the NOAA files it misses the letter completely. >>> e.g. name = "Köln", NOAA file has "Kln" >>> >>> On Monday, January 25, 2021 at 11:52:49 PM UTC+1 [email protected] wrote: >>> >>>> dumb question. the climatogical report & summary - Name, is missing "ö" >>>>> looks like it did not like UTF-8. >>>>> is there a way to manually fix this? >>>>> >>>> >>>> Not a dumb question at all, but I don't understand it either. What "ö"? >>>> >>> -- 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/614395f3-d991-45f9-ad80-dba7fe59168en%40googlegroups.com.
