Every post older than this one is taken from teblog – my blog that ran on Typepad from 2005 to 2015. The explanation for the move is in the previous post.
While the transfer was reasonably straightforward (it was only 530 posts), WordPress didn’t like certain characters. In fact, it wouldn’t even allow me to edit any posts with those characters in. (They showed up in the public posts as black diamonds with question marks in.) The characters I’ve found thus far are the pound sign, the ellipsis (three dots), angled brackets, forward slashes and angled double quotes. If you need to do this, use these abbreviations – pound, hellip, lt, gt, frasl and quot respectively. Precede each one with an ampersand (&) and finish with a semi-colon (;).
[Later: It’s not happy with accents either. I found it most reliable to use codes like #232 and #233 for grave and accute accents on an e. You still have to start and end with an ampersand and a semi-colon. Here’s a decent collection of character codes. Mouse over each character to see all the possible codes for it. I found the last one on each list worked fine in WordPress. ] Here’s my set of dodgy characters (there were 286 in the blog altogether:
[ Just discovered that WordPress has trouble with the em dash as well. I used #8195 with the ampersand and semi-colon as before. ]
Since Typepad exports a text file, it’s a relatively simple (although tedious) task to go through searching and replacing the offending characters. Which is what I’m doing right now.
Once the offending posts and comments are deleted from WordPress, it should be a simple matter to re-import the cleaned up Typepad file. WordPress ignores duplicates of what it already has. Tip: Empty the ‘Trash’ of your faulty posts and comments before you start otherwise WordPress will skip them.
[ Later: Darn it – I didn’t change cross-links to other posts – they still go to Typepad. I should be able to fix them inside the WordPress posts. I pointed TextPad’s ‘search in files’ at the exported file to list them. I copied and pasted the results list to a text file for a permanent record.]
[ Later still: It was a bit tedious – yet only 57 posts and comments had cross-links in them. You have to find the linked-to post to get its URL then paste this in to replace the cross-link. If you have loads, you might prefer not to do a manual conversion and use an automated service like TP2WP. This currently costs $49. It’s probably worth mentioning that its security certificate expired on 7 Dec 2015 and you may be denied access to the service. It does, however, come highly recommended, so I assume it does all this donkey work for you. I’ve asked one of the co-authors about both things. Will report back here. ]