X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=README;h=35e44ae7421f006b5b64c91f49c537f04bf46e77;hb=11210e8190261d1ab630b1a56f6c0a44a5e82419;hp=07aae20ac94ee36dd7992d094043419af862dc19;hpb=b6af9f0d947384b5be3025877cbf4fddff2094ff;p=pspp-builds.git diff --git a/README b/README index 07aae20a..35e44ae7 100644 --- a/README +++ b/README @@ -4,7 +4,7 @@ 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, or HTML formats. +reports in ASCII, PostScript, PDF, HTML, SVG, or OpenDocument formats. Instructions for PSPP installation are in INSTALL, including a list of prerequisite packages and other PSPP-specific information. Full @@ -21,12 +21,6 @@ at http://savannah.gnu.org/projects/pspp The following miscellaneous notes apply to this release: - * If you use GCC 4.3 or later to compile PSPP, along with any - version of the GNU Scientific Library (GSL) released as of - this writing (June 2008), then you will need to specify the - -fgnu89-inline flag to the compiler on the "configure" - command line: "./configure CFLAGS=-fgnu89-inline". - * 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 @@ -58,8 +52,8 @@ following support to users: * 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. + output in ASCII, PostScript, PDF, HTML, and SVG 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 @@ -94,3 +88,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.