Subject | Re: [firebird-support] UTF8 in firebird ? |
---|---|
Author | Michael Ludwig |
Post date | 2012-01-06T15:12:56Z |
Mark Rotteveel schrieb am 06.01.2012 um 15:49 (+0100):
against all standards.
method), version "WI-V2.5.0.26074 Firebird 2.5":
SQL> create table tc1 (a int, b varchar(10) character set ISO8859_1);
SQL> create table tc2 (a int, b varchar(10) character set ISO8859_15);
Statement failed, SQLSTATE = HY004
Dynamic SQL Error
-SQL error code = -204
-Data type unknown
-CHARACTER SET ISO8859_15 is not defined
Mon diœ, une errœr! Ah, c'est dommage! :)
--
Michael Ludwig
> On Fri, 6 Jan 2012 15:11:26 +0100, Michael Ludwig <milu71@...> wrote:Hehe, so many people blaming Microsoft, but they do get stuff right,
> > No, it's not; Œ and œ are missing from ISO-8859-1 (Latin1). Guess
> > the French delegation to the ISO botched up badly on that one … :)
> > They were more alert later when ISO-8859-15 (Latin9) was devised,
> > which includes not only the sigil of an ill-conceived currency (€)
> > but also the Œ and œ. So that's what you should be using, I think,
> > for your selection of Western European countries.
>
> You are right, missed that one :) They are included in the Microsoft
> 'version' of ISO-8859-1: Windows-1252. Funny thing is that ISO-8859-15
> contains all characters in Windows-1252, but some of them are at
> different byte encodings. Characterset are annoying :)
against all standards.
> BTW: I can't remember: does Firebird actually include ISO-8859-15Let's give it a try on server version Firebird/x86-64/Windows NT (access
> support?
method), version "WI-V2.5.0.26074 Firebird 2.5":
SQL> create table tc1 (a int, b varchar(10) character set ISO8859_1);
SQL> create table tc2 (a int, b varchar(10) character set ISO8859_15);
Statement failed, SQLSTATE = HY004
Dynamic SQL Error
-SQL error code = -204
-Data type unknown
-CHARACTER SET ISO8859_15 is not defined
Mon diœ, une errœr! Ah, c'est dommage! :)
--
Michael Ludwig