Subject | Re: Unicode characters are dropped out firebird 1.5.1 and .net provider 1.6.2 isql input |
---|---|
Author | marijoaou |
Post date | 2004-09-30T13:59:33Z |
Hello,
The I have saved the files in ANSI format in notepad.
If I try for example unicode or UTF-8 format isql -i command throws
EOF expected etc notice.
What format are others using in windows ? and I have learned that
script files ending with CTRL+F gets rid of those EOF messages at
least for ansi notepad files.
BR,
MariJo
--- In firebird-support@yahoogroups.com, "Ivan Prenosil"
<Ivan.Prenosil@s...> wrote:
The I have saved the files in ANSI format in notepad.
If I try for example unicode or UTF-8 format isql -i command throws
EOF expected etc notice.
What format are others using in windows ? and I have learned that
script files ending with CTRL+F gets rid of those EOF messages at
least for ansi notepad files.
BR,
MariJo
--- In firebird-support@yahoogroups.com, "Ivan Prenosil"
<Ivan.Prenosil@s...> wrote:
> > The problem is that when I insert data (strings) with isql scriptand I have the setting SET NAMES UNICODE_FSS before
> the connection phrase. (I have written the script in windowsnotepad)
>firebird 1.5.1 and .net provider 1.6.2 isql input
> How are you saving the script from the notepad. As UTF-8 ?
>
> Ivan
>
>
>
> ----- Original Message -----
> From: "Mari Johanna" <marijoaou@y...>
> To: <firebird-support@yahoogroups.com>
> Sent: Thursday, September 30, 2004 11:53 AM
> Subject: [firebird-support] Unicode characters are dropped out
>after I changed from 1.0.3 database version to database
>
> Hello,
>
> I have a problem with unicode characters äåö etc that appeared
> version 1.5.1 and newer .net provider.The problem is that when Iinsert data (strings) with isql script and I have the
> setting SET NAMES UNICODE_FSS before the connection phrase. (I havewritten the script in windows notepad)
>program shows the problematic characters allright. But
> The data seems to be OK when I look at it with IBSQL and that
> when I query them with .net provider for firebird then all theproblematic characters are left out from the .net
> dataset.unicode then this provider can get the datas without
>
> But when I use this same .net provider to insert this data as
> missing any ä:s and ö:s. And that is why it seems that there couldbe something this isql script is putting is not OK.
>one. It is odd that everything was working just great
> Would be really really grateful if anyone could help me with this
> before I upgraded to the newer versions of database and provider.
>
> BR,
> MariJo