Reiner has asked that papco be able to export to a rich ascii file, and to a CDF file.
My recollection is the CDF file is very close. I think I can dump a papco_dataset out to a cdf file, so I might just need to make the adapter in the papco output code.
For rich ascii, I'm just copying and hacking the ascii code to include additional metadata in the output.
Another thing to consider with this is to change (or provide) an interface that takes papco_datasets. The problem is, for example, I can't specify units in the rich ascii formatting because I don't have them. I could add a keyword, but then the interface continues to grow. Essentially the API for the export data is a data model, and this would be fixed by simply passing QDataSets and providing an adapter for legacy operations...