> > 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.
>

i thing you have a misunderstanding, because utf8 if "FROM" 1 to 6 bytes
(or even more in the theory) !
so why 3 (or 4) bytes will be utf8 and not 1 or 2 ??

> 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.
>

their is no other better way that let the user setup himself the length
of the varchar
column in 1 bytes instead of x4 bytes. for my column of 250 characteres
if i know i will target russian or chinesse
i will setup varchar(750) and if i know i will target french and spanish
i will
setup varchar(300). and if i want to be ABSOLUTELY
sure i can enter 250 char in any case i will setup if as varchar 1500
(klingon extension?) !

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

[Non-text portions of this message have been removed]