> Please, specify "UTF-8" as alias to "UNICODE_FSS" value. If server
> cannot handle this, then jdbc driver could easily implement it.
> Probably not the bad idea to let server recognise it as well.

UTF-8 will be recognized by server either in 1.5 or 2.0.

> And Java standard uses Cp1251, Cp1252, etc... for windows encodings.
> Is it possible to let jdbc driver recognize it and convert to
> Firebird appropriate one.

Well... Server has some encodings that are not supported by Java, for
example "NONE" or "OCTETS". So, I will leave setEncoding() method as
is because set encoding is equal to setting isc_dpb_lc_ctype DPB
property. I will add new property charSet that will be set to Java
character set name.

Roman