X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?p=pspp;a=blobdiff_plain;f=README;h=36e9c4a90be1816389a94f243e023c45c310110d;hp=da94b711fc047e80940d13bcafa0885ada2311e6;hb=refs%2Fheads%2Flexer;hpb=6bae018e92d45abceef4224117a147f87f2853a9 diff --git a/README b/README index da94b711fc..36e9c4a90b 100644 --- a/README +++ b/README @@ -1,23 +1,33 @@ -PSPP is a program for statistical analysis of sampled data. It -interprets commands in the SPSS language and produces tabular output -in ASCII, PostScript, or HTML format. +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 transformation language. Its statistical procedure support is -currently limited, but growing. +PSPP supports T-tests, ANOVA and GLM analyses, factor analysis, +non-parametric tests, and other statistical features. PSPP produces +statistical reports in plain text, PDF, PostScript, CSV, HTML, SVG, +and OpenDocument 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. +prerequisite packages and other PSPP-specific information. Full +documentation on PSPP's language is also included. For information on differences from previous versions, please see file -NEWS. Full documentation on PSPP's language can be found in the doc/ -directory. +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://alpha.gnu.org/gnu/pspp/. Development sources are available from -CVS at http://savannah.gnu.org/projects/pspp - +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: + + * 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. 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 @@ -31,8 +41,7 @@ following support to users: supports a large subset of it. * All the statistical procedures that someone is willing to - implement, whether they exist in SPSS or not. Currently, - statistical support is limited, but growing. + implement, whether they exist in SPSS or not. * Compatibility with SPSS syntax, including compatibility with known bugs and warts, where it makes sense. We also provide @@ -43,11 +52,6 @@ following support to users: 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, and HTML formats. We will - enhance PSPP's output formatting in the future. - * Good documentation. Currently the PSPP manual describes its language completely, but we would like to add information on how to select statistical procedures and interpret their @@ -56,8 +60,9 @@ following support to users: * Efficient support for very large data sets. For procedures where it is practical, we wish to efficiently support data sets many times larger than physical memory. The framework - for this feature is already in place, but it has not been - tuned or extensively tested. + for this feature is already in place. It has not been tuned + or extensively tested, however initial experience has given + impressive results. Over the long term, we also wish to provide support to developers who wish to extend PSPP with new statistical procedures, by supplying the @@ -80,3 +85,6 @@ following: 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.