Extracted text and test files from source code
This commit is contained in:
parent
676a7ea81c
commit
e7e66a9245
134 changed files with 0 additions and 14081 deletions
|
|
@ -1,5 +0,0 @@
|
|||
This module was created by Matt Westgate <drupal at asitis dot org>
|
||||
Maintained up to version 4.6 by Karsten Mueller <kmue at mac dot com>
|
||||
Maintained up to version 4.7 by Peter John Hartman <peterjohnhartman at gmail.com>
|
||||
Some bug fixes by David Kent Norman on Dec 20, 2005 <deekayen at: deekayen {dot} net>
|
||||
and is currently maintained by Joao Ventura <joao at venturas dot org>.
|
||||
|
|
@ -1,94 +0,0 @@
|
|||
INSTALLATION
|
||||
------------
|
||||
|
||||
Decompress the print-n.x-n.n.tar.gz file into your Drupal modules
|
||||
directory.
|
||||
|
||||
Enable the print module: Administer > Site building > Modules
|
||||
(admin/build/modules)
|
||||
|
||||
PDF TOOL
|
||||
--------
|
||||
|
||||
The print_pdf module requires the use of an external PDF generation tool.
|
||||
The currently supported tools are dompdf, TCPDF and wkhtmltopdf. Please
|
||||
note that any errors/bugs in those tools need to be reported and fixed by
|
||||
their maintainers. DO NOT report bugs in those tools in the print module's
|
||||
issue queue at Drupal.org.
|
||||
|
||||
supported paths:
|
||||
* print module lib directory (usually modules/print/lib)
|
||||
* libraries directory (libraries)
|
||||
|
||||
dompdf support:
|
||||
The dompdf tool produces results that are more faithful to the HTML
|
||||
printer-friendly page. Unicode is not supported (only ISO-8859-1).
|
||||
This tool is not supported and there are several known bugs that result
|
||||
from its incomplete implementation.
|
||||
|
||||
1. Download dompdf from http://code.google.com/p/dompdf/downloads/list
|
||||
2. Extract the contents of the downloaded package into one of the
|
||||
supported paths.
|
||||
3. Check if dompdf_config.inc.php fits your installation. In 99% of cases,
|
||||
no changes are necessary, so just try to use it and only edit anything if
|
||||
the PDF generation fails.
|
||||
4. Grant write access to the lib/fonts directory to your webserver user.
|
||||
5. If you're using dompdf-0.5.1, delete the dompdf.php file as it contains
|
||||
a security vulnerability
|
||||
6. If you're using dompdf-0.6 or later, you can try to enable the Unicode
|
||||
support, but you'll need to add some Unicode fonts. See
|
||||
http://groups.google.com/group/dompdf/browse_thread/thread/9f7bc0162b04d5cf
|
||||
for further info on this.
|
||||
7. Check http://code.google.com/p/dompdf/ for further information.
|
||||
|
||||
TCPDF support:
|
||||
TCPDF seems to be more actively developed than dompdf, but it's support
|
||||
for CSS is considerably worse. Unicode is supported (use of Unicode fonts
|
||||
result in HUGE files). Page header and footer are supported. This module
|
||||
requires TCPDF >= 4.0.000.
|
||||
|
||||
1. Download TCPDF from http://sourceforge.net/projects/tcpdf/
|
||||
2. Extract the contents of the downloaded package into one of the
|
||||
supported paths. There is no need to modify the config/tcpdf_config.php
|
||||
file, as the module self-configures TCPDF.
|
||||
3. Grant write access to the cache and images directories to your
|
||||
webserver user.
|
||||
4. Check http://tcpdf.sourceforge.net/ for further information.
|
||||
|
||||
wkhtmltopdf support:
|
||||
|
||||
1. Download wkhtmltopdf from
|
||||
http://code.google.com/p/wkhtmltopdf/downloads/list. You can choose to
|
||||
download the source and compile it or simply download the static binary,
|
||||
which doesn't require you to compile anything. Note that the compiled
|
||||
version may require a running X server (static uses patched libs that can
|
||||
work without one).
|
||||
2. Place the wkhtmltopdf executable into one of the supported paths.
|
||||
(usually libraries). You can also place a symbolic link to the executable.
|
||||
3. Check http://code.google.com/p/wkhtmltopdf/ for further information.
|
||||
|
||||
UPDATE
|
||||
------
|
||||
|
||||
When updating from a previous version, just remove the print directory and
|
||||
follow the instructions above. Make sure that you backup any costumization
|
||||
to the print.tpl.php and print.css files.
|
||||
|
||||
ROBOTS
|
||||
------
|
||||
|
||||
Even though it is possible to set per-page robots settings, the following
|
||||
can be placed in your robots.txt file after the User-agent line to prevent
|
||||
search engines from even asking for the page:
|
||||
|
||||
Disallow: /print/
|
||||
|
||||
Also, for updates from older versions (<=4.7.x-1.0 and <=5.x-1.2) which used
|
||||
node/nnn/print instead of print/nnn, the following lines can prevent
|
||||
requests from Google for the obsolete print URLs:
|
||||
|
||||
Disallow: /*/print$
|
||||
|
||||
Note that pattern matching in robots.txt is a Google extension (see
|
||||
http://www.google.com/support/webmasters/bin/answer.py?answer=40367 for more
|
||||
information).
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
PRINT MODULE
|
||||
M: Joao Ventura <joao at venturas dot org>
|
||||
S: maintained
|
||||
|
|
@ -1,5 +0,0 @@
|
|||
Instead of placing the downloaded external libs (such as TCPDF, dompdf,
|
||||
etc.) used by the print module here, you should place them in libraries.
|
||||
|
||||
This directory is still a valid location for them, however. The Libraries
|
||||
API module library path is also valid.
|
||||
Reference in a new issue