From ac97c51273f9d180eb492adc3643729973dab6dd Mon Sep 17 00:00:00 2001 From: Ben Pfaff Date: Mon, 27 Feb 2023 10:00:48 -0800 Subject: [PATCH] Update README. The PSPP output subsystem is now pretty good and I don't think that it's necessary to include it as future work anymore. I haven't heard anything about OpenBSD in a while, so I don't think it's necessary to list its tests as an explicit caveat. These days I tend to prefer hearing bug reports via email. --- README | 23 ++++------------------- 1 file changed, 4 insertions(+), 19 deletions(-) diff --git a/README b/README index 9cc48a8364..4d86641692 100644 --- a/README +++ b/README @@ -20,20 +20,11 @@ NEWS. Source code for the latest release of PSPP is available at ftp://ftp.gnu.org/pub/gnu/pspp/. Test releases are at ftp://alpha.gnu.org/gnu/pspp/. Development sources are available -at http://savannah.gnu.org/projects/pspp +at https://savannah.gnu.org/projects/pspp -The following miscellaneous notes apply to this release: - - * On a few operating systems, such as OpenBSD, some of the - tests may fail with messages similar to: 'Warning: cannot - create a converter for "646" to "UTF-8"'. These test - failures may safely be ignored. - -Questions and comments about using PSPP may be sent to pspp-users@gnu.org. -Bug reports may be filed at http://savannah.gnu.org/bugs/?group=pspp -or emailed to bug-gnu-pspp@gnu.org. We prefer the web-based system -because it makes it more difficult for us to lose track of bugs, but we -are happy to hear from users through any means. +Questions and comments about using PSPP may be sent to +pspp-users@gnu.org. Please email bug reports to bug-gnu-pspp@gnu.org +or file them online at https://savannah.gnu.org/bugs/?group=pspp. The PSPP bug tracker and bug reporting mailing list are public. To privately report a security vulnerability in GNU PSPP, please send @@ -79,12 +70,6 @@ following: constructs. We wish to improve the situation by supplying a more complete and flexible parser generator. - * Easy-to-use support for producing attractive output. - Currently, output is done by writing code to explicitly fill - in table cells with data. We should be able to supply a - more convenient interface that also allows for providing - machine-readable output. - * Eventually, a plug-in interface for procedures. Over the short term, the interface between the PSPP core and statistical procedures is evolving quickly enough that a -- 2.30.2