That was a bad idea. Now I have a character set issue :D

Depuis de longs mois déjà ...

I think I'll enjoy some help. My SQL input from a DB export looks like this, without extra encoding:

UPDATE `evo_items__item` SET `post_ID` = 4922, `post_content` = 'L''idée de la lampe...

When I feed this into phpmyadmin, using windows-1256 set for this file, I get a correct information displayed in phpmyadmin backend. But once the b2evolution cache is flushed, I get a bad front end display, for the records I just updated:

Depuis de longs mois déjà , sur Google et...

Other records which I didn't update are correctly displayed by the front end. For example:

Ce soir, au téléphone, le...

So, here, any advice would clearly be welcome.

I used headers and footers from my utf8 export, importing it again as utf8 data. That finally worked, then I cleaned the cache:

SET SQL_MODE="NO_AUTO_VALUE_ON_ZERO";
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;
UPDATE `evo_items__item` SET `post_content` = 'Par le passé, ...
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;

I think I have now almost jumped from 2.4.0rc2 to 3.3.3-stable.