Martin,
It’s a case of that shouldn’t happen because I had that same issue when I first developed and migrated.
I’ve listed the issue at https://github.com/michael-cannon/typo3-importer/issues/2. However, I doubt that I will fix anytime soon because I don’t have capacity right now.
Others are welcome to step in and fix though. It’s open source.
This is really a great piece of code! http://www.tink.ch will use it to import about 10’000 articles. But we also have the exact encoding-problem. I will try to fix it, if not already done?
Thank you for offering to fix the encoding issue. I thought I had the work arounds in place, but seems to not be.
It might be that the encoding type of the source database might need to be set and ditto for the target database.
Thanks for the hints, I’ll try it. Unfortunatly the next two weeks I have a great deal to do. But after this two weeks, we will start importing and hence to fix the encoding issue.
