Rostislav

The trick with PipelineDepth helped to me as well.

Thank you for the great tool and fantastic support! The solution seems to be best possible under the circumstances..

Thank you! Your approach makes full sense to me. I wonder if a NetCDF3 file with '_NCProperties' attribute set as a real attribute is a legitimate NetCDF. Meanwhile I have posted the issue here: https://github.com/Unidata/netcdf-c/issues/1572 Let us see what netcdf folks say..

Thank you! Your approach makes full sense to me. I wonder if a NetCDF3 file with '_NCProperties' attribute set as a real attribute is a legitimate NetCDF. Meanwhile I have posted the issue here: https://github.com/Unidata/netcdf-c/issues/1572. Let us see what netcdf folks say..

Failure on an .nc file that has _NCProperties attribute

Thanks for the great tool! I had to make a workaround by using channels to map remote UTF7 names to local UTF8. It would be indeed great to make the concersion transparant, so I join the feature request. Just in case, the implementation of the conversion itself can be found e.g. in mutt source code https://gitlab.com/muttmua/mutt/blob/master/imap/utf7.c

Caterpillar Cat S60: LIBMTP_Get_Storage() failed

:) Thank you!