5,838
edits
Webtags (preserving history): Difference between revisions
From Cumulus Wiki
Jump to navigationJump to search
m
→Encoding
m (→Encoding) |
m (→Encoding) |
||
|
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.
'''With that introduction, you can now choose whether to read the rest of this section which uses more technical terminology.'''
''Let me explain that technical term, essentially encoding refers to the character set used by any file''.
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.
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.
== The format used for naming ==
| |||
