Foundation-emails:   is converted to  

[mkelley82]

  is converted to  

This happens during the conversion process..

[davidhouweling]

I also have a similar issue with ' being shown in the email as '

[REJack]

thats happened with > & < too, formerly it transform every & to &

[rafibomb]

Are you using the web inliner or the npm run build command?

[REJack]

@rafibomb i used the web inliner

[davidhouweling]

I'm using the npm run build, getting the result of that and emailing it through nodemailer to an address being consumed by Outlook.

[jasonlmann]

I'm seeing the ' issue using npm run build and npm run litmus

[REJack]

with npm run build i get no failures

[mkelley82]

I am seeing it happen with the inliner.

[rafibomb]

Looks like this is not an inliner issue.

If you are using npm start and not inlining, then view page source - it seems that you still see the character is converted. It seems to be related to Cheerio which is used in Inky. Working to track that down.

[rafibomb]

There is a Cheerio option to prevent the characters from being converted. We're testing the option here: https://github.com/zurb/inky/tree/fix-character-escaping

It would help resolve this sooner if you can test this fix out by pointing your package.json inky dependency to this branch and running npm update

[rafibomb]

Added test cases here: 9a09698

[jasonlmann]

I can confirm this works for the apostrophe / ' issue.

I'm kinda new to Github. Is that commit you linked to just for reference or did you want us to leave comments on it to confirm it's working?

[coreyschaaf]

@rafibomb i tried the fix above and the issue that I had with
<< >> causes the parser to just stop working. Which means I would have to go through about 20 emails where dynamic content is injected just to get it to inline correctly. However, I tried to go back to what I had before and now the inliner will not work for me as it did before. It keeps erroring when it gets to the double brackets for the dynamic code that's injected by my email provider.

[Fender123]

Seems to fix most problems. No more escaped quotes.

But comparing the output of this branch with 2.1 stable, I noticed that = characters in urls get escaped with =. Not sure if they will work like expected.

Edit: Chrome handles the urls fine. But I can't test on Outlook and other mail programs
Example: https://test.com?utm_source=test&utm_medium=test&utm_campaign=test

[rafibomb]

Resolved by https://github.com/zurb/inky/pull/57

@coreyschaaf We added a <raw> tag that you can wrap HTML with to not convert or not run through Inky. It's in the develop branch on Inky now. The Inliner may still convert it but at least Inky does not.

Use it like this:
<raw><<LCG Program\TG LCG Coupon Code Default='246996'>></raw>

[rafibomb]

@Fender123 The branch has been updated and since merged into develop because it passed testing. Can you add a test case for the URL piece you're referring to here? https://github.com/zurb/foundation-emails/blob/develop/test/visual/pages/inliner-bugs.html

[rafibomb]

@jasonlmann Good question! When a potential fix is pushed it does help if people test it and report back - that way we can confidently merge it quicker. The more people who test it - the more use cases we can cover. Thanks!

[m-i-k-e]

@kball Any idea when this will be merged to master and released?