BUG: collated: correctly handle ascii writing. See #1545.
The collated container ('decomposedBlockData') is always binary but the 'payload' might be ascii so use that header information instead of the decomposeBlockData header.
Probably not really a bug. The
archinformation is only emitted for binary files since we don't want to add additional noise to ASCII files and more importantly we'd like to avoid people accidentally adding in incorrect
archinformation when copying across (ASCII) config files to another setup.
However, for the decomposed blocks, there should not really be a situation in which the collated container and the payload could have different label/scalar sizes. We only support the native sizes when writing, for the ASCII payload they are simply just missing (suppressed).