⇐ ⇒

[CF-metadata] Pre-proposal for "charset"

From: Chris Barker <chris.barker>
Date: Wed, 22 Feb 2017 10:56:20 -0800

Another note:

On Mon, Feb 6, 2017 at 3:08 PM, Bob Simons - NOAA Federal <
bob.simons at noaa.gov> wrote:

> * "HTML" - the chars are to be interpreted as an array of Strings with
> HTML content, using the ISO-8859-1 charset. Non-ISO-8859-1 must be encoded
> using the &#d; format where d is the decimal number of a Unicode character.
> * "XML" - the chars are to be interpreted as a an array of Strings with
> XML content, using the ISO-8859-1 charset. Non-ISO-8859-1 characters must
> be encoded using the &#d; format where d is the decimal number of a Unicode
> character.
>

Don't HTML and XML both use an ASCII-compatible header that specified the
encoding?

(and XML uses "encoding", rather than "charset"):

<?xml version="1.0" encoding="UTF-8"?>

and "the default character encoding was changed to UTF-8 in HTML5."

So if there is going to be a default, it should probably be UTF-8

We need to either specify the "string" dimension, or have a consistent
convention:

A 10x8 CHAR array could be either 10 8 character strings or 8 ten character
strings. And it gets more confusing with higher dimensions.

-CHB



-- 
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception
Chris.Barker at noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20170222/06ce8bc2/attachment.html>
Received on Wed Feb 22 2017 - 11:56:20 GMT

This archive was generated by hypermail 2.3.0 : Tue Sep 13 2022 - 23:02:42 BST

⇐ ⇒