On Fri, 06 Jan 2012 00:42:25 +0400, Vander Clock Stephane
<svanderclock@...> wrote:

>> The longer term solution is for the Firebird project to look at its
>> data representation and find something that works better with UTF8.
>
> yes, at least some options in the database (or in the create statement)

to

> define the size in byte of 1 UTF8 char
>
> For exemple by default 1 utf8 char = 4 bytes (like it is now) and i can
> be able to
> customize it to be egual to 1 bytes.

Then it is no longer UTF-8. What should change is how Firebird handles and
stores variable length character encodings like UTF-8, because you are
right: some parts of Firebird treat it as if it is always 4 bytes, and it
really should not do that.

However redefining UTF-8 to fit your specific wishes is not the right way.

Mark