Paul Vinkenoog schrieb am 06.01.2011 um 16:27 (+0100):

> Markus wrote:

> Like isql with connection charset NONE, IBExpert also shows you the
> two composing bytes. I suppose that you can set the connection
> character set to ISO8859_1. Maybe IBExpert even supports UTF8 (I mean
> *really* supports it, unlike isql, afaik).

Thanks Paul, very helpful posting!

With isql (or other terminal stuff), you have to take into account the
terminal itself, of course. It does work in cmd.exe, at least for simple
cases like Reißwolf:

\,,,/
(o o)
------oOOo-(_)-oOOo------
:: chcp 65001
Aktive Codepage: 65001.

:: Firebird_2_5\bin\isql.exe eins25 -u milu -p bla -ch utf8
Database: eins25, User: milu
SQL> input T:\MiLu\Dev\SQL\Firebird\charset-names.utf8.sql;

S
================================================
Reißbrett
Reißbrett

SQL> quit;

:: chcp 1252
Aktive Codepage: 1252.

:: Firebird_2_5\bin\isql.exe eins25 -u milu -p bla -ch iso8859_1
Database: eins25, User: milu
SQL> input T:\MiLu\Dev\SQL\Firebird\charset-names.latin1.sql;

S
============
Reißbrett
Reißbrett
-------------------------

And while we're at it, the file encoding also matters, of course. The
INPUT command doesn't automagically guess the file encoding. It assumes
the file encoding is what is specified in the connection encoding, which
you do before opening the connection either by saying -charset (-ch) or
SET NAMES encoding_du_jour.

> > [IBExpert] sort of shows German Umlauts but Äpfel becomes Ä,pfel and
> > chinese/asian characters show up just plain wrong there.

IBExpert seems to be Made in Germany (TM), so it should properly ingest
Äpfel. (But I've never used the tool, so I can't really be sure.)

--
Michael Ludwig