After extensive discussion on the FB Architecture list, it was
determined that the current unicode implementation in Firebird is not a
standard unicode implementation. As near as anyone can tell, it was
implemented when the standard (possibly UTF-8) was in a very early draft
stage. Since it predates the standard, it does not necessarily
correctly implement it.

The international branch supports UTF-16 though.

On Wed, 2005-03-09 at 07:05, Daniel Albuschat wrote:
>
>
> On Wed, 09 Mar 2005 12:13:36 -0000, icwicks <icwicks@...> wrote:
> >
> > Hello.
> > I understand a product I use called GoldMine is about to go through
> > a change and will be hosted on a Firebird database.
> > I have a client who wants to use GoldMine in Japan.
> > 2 questions;
> >
> > 1. Will firebird support the Japanese character sets?
>
> Firebird supports UNICODE, which would be the ideal solution.
> But whether you can use this will depend on the client application,
> GoldMine in your case.
>
> There's a list of supported character sets at
> http://www.destructor.de/firebird/charsets.htm
> and
> http://firebird.sourceforge.net/index.php?op=doc&id=fb_1_5_charsets&nosb=1
>
> >From what I can see, SJIS_0208 and EUCJ_0208 are supported...
> iso-2022-jp seems to be missing, though.
>
> > 2. What version of Firebird is now being used?
>
> The latest stable version is Firebird 1.5, you can download it from
>
> http://www.firebirdsql.org/index.php?op=files&id=engine
> or
> http://sf.net/projects/firebird
>
> I'd still contact the GoldMine support and ask them the same questions...
> Maybe the application itself can't handle Japanese text or supports
> only a certain firebird version.
>
> --
> eat(this); // delicious suicide
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>