Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
steve wrote:Does Mark's suggestion not work for you?
No it doesn't work.
I've tried several combinations and the only one that works is:
- the charset is set to UTF-8
- Cumulus otput (NOAA report) file is in UTF-8 format.
You can see it here: http://www.pogoda-niesiolowice.kaszuby. ... hp?yr=2012 (I purposely put there some other characters from my national language - ś ć ę ż ź ń- you can see them at the right-top of the report):
BTW. This problem (output format of the Cumulus) is related also to the e.g forecast generated by Cumulus. It uses words from "strings.ini" file. They are processed and being sent to web server (in ANSI format I think). So when "strange" (e.g my national) characters are used in the "strings.ini" file you see "black diamonds" in the forecast text too. Probably if the output of the forecast were in UTF-8 format it would have solved this problem too.
Best Regards,
Piotr
The day when I have learned something is not the lost one.
Ignorance can be corrected with the help of a book. Stupidity requires a shotgun and a shovel.
beteljuice wrote:Piotr - you have several </head></body> in your page.
ATM things look alright to me
Try to get the spurious tags out of your page.
I did it. Thanks for your comments. I'm not an expert in html and php so, it must take time untill i can clean my pages up (I'm still trying to learn).
Best Regards,
Piotr
The day when I have learned something is not the lost one.
Ignorance can be corrected with the help of a book. Stupidity requires a shotgun and a shovel.
Thank you very much Steve. You are quick and helpful as usual. I have installed this new version, changed the NOAA report save format and let's hope that this will "save my life". Unfortunately I have to wait until tomorrow.
Is there any hope for "forecast words" format change?
Best Regards,
Piotr
The day when I have learned something is not the lost one.
Ignorance can be corrected with the help of a book. Stupidity requires a shotgun and a shovel.
pernaczy wrote:Is there any hope for "forecast words" format change?
That would need the code which saves the processed web pages to change, and I don't think there is the same option with the code that does that, so I would probably have to rewrite a few sections of code. But I'll look into it; as I understand it, web pages are supposed to be UTF-8 now anyway?
steve wrote:as I understand it, web pages are supposed to be UTF-8 now anyway?
I'm not an expert, but I think that UTF-8 is (probably) the most convenient format for many "strange" languages (as mine is).
Going back to NOAA reports. The modification you have done to the latest version of CUMULUS (NOAA reports can be saved in UTF-8 format) doesn't work. I set up this option yesterday and unfortunately both "todays" files (NOAAYR2013.txt and NOAAMO0513.txt) have been saved in ANSI format. You can check it on my web page. Only those two have "black diamonds". All other reports I saved manually yesterday in UTF-8 format.
Best Regards,
Piotr
The day when I have learned something is not the lost one.
Ignorance can be corrected with the help of a book. Stupidity requires a shotgun and a shovel.
pernaczy wrote:Going back to NOAA reports. The modification you have done to the latest version of CUMULUS (NOAA reports can be saved in UTF-8 format) doesn't work. I set up this option yesterday and unfortunately both "todays" files (NOAAYR2013.txt and NOAAMO0513.txt) have been saved in ANSI format.
That's impossible! I tested it and it works!
But actually, I only tested the 'manual' saving, I forgot that the automatic saving is separate code
I'll change the other code and upload a new build later today.
mcrossley wrote:Well, UTF-8 is now the default for HTML5 and will cover virtually all use cases, for other HTML/XHMTL standards it is still a minefield.
So I could change the standard Cumulus web pages to HTML5, and change the encoding to UTF-8, but if I change the encoding (without it being optional) for 'extra' files (and where people had replaced the standard files with others), that may cause people problems?
The day when I have learned something is not the lost one.
Ignorance can be corrected with the help of a book. Stupidity requires a shotgun and a shovel.