Subject Re: Java CharSet to Firebird CharSet
Author Fabiano
It is done, Mark.

BTW, is it correct to connect to Firebird using always the "UTF-8" charset, independent of the charset used by the O.S? I read somewhere that despite the charset the O.S is using, Java always use UTF-16, and it doesn´t matter if i connect with ISO-8859-1, UTF-8 or other, jaybird will always convert from UTF-16 (Java) to connection charset "before" sending something to the server.



--- In, Mark Rotteveel <mark@...> wrote:
> On 9-8-2012 19:48, Roman Rokytskyy wrote:
> > I do not know about current official names of character sets, but in
> > previous versions they were called differently. The windows-1252 was,
> > for example, Cp1252. These values are fully mapped.
> Looking at
> and
> it looks like Jaybird only maps the characterset names that were
> supported under Java 1.3 (which is not so weird as Jaybird 2.1 still
> supported JDK1.3).
> Characterset support in Java received a major overhaul in Java 1.4 where
> the standard IANA characterset names (
> ) were used, with the
> 'old' names as an alias:
> I was actually considering to switch to the use of the Charset classes
> of Java instead of using our own implementation somewhere in the future.
> Fabiano, could you create a ticket, I will then see if it is easy to
> include more aliases for now.
> Mark
> --
> Mark Rotteveel