Subject | Re: Importing text into a unicode field |
---|---|
Author | bruce.eglington |
Post date | 2009-05-12T17:12:18Z |
Dimitry
I can't do what you suggest as I don't know, ahead of time, what language each string belongs to. I have a source database table with more than 30000 records and would have to manually check each to see what language the string is associated with - just not feasible.
All I do know, from checking records where problems occur, is that the issue is with characters typical of German,etc.
Bruce
I can't do what you suggest as I don't know, ahead of time, what language each string belongs to. I have a source database table with more than 30000 records and would have to manually check each to see what language the string is associated with - just not feasible.
All I do know, from checking records where problems occur, is that the issue is with characters typical of German,etc.
Bruce
--- In firebird-support@yahoogroups.com, Dimitry Sibiryakov <sd@...> wrote:
>
> > I am not sure whether the problems are something I have created in the database but am more inclined to think that the issue stems from the pumping software not being able to convert and represent characters appropriately for unicode use since I never had this problem when lilimiting text to ASCII characters with codes below 128.
>
> I doubt that this is problem in pumping software as itself, rather
> than the way you use it.
> If you created database with UTF-8 charset and want to pump data in
> different languages, you should do it step-by-step.
> At first, set up connection using German character set and pump
> German texts. Then set up connection using Finnish character set and
> pump Finnish text. Continue it until all texts are inside.
> Don't ever try to use character set NONE or UTF-8 directly because,
> indeed, pumping software have no idea how to convert national character
> sets into them.
>
> SY, SD.
>