In Firebird 2.0 or later, character set conversion method has changed, then "Windows-31J" extension were
cannot use in FB2.0 or later environment. (detail in quated mail as below)
This is a severe problem for japanese user. Typical develloper use delphi with FB1.0 or 1.5 on Windows server and
use "Windows-31J" extension, the same code don't work on FB 2.0 or later. Then many japanese user cannot migrate
from FB1.x to 2.x.
Please add character set 'cp932' to FB 2.1.
# I will help to test it.
Fortunately, iCU routine has 'Windows-31j' then use it in order to support 'cp932'.
KIMURA, Meiji(FAMILY, Given)
//--> Quated mail as below
[Firebird-devel] Firebird 2.x cannot handle with some japanesecharacters in SJIS_0208 environment.
KIMURA, Meiji wrote:
> In Firebird 1.x, InterBase 6.x or later, 'SJIS_0208' *IS* Shift_JIS in IANA.
> But in the condition that the same character set 'SJIS_0208' between client and server,
> there is no conversion of character set. As a result, 'Windows-31J' extension can use
> with no error.
In previous version there is a direct (special) converter from SJIS to
something else and this converter was removed, doing the conversion
> But in Firebird 2.0 environment, If the same character set 'SJIS_0208' used between
> client and server, Unicode is used as a pivot character set. as a result,
> we cannot use "Windows-31J" extension.
I've already heard this, maybe from Daiju.
> It seems that the same problem occurs in MySQL 4.1.
> In the case of MySQL, there is no conversion version 4.0 or before, but
> version 4.1 or later, Unicode is used as a pivot character set, then
> the same problem occurs.
> MySQL support character set 'cp932' as a measure for this problem.
> cp932 means 'Windows Codepage 932'. cp932 *IS* Windows-31J in IANA.
> I supporse if Firebird 2.0 will support character set 'cp932', we can avoid this problem.
> # When use iCU routine, use 'windows-31j' instead of 'shift-jis'.
This seems to be the way to go.