Hello,
I recently received an e-mail containing German umlauts (ä,ö,ü), which produced the following error when loading the message:
DB Error in /var/www/webmail/program/include/rcube_db.inc (283): DB Error: unknown error Query:
<snip> [nativecode=ERROR: invalid byte sequence for encoding "UNICODE": 0xfc7220]
Apparently, the error is connected to the message's original encoding, which is:
Content-Type: text/plain; charset="ISO-8859-1"
I'm running Roundcube on Apache 2.0 with PostgreSQL 7.4 as a backend. I have not tested this error with the 8.0/8.1 releases yet.
Any ideas?
Unfortunately I'm not very familiar with postgres. Can any postgres experienced users give us some advice on this? Should text be converted to UTF-8 before inserting?
Regards, Thomas
2005/12/11, Christian Kastner christian.kastner@gmail.com:
Hello,
I recently received an e-mail containing German umlauts (ä,ö,ü), which produced the following error when loading the message:
DB Error in /var/www/webmail/program/include/rcube_db.inc (283): DB Error: unknown error Query:
<snip> [nativecode=ERROR: invalid byte sequence for encoding "UNICODE": 0xfc7220]
Apparently, the error is connected to the message's original encoding, which is:
Content-Type: text/plain; charset="ISO-8859-1"
I'm running Roundcube on Apache 2.0 with PostgreSQL 7.4 as a backend. I have not tested this error with the 8.0/8.1 releases yet.
Any ideas?
On Thu, 15 Dec 2005, Thomas Bruederli wrote:
Unfortunately I'm not very familiar with postgres. Can any postgres experienced users give us some advice on this? Should text be converted to UTF-8 before inserting?
OK, let's see what's up. The bad thing is that I don't have a RC in production, but.... (see next message).
2005/12/11, Christian Kastner christian.kastner@gmail.com:
I recently received an e-mail containing German umlauts (ä,ö,ü), which produced the following error when loading the message:
DB Error in /var/www/webmail/program/include/rcube_db.inc (283): DB Error: unknown error Query:
<snip> [nativecode=ERROR: invalid byte sequence for encoding "UNICODE": 0xfc7220]
OK, aparently it looks like the client encoding is not iso-8859-1, but rather UTF-8 (could you pass the client_encoding value from postgresql.conf).
Apparently, the error is connected to the message's original encoding, which is:
Content-Type: text/plain; charset="ISO-8859-1"
If I'm correct, there should be some kind of translation of diferent encodings.
-- 18:02:25 up 4 days, 9:57, 5 users, load average: 1.59, 1.57, 1.62
Lic. Martín Marqués | SELECT 'mmarques' || Centro de Telemática | '@' || 'unl.edu.ar'; Universidad Nacional | DBA, Programador, del Litoral | Administrador
-
Christian Kastner -
Martin Marques -
Thomas Bruederli