-
From: Mercea Paul [mailto:paul.mer...@almexa.ro]
Sent: 10 January 2010 12:15 PM
To: lo...@nucleo.co.za; 'For users and developers of the Firebird .NET
providers'
Subject: RE: [Firebird-net-provider] Character set problem between with
Firebird & .NET provider
Hi Louis
>
Hi Louis
> -Original Message-
> From: Louis van Alphen [mailto:lo...@nucleo.co.za]
> Sent: Friday, January 08, 2010 14:59
> To: firebird-net-provider@lists.sourceforge.net
> Subject: Re: [Firebird-net-provider] Character set problem between with
> Firebird & .NET
Hi,
At January-08-10, 3:56 AM, André Knappstein, Controlling wrote:
> I don't know.
> If I remember correctly I have read that unicode takes an extra byte
> per character and I did not want to hit any technical limit (max.
> lenghth of index key and such...)
UTF-8 can take between 1 and 4 bytes
is van Alphen [mailto:lo...@nucleo.co.za]
Sent: 08 January 2010 12:00 PM
To: 'firebird-net-provider@lists.sourceforge.net'
Subject: RE: [Firebird-net-provider] Character set problem between with
Firebird & .NET provider
I tried WIN1252 but it still does not work.
I did the following ste
error when accessing certain data
-Original Message-
From: André Knappstein, Controlling [mailto:knappst...@beta-eigenheim.de]
Sent: 07 January 2010 04:21 PM
To: Louis van Alphen
Subject: Re: [Firebird-net-provider] Character set problem between with
Firebird & .NET provider
I would se
I don't know.
If I remember correctly I have read that unicode takes an extra byte
per character and I did not want to hit any technical limit (max.
lenghth of index key and such...)
And I dimly remember that there were such limits for FB 1.5, which
have been extended along with 2.x.
Our database
On Thu, Jan 7, 2010 at 16:54, André Knappstein, Controlling
wrote:
> We changed everything to Win1252 instead, which supports spanish and
> french characters as well as German Umlauts and ß
Why not unicode?
--
Jiri {x2} Cincura (CTO x2develop.com)
http://blog.cincura.net/ | http://www.ID3rename
I would second what Jiri wrote.
We have been using 8859_1 widely. This works okay with ODBC.
Using .net, some things did not work correctly. Or rather they worked
correctly but not as we expected :)
ISO8859_1 does - for example - not really specify a solution for
displaying the Euro symbol (€).
W
On Thu, Jan 7, 2010 at 13:45, Louis van Alphen wrote:
> What else do I need to do?
Are you sure, that your application works in ISO8859_1. For .NET I
don't think so.
--
Jiri {x2} Cincura (CTO x2develop.com)
http://blog.cincura.net/ | http://www.ID3renamer.com
--
Hi, I would appreciate it if someone could help.
I am I South Africa and is developing an application for use in South
Africa, France and Italy. Therefore the application and database has to
support the French and Italian special characters.
I created the database using IBExpert with a defa
10 matches
Mail list logo
