> One more note: from #141, someone wrote: > > "In the HDF5 case, string encoding is an intrinsic part of the HDF5 string > datatype and can only be ASCII or UTF-8. " > > So that's it -- "strings will be UTF-8" we're done with that part :-).
That would be me and I got called out on this so let me set the record straight. The HDF5 library does not verify or enforce the encoding of bytes stored in HDF5 strings. The HDF5 string datatype has a tag for declaring the encoding and currently supports two values, for ASCII and UTF-8. The application is responsible for setting the correct tag value. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/139#issuecomment-433551519
