Hi everyone. I use ghost to email thousands of members. One of them who uses Outlook (native client on windows) sees “’” wherever a simple apostrophe should be (for example “it’s” instead to “it’s”.
Has anyone else experienced the same problem? Is it something to do with how Ghost renders HTML or something beyond my control?
Are you writing posts in Ghost? or perhaps pasting from another editor?
I wrote these posts in Ghost. I may have copy-pasted from within the article while editing but nothing external.
Also the “&apos” appeared even in text that was placed within markup/quote sections.
Not sure in that case, haven’t heard anyone else report this so far!
It looks like it only happens in Outlook. Happened on multiple posts to multiple users, and to all apostrophes, so not a matter of copy-pasting from a different source.
The newsletter email function is subbing in &apos when rendering HTML. Outlook choking on &apos is a known issue and nothing specifically to do with Ghost except the rest of the world codes around it. In fact in the js code, there are even commented references to this problem.
You can work out a partial solution now by always using markup text for paragraphs where you want to use an apostrophe, and subbing out either &-#-x2019-; or &-rsquo-; (remove the dashes) for each instance of that character. The solution obviously is for Ghost’s newsletter converter not to use &apos at all, and use one of these instead. I have been hunting through the js but haven’t found the location where this is done yet.
Thank you!
It doesn’t happen when I use MailChimp or Substack, so clearly they are working around it and Ghost should too. I hope it gets patched up soon. It’s a minor issue but it makes the email unreadable to thousands of my readers.
@John FYI
I have the same issue with Ghost newsletter and Outlook recipients. Have you found a handy solution to this? I might have to go to Mailchimp.
@flyride suggested a solution above, but it does not seem practical (I can’t go through my writing and convert ever ’ into special code in markdown.
I am also contemplating switching back to Mailchimp. Which is sad because I love ghost and want to be able to use! But not being able to send legible emails is a big problem, especially when the cause is a known issue that all other platforms already work around.