Hi Daniel,

Your posting deserves a longer answer, but for a quick
try I want to point out one thing:

In FB1.5.1 the handling of the NONE character set
has been changed, so that these transliteration errors
between NONE and defined charsets no longer occur.

Please test FB1.5.1 RC3 whether it will resolve the
concrete problem.

Regards,
Peter Jacobi