@ChrisBarker-NOAA * The sub-issues haven't been split off. * This issue is about attributes only. * The difference between CHAR and STRING for an attribute is, essentially, which type you pick when you create the attribute. With CHAR you can't specify arrays for the value (because it already is a CHAR array) and with STRING you can.
Assuming we do spin off sub-issues related to encoding and string array attributes, I agree fully that we should, in this specific issue, propose making changes to the CF document to make it clear that CHAR attributes must be ASCII or latin-1 and STRING attributes should be unicode/utf-8. -- 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-599603557 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].
