This new release comes after nearly two years of work and as always, also brings new features such as those described below:
As always, a new release, you must fix the detected errors, both by developers and by users.
Updating third-party libraries:
Also updated to the latest versions all third-party libraries to have as current as possible and above code, free of security breaches, as far as possible.
Processing text using Tesseract OCR engine:
This feature allows SaltOS get texts and indexing images in the database to improve search quality. To do this, SaltOS uses the Tesseract (https://code.google.com/p/tesseract-ocr/ and http://es.wikipedia.org/wiki/Tesseract_OCR) project which was released as open source in year 2005 by Hewlett Packard and the University of Nevada, Las Vegas. Tesseract is currently developed by Google and distributed under the Apache License, Version 2.0.
SaltOS also applies corrections to obtain results pages texts and thus able to process invoices, receipts and other documents that can be processed as product listings, details of invoices or delivery notes or anything integrators need SaltOS .
Improved SaltOS's search engine:
The new search engine SaltOS now incorporates two types of searches: all SaltOS or all files. This allows you to find what you want in all records of the entire database or all the contents of all files that have been processed SaltOS.
To do this, SaltOS relies on an engine called Mroonga (Fast Fulltext Search Engine). This search engine allows SaltOS achieve response times of the order of 100ms, instead of the previous n seconds that could take in return results. To use this feature, simply use MariaDB from version 10.0.15 (https://mariadb.com/kb/en/mariadb/about-mroonga/) or use the CentOS's image that we distribute with a pre-installed and pre-configured system (http://download.saltos.org).
Update to Google API v3:
As discussed in a previous post, in early January, the timing of the agenda SaltOS with Google Calendar stopped working after the close of the service by the old APIs, which had to do the R & D necessary to to update the access code Google Calendar and thus able to regain operate this provision as used SaltOS. One of the things I had to do also is investigating how to get the token authentication without putting the user or key manually in the login of Google, but who wants more details of this story, see the post Transparent access (login) to Google API v3
New SaltOS documentation:
After several attempts to make a user documentation for SaltOS, Jordi Company, has been put to work and made the big step of providing all the applications SaltOS its corresponding User Manual. The writing process is done using the T2T format, which means txt2tags (http://txt2tags.org/) allows for LaTeX and HTML code, ideal for generating DPFs files and to integrate it in our website. For more info: