yup - yr site now loads correctly into my edge browser. Glad to have been of help - and I guess the same 'fix' could possibly help other users who have a need for utf-8 encoding and are getting baffled whilst trying to make it work with txt and NOAA in particular!
Still - yr sorted - which is good news!! On Saturday, 17 June 2017 14:12:46 UTC+3, Gert Andersen wrote: > Hi Andrew > > Problem solved. I read the suggested document and inserted: > AddCharset UTF-8 .txt > in the .htaccess file. > > Thanks for pointing me in the right direction. > > Rgds > Gert > > On Saturday, June 17, 2017 at 11:12:56 AM UTC+2, Andrew Milner wrote: >> >> The file you attached loaded correctly into my edge brouser with no >> problems, but from your server I agree, no luck >> >> You may be able to force things by using .htaccess file on your server -= >> or may find the attached article points you in the right directions >> >> http://htmlpurifier.org/docs/enduser-utf8.html >> >> >> >> On Saturday, 17 June 2017 12:04:09 UTC+3, Gert Andersen wrote: >> >>> Hi >>> >>> I did some testing now and my findings are: >>> >>> - NOAA reports are generated correctly at the Raspberry >>> - NOAA reports are transferred correctly to my external server >>> - I can download them to my desktop and I can view them correctly with >>> Opera >>> - I can't view them correctly with Opera when they are located at the >>> server: >>> http://vsvejr.dk/weeWX/NOAA/NOAA-2017-06.txt >>> <http://vsvejr.dk/weeWX/NOAA/NOAA-2017-06.txt> >>> >>> I have attached the file I have downloaded to my desktop. >>> >>> Any ideas where to look? >>> >>> Rgds >>> Gert >>> >>> On Saturday, June 17, 2017 at 9:05:55 AM UTC+2, Gert Andersen wrote: >>>> >>>> Hi >>>> Thanks for the answers. >>>> >>>> I have changed to utf8, both overall and at each report. It helped, now >>>> the reports are generated correctly. The problem is now, when I see the >>>> reports with a browser, the characters are not printed correctly. >>>> >>>> I have tried Opera, Chrome, Firefox and Edge, same result. So it's a >>>> browser problem now, as Tom mentioned, and I'll try to see how I can >>>> change >>>> this. >>>> >>>> Thanks again for great support. >>>> >>>> Rgds >>>> Gert >>>> >>>> >>>> On Saturday, June 17, 2017 at 8:19:03 AM UTC+2, Andrew Milner wrote: >>>>> >>>>> try encoding = utf8 instead of encoding = html_entities at the higher >>>>> level. >>>>> >>>>> On Saturday, 17 June 2017 08:44:09 UTC+3, Gert Andersen wrote: >>>>>> >>>>>> Hi Tom >>>>>> >>>>>> Thank you for looking at this "Danish" problem >>>>>> >>>>>> In my skin.conf I have: >>>>>> >>>>>> *encoding = html_entities* >>>>>> >>>>>> * [[SummaryByMonth]]* >>>>>> * # Reports that summarize "by month"* >>>>>> * [[[NOAA_month]]]* >>>>>> * encoding = utf8* >>>>>> * template = NOAA/NOAA-YYYY-MM.txt.tmpl* >>>>>> >>>>>> * [[SummaryByYear]]* >>>>>> * # Reports that summarize "by year"* >>>>>> * [[[NOAA_year]]]* >>>>>> * encoding = utf8* >>>>>> * template = NOAA/NOAA-YYYY.txt.tmpl* >>>>>> >>>>>> I have already tried utf8 in skin.conf, so there must be another >>>>>> explanation. The reports are generated at the Raspberry, so can there be >>>>>> a >>>>>> problem there with installed language or? >>>>>> >>>>>> Thanks >>>>>> >>>>>> Gert >>>>>> >>>>>> On Saturday, June 17, 2017 at 5:10:47 AM UTC+2, Tom Keffer wrote: >>>>>>> >>>>>>> Hello, Gart >>>>>>> >>>>>>> If you look in the skin configuration file, skin.conf, you'll see a >>>>>>> section that looks like this: >>>>>>> >>>>>>> [[SummaryByMonth]] >>>>>>> # Reports that summarize "by month" >>>>>>> [[[NOAA_month]]] >>>>>>> encoding = strict_ascii >>>>>>> template = NOAA/NOAA-YYYY-MM.txt.tmpl >>>>>>> >>>>>>> [[SummaryByYear]] >>>>>>> # Reports that summarize "by year" >>>>>>> [[[NOAA_year]]] >>>>>>> encoding = strict_ascii >>>>>>> template = NOAA/NOAA-YYYY.txt.tmpl >>>>>>> >>>>>>> Change the highlighted areas to 'utf8'. This will cause the file >>>>>>> generation engine to emit UTF8 files, instead of strict ascii. >>>>>>> >>>>>>> NB: the created file is a text file (type ".txt") so, unlike an >>>>>>> HTML file, it includes *no information on the encoding it uses*. >>>>>>> Nevertheless, most browsers will figure out that there are UTF8 >>>>>>> characters >>>>>>> included in the file and do the right thing. But, this is not >>>>>>> guaranteed. >>>>>>> >>>>>>> A more robust solution would be to change the file to an HTML file. >>>>>>> >>>>>>> -tk >>>>>>> >>>>>>> On Fri, Jun 16, 2017 at 10:10 AM, Gert Andersen <[email protected] >>>>>>> > wrote: >>>>>>> >>>>>>>> Hi >>>>>>>> >>>>>>>> I'm new to weeWX and I have a question regarding Danish characters. >>>>>>>> >>>>>>>> In the NOAA report I have: >>>>>>>> >>>>>>>> Vester Sømarken, Bornholm >>>>>>>> >>>>>>>> it should be >>>>>>>> >>>>>>>> Vester Sømarken, Bornholm. >>>>>>>> >>>>>>>> >>>>>>>> I have included: >>>>>>>> >>>>>>>> #encoding UTF-8 >>>>>>>> >>>>>>>> in the NOAA templates. >>>>>>>> >>>>>>>> >>>>>>>> Any suggestions? >>>>>>>> >>>>>>>> >>>>>>>> Link: >>>>>>>> >>>>>>>> http://vsvejr.dk/weeWX/NOAA/NOAA-2017-06.txt >>>>>>>> >>>>>>>> >>>>>>>> Thanks >>>>>>>> >>>>>>>> >>>>>>>> Rgds >>>>>>>> >>>>>>>> Gert >>>>>>>> >>>>>>>> -- >>>>>>>> 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]. >>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>> >>>>>>> >>>>>>> -- 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]. For more options, visit https://groups.google.com/d/optout.
