There are other issues to be aware of with unicode ... these apply to
both migration and to operation. They are issues with Unicode itself,
not Firebird's implementation.

There are often several ways to represent the same character in Unicode,
and those ways should be treated identically. Accented characters are a
prime example. a`, `a, and à are all considered to be the same
character under unicode rules. A canonical representation should be
built by the application before storing or operating against the
database, or you may have unexpected results. In addition, you may have
to consider localized rules for some characters. In German, for
example, the digraph 'ss' and the character 'ß' are considered identical
for all purposes. 'Fussball' is absolutely equal to 'Fußball' for
german language database purposes.

On Fri, 2005-12-02 at 02:00 +0000, triathlon98bis wrote:
> For consistency (and to avoid transliteration errors) I need to
> convert a few databases from charset none to unicode_fss.
> I tried using some data pumping tools to do this (specifically ibpump
> and fbcopy) but both give me errors (ibpump has problems with circular
> dependencies in the data structure (even when told to disragard these
> constraints), fbcopy give an error message "XSDA:SetValue incompatible
> types".
>
> What can I do to fix this? Is there a possible manipulation on the
> tables? Another tool which can help me?
>
> Thanks for the help,
> Joachim