@alexmaroldi a known issue in #dompdf 0.5.1 that’s been addressed for the next release http://code.google.com/p/dompdf/downloads