Yum Install Xpdf Centos
Rochell Estrello
If this is indeed true, are there any alternatives to pdftotext that do a simple and fast conversion that would work on this server? Is it possible that the pdftotext can be complied for a different version, or that I installed it incorrectly with permissions?
To install the mysql-server you must include the MySQL Community Repo first. Visit the MySQL Yum Repository download site and find the .rpm file you need. You can download the file from the command line using wget (example shown using Red Hat Enterprise Linux 7 / Oracle Linux 7):
Main site, , has pretty good wiki for documentation and a tidy installation walkthrough. Unfortunately for me I had a ton of problems getting pdf2swf to work properly on CentOS 6.3 x86_64, but fortunately for you I finally got it working and also put together this guide, which will hopefully save you some time.
Note: swftools version that comes default with yum would not work for me hence the need to compile from source.
Note2: this guide assumes the distro is up to date and all system libraries have been installed
evince - the default document viewer on Gnome/Ubuntu, with support for PDF, PostScript, and a few other formats. Can fill forms, highlight text, and annotate. Normal text selection. Remembers window size and document zoom. Dark mode. [install]
MuPDF - extremely fast and minimalistic. Block selection by dragging with the right mouse button, search with /. Can't annotate, fill forms, sign, or anything else. Doesn't remember the zoom factor, or the window size/position. [install]
Zathura - extremely fast and minimalistic (uses the MuPDF ending via a plugin system). Keyboard-navigation, bookmarks, auto-reload on changes. Block selection by dragging with the left mouse button. No form filling or other features. Doesn't remember the zoom factor, or the window size/position. [install]
okular - Multi-format document viewer (PDF, CHM, ePub, others). Requires many KDE prerequisites unless installed as Flatpak. Can easily copy text and images. May be slow and have issues with printing. [install]
PDF Studio Viewer is a free PDF reader for Linux. It's easy to install as it is packaged as a single file with no dependencies, etc.... It has advanced viewing options (pan and zoom, screenshot, rulers & grids, thumbnail tab, digital signature tabs, bookmark tab, layer tab), printing options (preview, booklet) and search options (search within fields, annotations, recursively into folders, etc..). It can annotate PDF documents with graphical, text and markup annotations. It can fill & save interactive forms.
Many of the 32-bit dependencies needed by Adobe's 9.5.5 reader are not available In Ubuntu 18.10 or newer. Getting it working involves a very tedious process of identifying the needed files and importing them from an 18.04 installation's i386-linux-gnu directories into the corresponding places in the newer installation. I've done this on Ubuntu Studio 19.10 and 3 instances of Kubuntu 19.10 with mixed results (on one of the Kubuntu installs, it throws undefined symbol errors). I have yet to try it with the the advanced function I want to use it for (booklet printing).
You also need to install libxt-dev. The --with-Xm-... arguments to ./configure aren't necessary (in fact --with-Xm-includes=/usr/include/Xm will fail, since Motif header includes all look for files in an Xm sub-directory of the given include directory), and --with-freetype2-library=/usr/lib/x86_64-linux-gnu can be dropped too (it's the default):
It should actually be as easy as running sudo apt install tesseract-ocr. I did it a few months back and I remember having trouble with sudo aswell. I believe in the end I just had to reset my sudo password ;-) I struggled a whole day with this at the time.
apt install -y git screen mysql-server ghostscript libgraphicsmagick-dev xpdf dcraw redis-server ffmpeg exiftool libreoffice apache2systemctl enable apache2.servicesystemctl start apache2.serviceapt-get install -y software-properties-commonadd-apt-repository ppa:ondrej/phpapt install -y php7.2 libapache2-mod-php7.2 php7.2-common php7.2-mbstring php7.2-xmlrpc php7.2-gd php7.2-xml php7.2-intl php7.2-mysql php7.2-cli php7.2-zip php7.2-curl php7.2-posix php7.2-dev php-pear php7.2-redis php7.2-gmagick php7.2-gmp
This maximizes compatibility and security across all packages. Once the server OS packages are up to date, we can continue by installing the LAMP stack with Apache, MariaDB, PHP and all the other packages required by Feng Office.
PS. If you liked this post on how to install Feng Office on a CentOS 7 VPS or if you found it helpful, please share it with your friends on the social networks using the share shortcuts below, or simply leave a comment in the comments section. Thank you.
This document also provides instructionson how to get help installing and using Swish-e(and the important information you should provide when asking for help).Please read these instructions before requesting helpon the Swish-e discussion list.See "QUESTIONS AND TROUBLESHOOTING".
Swish-e knows how to index HTML, XML, and plain text documents.Helper applications and other tools are used to convert documentssuch as PDF or MS Word into a format that Swish-e can index.These additional applications and tools (listed below)must be installed separately.The process of converting documents is called "filtering".
NOTE: Swish-e version 4.2.0 installs a lot more fileswhen running "make install".Be aware that the Swish-e documentation may thus include errorsabout where files are located.Please notify the Swish-e discussion list of any documentation errors.
If you have existing indexes,you may need to re-index your databefore running the "make install" step described below.Swish-e may be run from the build directory after compiling,but before installation.
A Windows binary version is availableas a separate download from the Swish-e site ( -e.org).Many of the installation instructions below will not apply to Windows users;the Windows version is pre-compiledand includes libxml2, zlib, xpdf, and catdoc.
Swish-e makes use of a number of libraries and toolsthat are not distributed with Swish-e.Some libraries need to be installed before building Swish-e from source;other tools can be installed at any time.See below for details.
Most of the packages listed below are availableas easily installable packages.Check with your operating system vendor or install them from source.Most are very common packages that may already be installed on your computer.
libxml2 is very strongly recommended.It is used for parsing both HTML and XML files.Swish-e can be built and installed without libxml2,but the HTML parser that is built into Swish-eis not as accurate as libxml2.
If libxml2 is installed in a non-standard location(e.g., libxml2 is built with --prefix $HOME/local),make sure that you add the bin directory to your $PATHbefore building Swish-e.Swish-e's configure script uses a programcreated by libxml2 (xml2-config)to find the location of libxml2.Use which xml2-config to verifythat the program can be found where expected.
IMPORTANT:Once Swish-e is installed, do not run it as the superuser (root) --root is only required during the installation step,when installing into system directories.Please do not break this rule.
NOTE:If you are upgrading from an older version of Swish-e,be sure and review the CHANGES file.Old index files may not be compatible with newer versions of Swish-e.After building Swish-e (but before running "make install"),Swish-e can be run from the build directory:
Platforms may require varying link instructionswhen libraries are installed in non-standard locations.Swish-e uses the GNU autoconf tools for building the package.autoconf is good at building and testing,but still requires you to provide information appropriate for your platform.This may mean reading the manual page for your compiler and linkerto see how to specify non-standard file locations.
In this case,you would need to add $HOME/local/binto the start of your shell's $PATH setting.This is required because libxml2 installs a programthat is used when running the configure script.Before running configure, type:
Swish installs a number of files.By default, all files are installed below /usr/local,but this can be changed by setting --prefixwhen running configure (as shown above).Individual paths may also be set.Run configure --help for details.
Note that the Perl modules are not installed in the system Perl library.Swish-e and the Perl scripts that require the modulesknow where to find the modules,but the perldoc program (used for reading documentation) does not. This can be corrected by adding $prefix/lib/swish-eand $prefix/lib/swish-e/perl to the PERL5LIB environment variable.
The Swish-e discussion list is the placeto ask questions about installing and using Swish-e,see or post bug fixes or security announcements,and offer help to others.Please do not contact the developers directly.
Support for installation, configuration, and usageis available via the Swish-e discussion list.Visit -e.org for information.Do not contact developers directly for help --always post your question to the list.
The advantage of the -S prog method of spidering(over the previous -S http method)is that the Perl code is only compiled onceinstead of once for every document fetched from the web server.In addition, it is a much more advanced spider with many, many features.Still, as used here,spider.pl will automatically index PDF or MS Word documentsif (when) Xpdf and Catdoc are installed.
One final note about the -S prog input source method.The program specified with -i or IndexDir needs to be an absolute path.The exception is when the program is installed in the libexecdir directory.Then, a plain program name may be specified(as in the example showing spider.pl, above).
0aad45d008