Additionally, the netcdf standard itself has support for UTF-8 variable names, requires them to be [NFC](https://en.wikipedia.org/wiki/Unicode_equivalence#Normal_forms), and specifically excludes bytes [0x00 to 0x1F and 0x7F to 0xFF](https://www.unidata.ucar.edu/software/netcdf/docs/file_format_specifications.html) (see the "name" part of that document).
I think this matters because at least one of the [standard attributes ](http://cfconventions.org/Data/cf-conventions/cf-conventions-1.8/cf-conventions.html#ancillary-data) needs to be able to refer to variable names. Basically, allowing anything other than UTF-8, especially things that allow bytes 0x7F to 0xFF (like the ISO-8859 series encodings do), would probably cause actual problems. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/141#issuecomment-599690108 This list forwards relevant notifications from Github. It is distinct from [email protected], although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to [email protected].
