themed pdf node template -- messes up my pdf for a view

Hi,

I am assuming that TYPE as you placed there is a placeholder.. I.e. for story types you would use the print.node-story.tpl.php filename..

And also, I am sorry but there's no way that the current system can enable a view to use a type-specific template, simply because views are not types..

I will take a look to see if I can understand what your problem is..

Oh, and another thing. The template file must be placed in your current theme's directory, not in the theme folder. The instructions are not so clear about that..

The template system that is used by Views and the rest of Drupal doens't apply directly to this case.. This module actually treats nodes a lot different than non-nodes (and a view is not a node)..

What gets 'printed' when you process a view is what gets output by Drupal.. So, it should be using the template you have setup for 'normal' Drupal page browsing. The way that the system is built is supposed to let you customize the output of the print view (mostly to include/exclude elements and to move things around a bit), but it was never supposed to be a mini-Drupal inside Drupal.

Your cache problem was probably some caching by your proxy or your browser's cache. You should press Shift+F5 to force a refresh to make sure in those cases

As to the quotes, what is the problem exactly?

João

Hi,

Regarding the quotes, are you using TCPDF or dompdf? I am guessing you're using dompdf, as that is the one that doesn't support UTF-8. Last night's dev has a patch that converts Unicode to ISO-8859-1 before passing it to dompdf, but that only fixes the 96 extra characters which are supported by that encoding..

I think that the curly quotes are not part of those 96, so you'll probably need to replace them with normal quotes..

João

in order to save u time w messy MS WORD single and double quotes - here's a quick'n'dirty fix how to replace them w normal quotes since DomPDF doesn't support UTF-8.

Open print_pdf.pages.inc and add t following function on top of t file AFTER require_once line:

// REPLACE ANY STUPID UTF-8 CHARS
function utf8_char_replace(&$var) {
 
    $trans_table = array(
        chr(0xe2).chr(0x80).chr(0x9a) => '\'', //SINGLE LOW-9 QUOTATION MARK
        chr(0xe2).chr(0x80).chr(0x9e) => '"', //DOUBLE LOW-9 QUOTATION MARK
        chr(0xe2).chr(0x80).chr(0xa6) => '...', //HORIZONTAL ELLIPSIS
        chr(0xe2).chr(0x80).chr(0x98) => '\'', //LEFT SINGLE QUOTATION MARK
        chr(0xe2).chr(0x80).chr(0x99) => '\'', //RIGHT SINGLE QUOTATION MARK
        chr(0xe2).chr(0x80).chr(0x9c) => '"', //LEFT DOUBLE QUOTATION MARK
        chr(0xe2).chr(0x80).chr(0x9d) => '"', //RIGHT DOUBLE QUOTATION MARK
        chr(0xe2).chr(0x80).chr(0x93) => '-', //EN DASH
        chr(0xe2).chr(0x80).chr(0x94) => '-' //EM DASH
    );
 
    foreach ($trans_table as $utf8_code => $replace) {
        $var = str_replace($utf8_code, $replace, $var);
    }
 
    return $var;
}

then, search for these lines ...

// Convert from UTF-8 to ISO 8859-1 and then to HTML entities
  if (function_exists('utf8_decode')) {
    $html = utf8_decode($html);
    
  }

and add t following call of t function BEFORE them

// REPLACE UTF-8 CHARS
$html = utf8_char_replace($html);

That's it - this should output normal quotes in t PDF!

Note: I know I shouldn't touch t code of t module - so consider my posting as a "feature request" for t next version ;-)
Hope, that helps.

Hi,

The module supports three (3) library-supported methods of converting from UTF-8 to ISO-8859-1 which is at least a bit more supported by dompdf. Then it converts those ISO-8859-1 chars to html entities to force dompdf to accept them when it can't handle the ISO chars.

That's as far as I am willing to go in fixing something that needs to be fixed by dompdf. I am certainly not planning on starting to add arbitrary char replacements. Sorry, but I must draw the line somewhere on what can be fixed on this side and what MUST be fixed on their side.

Thanks for the effort, though.. Maybe this will indeed by helpful to others.

João

Hi,

I was creating the template (see http://drupal.org/node/826638). And jcnventura you say that it has to be inside the current theme folder. Well, my current theme folder is in /sites/all/themes/[theme_name]

if I use dompdf library (0.5.1) (I don't change the dompdf_config.inc.php, I set 777 permissions on lib/fonts, and I don't installate the fonts (the fonts in /lib/fonts are: Courier, Helvetica and Times)) the following error appears in the log:

Call to undefined function spl_autoload_register() in /srv/www/htdocs/webs/evissa/sites/all/modules/print/print_pdf/print_pdf.pages.inc on line 124

Well, then I change to tcpdf library (5.0.010), and it generates the pdf well, but the template is not used...

Any suggestion?

Thanks

Well,

maybe I found the solution...

I click on generate pdf, then it generates the pdf. So the pdf file is open. If I make changes on the template and then I generate the pdf, it shows the prevously version.

So, before you click on generate pdf file, you have to close all pdf files about the node nodes you have, and then click on generate pdf.

_snake_: I can't understand if you still have a problem, or not, but please add a new issue instead of re-opening old ones.