Accents are not printed properly

Inserting image

Annotated image.

Hey @benjy. Patch applies cleanly. No changes though. Still seeing Archivée and sucrée.

Nope, no cigars yet ;-) No changes.

The context, although I don't think it matters, is Commerce Kickstart 2 /Omega sub-theme. I also tried with Bartik.

No luck.

Reverted last patch
Applied new patch
drush cc all
Tried as admin in FF
Tried as authenticated in Chrome

I've installed and tested entity_print in a vanilla D7. Same problem with accents. I'm in the process of pushing this to a Pantheon test environment. This raises the issue of how to install wkhtmltopdf. More on this soon I hope.

Cheers

Update.

I installed entity_print on a vanilla D7 on Pantheon.io and accents are broken in the PDF for Article nodes.

I'm not sure what more I can do.

Setting back to active as well as major since, without support for accents, the module is broken for a lot of folks.

Thanks @jordanpagewhite, your patch fixes this issue AND, upon further review, @benjy's patch in #8 also fixes this issue - apologies.

So here's what's happening. In a vanilla D7 install patches in #8 and #15 fix the broken accents issue. This applies to 7.x-1.4 and 7.x-1.x-dev.

But copy the exact same code to a Commerce Kickstart 2 (CK2) install and it doesn't work - i.e. the accents remain broken. So it is fair to assume that CK2 is preventing the new entity-print.tpl.php from doing its job.

Any idea how I can solve this, where I should look?

p.s. While uninstalling, I found a bug in entity_print.install. Line 23 reads $rid_permissions = []; I believe that should be $rid_permissions = ''; right ?

Attached, the entity_print.install from 7.x-1.x-dev

Line 22 and 23

  // Prepare permission array.
  $rid_permissions = [];

p.s. I'll report that in a new issue.

Yes, adding <meta charset="utf-8"> to entity-print--commerce-order.tpl.php fixes the broken accents issue in Commerce Kickstart. Thanks guys!

One last question. I have seen variants for this fix across different templates. Is there a definitive/best-practice one ?

Variation #1

<meta charset="utf-8">
<meta http-equiv="Content-type" content="text/html; charset=UTF-8">

Variation #2
<meta http-equiv="Content-type" content="text/html; charset=UTF-8">

Variation #3
<meta charset="utf-8">

Let me know and I'll create the patch.

After further investigation, it appears Variation #3 or <meta charset="utf-8"> is all that is required.

The attached patch adds this meta tag where it was missing (entity-print.tpl.php and entity-print--commerce-order.tpl.php).

Also, since entity_type requires PHP 5.4, I added this dependency in the .info file of the module. [Update: as of 2015-12-13, the PHP 5.4 dependency has been removed].