Subject | Re: Firebird client connection charset, server charsets and encoding |
---|---|
Author | skoczian |
Post date | 2008-12-02T12:05:20Z |
--- In firebird-support@yahoogroups.com, Milan Babuskov <milanb@...>
wrote:
Gentoo Linux the umlaut characters are quite correct with this
connection charset. Entering them in a query looks a little
confusing, but works also.
ISQL uses the charset of the terminal, right?
names utf8" there also for databases with default charset ISO8859_1?
Greetings
Herta
wrote:
>connection
> skoczian wrote:
> > But: using ISO8859_1 as database default charset and as
> > charset gives me wrong umlaut characters in ISQL and emptyfields in
> > FlameRobin, if the field contains a non ASCII character.Sorry, I wrote this from memory. Using FlameRobin 0.8.6.1652 on
>
> This looks like a bug. Which version of FlameRobin?
> Please follow up on flamerobin-devel for this...
>
Gentoo Linux the umlaut characters are quite correct with this
connection charset. Entering them in a query looks a little
confusing, but works also.
ISQL uses the charset of the terminal, right?
> > Using ISO8859_1 as database default charset and UTF8 asconnection
> > charset gives me a FlameRobin warning and I don't know if thisis a
> > dangerous practice or notremoved in
>
> It is actually the best way to use it. That warning should be
> next FR release.Ok, thank you for that advice. How about ISQL, should I use "set
>
names utf8" there also for databases with default charset ISO8859_1?
Greetings
Herta