[The developments mentioned here are in CVS but not yet in the snapshots -- I'm waiting until the new "save data as binary" facility has stablized before I prepare new snapshots, but hopefully that should happen soon.] 1. The bug reported by Artur in http://lists.wfu.edu/pipermail/gretl-devel/2014-January/004875.html is fixed. 2. Binary data files: I've now implemented Jack's suggestion in http://lists.wfu.edu/pipermail/gretl-devel/2014-January/004872.html So here's how things stand: the --binary option to "store" is gone; instead, to save data as binary, use the new ".gdtb" filename extension, as in store foo.gdtb <optional-series-list> This results in creation of a zip file containing data.xml (metadata) and data.bin (binary component). The compression level of the zip file is governed by the --gzipped option, with a default level of 1 (relatively fast, "light" compression). The binary data option is not yet fully represented in the GUI. Before I do that I'd like to get reactions to a suggestion. Obviously, adding a new native datafile type will complicate the GUI somewhat. At the same time I'd like to remove some old complexity that I think is no longer needed. Under the menu "/File/Open data" we have both "User file", which leads to a file selector equipped with a long list of file types (both native and "import" formats) and an "import" item which lists the supported import formats. I'd like to get rid of the "import" item since it really just repeats in a different form what's available under "User file". And similarly for the "Append data" menu: I'd like to switch to a single file selector with a drop-down list of filters. There's one possible downside of this, but I doubt that it's a real issue. That is, suppose one has a misnamed file (e.g. a plain text file with ".xls" extension). In principle you could handle this by selecting "text/CSV" from the current import menu (hence forcing the interpretation of the file) and then using the "All files" filter in the dialog, or manually typing the spurious filename. The option of pre-forcing the interpretation of a file regardless of its name would be gone under my suggestion. But how many users have ever done this sort of thing? (Besides, this is a work-around for a problem that has an obvious and simple correct solution: rename the file in question. If you're smart enough to figure out that the "import" menu allows you to work around broken filenames, you're smart enough to fix the file!) Allin