Documentation updates

docs/releases/0.12.2.rst

@@ -72,6 +72,10 @@ and Tilmann Sittig.
 
 Statistics gathering
 ~~~~~~~~~~~~~~~~~~~~
+Previous attempts at gathering usage statistics have been met with deficient results.
+User participation in surveys as well as the quality of the data entered by users
+was disappointing.  That is why this version of **Mayan EDMS** features an
+anonymous statistics gathering functionality.
 
 
 Upgrading from a previous version
@@ -86,6 +90,7 @@ Migrate existing database schema with::
     $ ./manage.py migrate common 0001 --fake
     $ ./manage.py migrate common
     $ ./manage.py migrate checkouts
+    $ ./manage.py migrate installation
 
 The upgrade procedure is now complete.
 

docs/topics/document_visualization.rst

@@ -21,7 +21,6 @@ previews are then created on demand for the different sizes requested
 (thumbnail, page preview, full preview) and rotated interactively
 in the details view.
 
-
 Office document conversion however won't always work as expected because
 LibreOffice_ do not provide proper API's, so subprocess calling,
 temporary files and other black magic needs to be invoked to get it
@@ -30,6 +29,13 @@ or frames, and text extraction and OCR is done per page not per document,
 thats why even text documents need to be rendered by LibreOffice_
 before they can be previewed and text can be extracted.
 
+Version 0.12.1 introduced a new method of converting office documents, this
+new method doesn't require the use of the command line utility ``UNOCONV``.
+If this new method proves to continue working better than previous solutions the use
+of ``UNOCONV`` may be deprecated in the future.  The new conversion method
+adds just one new configuration option: :setting:`CONVERTER_LIBREOFFICE_PATH`
+which defaults to '/usr/bin/libreoffice'.
+
 
 .. _PDF: http://en.wikipedia.org/wiki/Portable_Document_Format
 .. _LibreOffice: http://www.libreoffice.org/

docs/topics/ocr.rst

@@ -10,9 +10,12 @@ processing by settings this options to 0, with other machines or cloud
 instances then connected to the same database doing the OCR processing.
 The document is checked to see if there are text parsers available, is
 no parser is available for that file type then the document is passed
-to tesseract page by page and the results stored per page, this is to
+to Tesseract_ page by page and the results stored per page, this is to
 keep the page image in sync with the transcribed text.  However when
 viewing the document in the details tab all the pages text are
-concatenated and shown to the user. Setting the :setting:`OCR_AUTOMATIC_OCR`
+concatenated and shown to the user.  All newly uploaded documents will be
-option to ``True`` would cause all newly uploaded documents to be
+queued automatically for OCR, if this is not desired setting the :setting:`OCR_AUTOMATIC_OCR`
-queued automatically for OCR.
+option to ``False`` would stop this behavior.
+
+
+.. _Tesseract: http://code.google.com/p/tesseract-ocr/

docs/topics/signatures.rst

@@ -22,3 +22,11 @@ functionality in the ``Setup menu``
 From this menu, key servers can be queried 
 and the results imported.  Public keys no longer needed can also be deleted 
 from this menu.
+
+Only `GNU Privacy Guard`_ signatures are support at the moment.  In case 
+your installation of GnuPG is non-standard, you can use the :setting:`SIGNATURES_GPG_HOME`
+configuration option to let **Mayan EDMS** find your GPG instance's home directory, used to
+store keyrings and other GPG configuration files.
+
+
+.. _`GNU Privacy Guard`: www.gnupg.org/