-PSPP is a program for statistical analysis of sampled data. It
-is a free replacement for the proprietary program SPSS.
+PSPP is a program for statistical analysis of sampled data. It is
+a free replacement for the proprietary program SPSS.
-PSPP development is ongoing. It already supports a large subset of
-SPSS's syntax. Its statistical procedure support is currently
-limited, but growing. At your option, PSPP will produce statistical
-reports in ASCII, PostScript, PDF, HTML, SVG, or OpenDocument formats.
+PSPP supports T-tests, ANOVA and GLM analyses, factor analysis,
+non-parametric tests, linear and logistic regression, clustering,
+and other statistical features. PSPP produces statistical reports in
+plain text, PDF, PostScript, CSV, HTML, SVG, and OpenDocument formats.
+It can import data from OpenDocument, Gnumeric, text and SPSS formats.
+
+PSPP has both text-based and graphical user interfaces. The PSPP
+user interface has been translated into a number of languages.
Instructions for PSPP installation are in INSTALL, including a list of
prerequisite packages and other PSPP-specific information. Full
-documentation on PSPP's language will be installed along with the
-programs.
+documentation on PSPP's language is also included.
For information on differences from previous versions, please see file
-NEWS.
-
+NEWS.
+
Source code for the latest release of PSPP is available at
-ftp://ftp.gnu.org/pub/gnu/pspp/. Older versions may be obtained from
+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
-
-The following miscellaneous notes apply to this release:
+at https://savannah.gnu.org/projects/pspp
- * On a few operating systems, such as OpenBSD, some of the
- tests may fail with messages similar to: 'Warning: cannot
- create a convertor 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. Please email bug reports to bug-gnu-pspp@gnu.org
+or file them online at https://savannah.gnu.org/bugs/?group=pspp.
-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.
+The PSPP bug tracker and bug reporting mailing list are public. To
+privately report a security vulnerability in GNU PSPP, please send
+your report to the closed mailing list pspp-security@gnu.org. The
+PSPP developers will help you assess your report and fix problems
+prior to public disclosure.
The long term goals for PSPP are ambitious. We wish to provide the
following support to users:
an "enhanced" mode in certain cases where PSPP can output
better results that may surprise SPSS users.
- * Friendly textual and graphical interfaces. This release
- includes the first version of PSPPIRE, the PSPP graphical
- user interface.
-
- * Attractive output, including graphs, in a variety of human-
- and machine-readable formats. PSPP currently produces
- output in ASCII, PostScript, PDF, HTML, and SVG formats. We
- will enhance PSPP's output formatting in the future.
+ * Friendly textual and graphical interfaces.
* Good documentation. Currently the PSPP manual describes its
language completely, but we would like to add information on
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
plug-in model does not make sense. Over the long term, it
may make sense to introduce plug-ins.
+
+For any copyright year range specified as YYYY-ZZZZ in this package note
+that the range specifies every single year in that closed interval.