[Mono-bugs] [Bug 73072][Nor] Changed - Wrong encoding in output from Postrgres (MySQL reported to fail too!) in Datagrid.

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Thu, 21 Apr 2005 07:19:46 -0400 (EDT)

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by gonzalo@ximian.com.


--- shadow/73072	2005-02-27 05:37:20.000000000 -0500
+++ shadow/73072.tmp.19156	2005-04-21 07:19:46.000000000 -0400
@@ -1,13 +1,13 @@
 Bug#: 73072
 Product: Mono: Tools
 Version: 1.0
 OS: unknown
 OS Details: Linux FC 3
-Status: REOPENED   
+Status: RESOLVED   
+Resolution: NOTABUG
 Severity: Unknown
 Priority: Normal
 Component: XSP
 AssignedTo: gonzalo@ximian.com                            
 ReportedBy: pommes@teleos-web.de               
 QAContact: mono-bugs@ximian.com
@@ -78,6 +78,23 @@
 Hope it helps somehow.
 If you have a problem with the databasetable, I can dump the whole
 database with all users etc (it's not big), but I will not transmit it
 via a public channel. Drop a message if you are in need of the whole
 database, I will upload it to my ftp or something...
+------- Additional Comments From gonzalo@ximian.com  2005-04-21 07:19 -------
+There are several problems with the test. First of all, if you're
+reading a file that is in a known encoding, you should use that
+encoding to read it. Otherwise you'll get garbage (that's what i got).
+Second, some time ago, while developing support for postgres in
+libgda, i tested the SET client_encoding option against different
+encodings for the database backend (initdb -E encoding). Different
+combinations might or might not work, but if the backend is in UTF8,
+client_encoding = UNICODE will always give you what you expect.
+About the differences in the output from mod_mono and xsp, that might
+be due to apache/xsp setting a differnet charset for the output page,
+as you're mixing various encodings.