On Wed, 21 Jul 2021, Sven Schreiber wrote: > I have a bit of a deja-vu feeling, but with a July snapshot I (still?) > see the behavior that when I save a dataset to the gdtb format, the > following happens: > > - I'm being shown a compression setting, which doesn't seem to have any > effect, however. I kind of remember that compression is not intended for > gdtb, but that we discussed at some point that it should then be > greyed out. > > - I also get a choice about which binary gdtb format to use, and I > believe that was supposed to be only a transitory thing and should not > be offered anymore. The two points are linked: older gdtb files were zipfiles, and if we were offering old formats for compatibility we couldn't just disable the compression-level choice when gdtb was selected. That's now updated in git. * We don't offer the legacy gdtb options any more. * We disable the compression choice when gdtb is selected. * We put up a warning on a gdtb save, pointing out that such files can't be read by gretl < 2020b. I guess we can dispense with the warning at some point, but 2020a is not really ancient yet.