Brian Sweeney
Brian Sweeney
Looks interesting. We'd like to avoid merging changes directly into the master branch where possible. Target your changes to the develop branch and we'll take a closer look.
If you have time to fix up this PR I'd be grateful. Still seems like a potentially good fix and I'll look at it more for the next release.
I'm not even having that much luck. Which version of dompdf are you using? Might help to see the HTML+CSS you're using. There are a few things about the demo...
Yikes. Not sure what's changed between 0.6 and 0.7 to cause this. I was about to release the final 0.7 but I think we'll need to fix this first.
Might be a problem in specific versions of PHP. The issue does not appear to be present when using PHP 5.6.
I think the `cloneNode` issue is unrelated, see #1027. I did run across another error while looking into this. I think it's probably unrelated, but until I do more research...
When we took out the dompdf_config.inc.php file for 0.7.0 we forgot to put the `mb_internal_encoding('UTF-8')` call, which ensures that MBString functions parse text as UTF-8 encoded string, elsewhere in the...
FYI, for a temporary fix you can just add `mb_internal_encoding('UTF-8');` somewhere in your PHP code prior to using dompdf.
The fatal error I [noted earlier](#issuecomment-187880503) also appears to be addressed by setting the internal encoding. However, I think we need to look into this a bit more. Even if...
Share a sample of your HTML+CSS and we'll take a look.