Hi Jim Beesley,

--- Long time ago, "Jim Beesley" wrote:
[Some suggestions for better mult CS support]

Are you still on the list? Have you got any responses, not seen here?

Firebird charset/collation issues seem to have no lobby.

Unfortunately I did my contribution to the unfortunate situation, when
I volunteered to address these issues and got developer status.
Shortly thereafter I realised, that I wouldn't have the time for
serious contributing, except maybe in the external DLLs.

I agree with most of your analysis. IMHO there are only three sane cases:

a) database uses only one character set (and possibly subsets like ASCII)

b) database uses different character sets, applications volunteers to
do all transcoding, FB automatic transcoding must be turned off some way

c) database uses different character sets, but all communication is
done using Unicode. This would be a fine option, if it works.

IMHO Carlos has explored c) in the newer versions of the .NET
provider. If you have access to a .NET programming environment, you
may want to test this.

Regards,
Peter Jacobi