ub-mannheim / ape Goto Github PK

APE printind is based on incoming HTML mails that are created by Alma. These mails are based on tons of different templates containing multiple fields and elements.

It could be useful to clean up things and modularize and possibly share the most used templates.

Ensure that the latest PhpMimeMailParser Version (https://github.com/php-mime-mail-parser/php-mime-mail-parser) is working with APE.

Creation of a status map / flow chart for a better understanding of containing elements, processes and relations between components

Is it possible to add additional fonts like Chinese? At the moment non contained fonts cannot be printed, fields are emtpy in pdf.

There are newer releases available on GitHub, maybe with relevant bug fixes.

We should update the code and could either include php-mime-mail-parser as a git submodule or use a package from the Linux distribution (if available).

Remove hard coded wkhtmltopdf binary and add to config file.

Line: 218 $convert_cmd = "/usr/local/bin/wkhtmltopdf -q ".$q_filename." ".$q_pdf;

Filter function (date, category, ...) for certain print items requested. Could be realized with a webform, that lets the user select a range of entries and print them (again) directly from the web interface.

In this case there was a printer error so the items have been sent but not printed and therefore should be printed again the next day.

Note: This is only relevant for updating older installations

Issue: The release change from wkhtmltopdf 0.12.3 to 0.12.4 changed handling of different screen-resolutions. This led to a number of size issues, documented in wkhtmltopdf/wkhtmltopdf#3241. The fix, release 0.12.5 still renders fonts smaller than 0.12.3 did. Especially for hold shelf slips our staff very much wanted to keep the previous size.

Fix: Adding the parameter --disable-smart-shrinking in the 0.12.5 production chain resulted in printouts matching their counterpart from the system running 0.12.3

For sites starting out with 0.12.5 this would probably not be necessary since they would start their design process with the scaling as-is.

Think about expanding the config file print.conf, add additional values. Which other elements may be useful?

Treatment of special signs in title and signature has to be re-evaluatedand corrected. For example there are problems if the signature contains slashes "/"