html entities converted erroneously

[bigpupil]

Symbols like the registration mark are being converted and showing up as boxes with question marks in them, rendering premailer generated markup unusable. Please correct so premailer functions as it previously did, where html entities where left as is.

[Studly]

I'm having this same problem with HTML code like:
  (non breaking space)
© (copyright symbol)

Premailer converts it into a funky character, which in an email client shows up as a question mark in a diamond. Premailer didn't use to do this ... just started about a month ago for me.

[Studly]

In my post above, I pasted the HTML for non breaking space and copyright, but it's not showing the code ... it just shows the character. But basically premailer is having a problem with HTML code that begins with "&" such as the code for non breaking space and the code for copyright symbol.

[refringe]

It's decoding HTML entities. And I agree, it shouldn't.

[egid]

My hacky solution for this is to remove the charset from the meta header tag. I had UTF-8 prior and it would screw it all up.

Here's how I'm rolling for now: <meta http-equiv="Content-Type" content="text/html" />

[bigpupil]

That IS a hacky egid workaround. Better than inlining your own styles I guess. Ok so it seems the error pre mailer is experiencing is related to the way it is treating the document because of how it's enterpeting (or misenterpreting) the doctype. Anyone have suggestions for a fix?

[egid]

As a side note, my hack also solves the problem of the #&13; carriage return encoding at the end of every line. I'm just a web guy, so I unfortunately can't offer any insights into the workings of the premailer.

[joevandyk]

I think the reason for this is premailer forcing the encoding to ASCII-8BIT. I'm not sure why it's doing that.

[mehas]

My hacky solution for this is to remove the charset from the meta header tag. I had UTF-8 prior and it would screw it all up.

Here's how I'm rolling for now: <meta http-equiv="Content-Type" content="text/html" />

This sort of works, but changes the encoding. For example, – (en dash) is changed to –.

[olivierlacan]

Same problem here. Straight UTF-8 characters produce errors, and HTML entities too.

[tomblomfield-zz]

I'm having this problem too.

£ gets encoded as =EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD

💩

[mehas]

for now I switched to the Mailchimp CSS Inliner tool: http://beaker.mailchimp.com/inline-css

[refringe]

I've been using the Mailchimp tool as well. Premailer has, unfortunately, been unusable for almost half of a year now. It's a shame it can't be reverted back to a previous, working version.

[sethbro]

Using Rails 3 and Premailer through https://github.com/fphilipe/premailer-rails3, I encountered this problem & was able to solve by explicitly setting the encoding to UTF-8.

# config/initializers/premailer.rb

PremailerRails.config.merge!(input_encoding: 'UTF-8')

[geetarista]

@sethbro Isn't that the default?

[sethbro]

For premailer-rails3, yes. I failed to control for something & this isn't the fix I thought.

For Premailer itself, ASCII-8BIT is the default input encoding (https://github.com/alexdunae/premailer/blob/master/lib/premailer/premailer.rb#L211), so that's probably worth setting in your own app.

[geetarista]

Aha! Thanks @sethbro.

[akzhan]

Duplicates #30.