Webtags (preserving history): Difference between revisions

m
Line 39: Line 39:
== Encoding ==
== Encoding ==


You can skip this section, but if you have problems with a web page not displaying the '''°''' symbol correctly, it will be because the character set encoding is either not declared or not consistent. Put simply, most modern web pages use "utf-8" encoding, but for historical reasons Cumulus defaults to producing files in ISO-8859-1 encoding. This causes the mismatch.  
If you have problems with a web page not displaying the '''°''' symbol correctly, it will be because the character set encoding is either not declared or not consistent. Put simply, most modern web pages use "utf-8" encoding, as do the standard web templates included with Cumulus, but for historical reasons Cumulus defaults to producing report files in ISO-8859-1 encoding. This causes the mismatch.  


To add just a little more detail here, if you choose to implement a web page to display these Cumulus reports, then the HTML of the web page to display the report, the JavaScript that selects which report to show, and inserts the report into the HTML, and the report itself must all use the same encoding, to avoid problems with displaying correct characters.
To add just a little more detail here, if you choose to implement a web page to display these Cumulus reports, then the HTML of the web page to display the report, the JavaScript that selects which report to show, and inserts the report into the HTML, and the report itself '''must all use the same encoding''', otherwise you will not get characters like ° displaying correctly.
 
In April 2014, Steve introduced the choice in Cumulus 1 of either ISO-8859-1 encoding (as he used originally) or UTF-8 encoding (what he migrated his web page templates to) for these reports.  For backwards compliance, the default selected by Steve Loft is his original ISO-8859-1 encoding, but his recommendation strongly expressed was that users should switch to UTF-8. This choice  with the former as default, but the latter as recommended, remains unchanged in MX.  The encoding for NOAA reports can be selected on the NOAA Settings screen of either Cumulus 1 or MX, and you are as Steve says strongly advised to reverse the setting.
 
Before I go into any more technical detail, this same advice of selecting "UTF-8" applies to any choices on the '''Extra web files''' in MX (or Files tab of internet settings in Cumulus 1).


'''With that introduction, you can now choose whether to read the rest of this section which uses more technical terminology.'''
'''With that introduction, you can now choose whether to read the rest of this section which uses more technical terminology.'''
Line 55: Line 59:
If you use 7 bits, you have 127 combinations, enough for standard 26 letters in both capitals, and lower case, plus 10 digits (0 to 9), some punctuation, and some control characters (like new line, end of file, and so on). If you use 8 bits, a whole byte, you have 254 combinations, and you can start coping with accented letters, with alphabets that don't have 26 letters, and even add some symbols. Obviously, once you start using more than one byte, you can have 16, 32, 64, or even more bits to use and can include lots more characters and the bigger character sets start including lots of symbols and the biggest add smilies or emotion icons.  
If you use 7 bits, you have 127 combinations, enough for standard 26 letters in both capitals, and lower case, plus 10 digits (0 to 9), some punctuation, and some control characters (like new line, end of file, and so on). If you use 8 bits, a whole byte, you have 254 combinations, and you can start coping with accented letters, with alphabets that don't have 26 letters, and even add some symbols. Obviously, once you start using more than one byte, you can have 16, 32, 64, or even more bits to use and can include lots more characters and the bigger character sets start including lots of symbols and the biggest add smilies or emotion icons.  
   
   
In April 2014, Steve introduced the choice in Cumulus 1 of either ISO-8859-1 encoding (as he used originally) or UTF-8 encoding (what he migrated his web page templates to) for these reports.  For backwards compliance, the default selected by Steve Loft is his original ISO-8859-1 encoding, but his recommendation strongly expressed was that users should switch to UTF-8. This choice  with the former as default, but the latter as recommended, remains unchanged in MX.  As a user you need to be aware the encoding you choose for these reports should match the encoding of any web page used for viewing these reports, and
the encoding of any scripts you use to select and read the report. The encoding can be selected on the NOAA Settings screen of either Cumulus 1 or MX.
Remember, most modern web pages (including the standard web templates provided with both flavours of Cumulus) use UTF-8 encoding.
Remember, most modern web pages (including the standard web templates provided with both flavours of Cumulus) use UTF-8 encoding.


5,838

edits