Character Encodings

This version addresses the problem of weird characters ending up in the Drupal database and was as a result of incorrect character encodings. For what it's worth the Wordpress MySql database is encoded as 'Latin1' and the Drupal MySql database is encoded as 'utf8' (unicode).

I conducted some tests and specifically tested against this particular sentence:-

“Mares eat oats–and does eat oats—and…little lambs eat ‘ivy’.”

Drupal Table Prefix

This version fixes a little problem where if the target database (Drupal) included a table prefix then the comments data was not transferred across. An error message was displayed, advising the user accordingly, clicking OK the conversion progressed.

This particular problem caused the effect of not being able to add a node, category, comment or user.

This has been rectified.

Character Encodings

I'm still working on this and hopefully by next release it should be resolved, touch wood.

An encoding problem has reared its ugly head and giving me no end of grief.
At the Wordpress end, type in (or more commonly paste in) this line of text:-

“Mares eat oats–and does eat oats—and…little lambs eat ‘ivy’.”

I'll point out that the double quotes starting and ending the line of text are not double quotes, they are in fact curly quotes. Try and find them on your keyboard. Chucked in for good measure are a few other non-standard type characters.