After doing a content import of a few thousand posts, we found that the import script would choke on items that have a double end curly quote or ”. It would then not include any content of the post after and including the double end curly quote, but move on to the next WordPress entry. It happens on the end quote, but not the start quote, i.e. “.
Comments
Comment #1
yrocq commentedThank you for your feedback. Could you tell me if the blog is encoded in UTF-8 or ISO-8859-1 ?
Comment #2
yrocq commentedI can't reproduce the bug. I need the xml file to investigate this problem.
Comment #3
lavamind commentedBranch 5.x is no longer supported.