Martin Yeo

#488 fixes, just waiting for a release now.

@pelson we're often battling with a tricky compromise between: - The 'right' solution. In this example that would be getting CF to adopt a without-implementation units standard. - A pragmatic...

Ah, sorry @tkoyama010, I did try to look for existing issues but I guess I didn't get my search terms correct.

From @SciTools/peloton: We prefer the simpler solution of 1 new parameter: `colorbar`, which defaults to `True`. If the user wants a customised colorbar then they should use `False` then add...

>Just so I understand the problem, I assume it is not enough to have a handle to the `colorbar` instance so you can adjust stuff? I have been led to...

This new activity has prompted a very useful discussion in @SciTools/peloton: NetCDF only supports ASCII (i.e. every character must be 1 byte). Iris _could_ do something with non-ASCII characters, but...

> I am not sure I understand what you mean with "NetCDF only supports ASCII (i.e. every character must be 1 byte)". Is the problem specific to string/char auxiliary coordinate...

Will consider this for 3.15

> Will consider this for 3.15 ... by which I mean we should make it easy - and documented - for users to define their own encode/decode routine.

> Opened [python/cpython#133967](https://github.com/python/cpython/issues/133967) to ask if this is a bug or intended behaviour. @bouweandela can you confirm this was fixed in Python 3.13.5? https://docs.python.org/3/whatsnew/changelog.html#id3