Re CHAR vs STRING, the netcdf C API method calls one [text](https://www.unidata.ucar.edu/software/netcdf/docs/group__attributes.html#ga83c961529fa27b1768528e5d27cc3eb4) and other other [string](https://www.unidata.ucar.edu/software/netcdf/docs/group__attributes.html#ga0d66350856a4a6dd3f459fd092937c27). Do we want to use that language at all in whatever text is developed?
Be aware that the netcdf python library will [force the use](https://github.com/Unidata/netcdf4-python/pull/389) of strings for netcdf4 files if it sees unicode points outside of ASCII. Also be aware that LATIN-1 is not compatible with UTF-8 with code points above 127. The ISO working group maintaining these "legacy" standards (ISO-8859-n, where n=1 is LATIN-1) doesn't even exist anymore... -- 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-599672675 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].
