> I'm working to fix it - you may have noticed drafts of new INTL
> interface floating around, but I would not expect to get it to work
> very soon.

Yup! I have noticed that, but I did not follow the discussion later.

> But your reasononing is sound, especially in light of fact that
> metadata BLOBs are marked as UNICODE_FSS, but store data in client
> character set.

Ok, then I keep using the client encoding. Would it be correct to write in
the JayBird release notes that people should not rely on server converting
BLOB contents to the client encoding and they better use either
getBinaryStream() or getBytes() instead of getCharacterStream() or
getString() for text blobs?

Roman