> One questions remains, though. > If ISO8859_1 is not suitable for that purpose, why have I never been > noticing this before? I mean, why do the other drivers/providers > translate those bytes correctly to a Euro sign?
ISO 8859-1 and WIN-1252 are almost exactly the same, except that where ISO 8859-1 has some control codes, WIN-1252 has a few extra letters (like U+2020 †, etc) -- one of those extra letters is the Euro sign. Many applications, however (especially Windows applications) treat ISO 8859-1 as being synonymous with WIN-1252, so that's probably why it worked in those other cases. .NET is not so lenient, however, and something marked as ISO 8859-1 to .NET will not be able to contain a Euro symbol. Dean. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
