On Tue, 14 Mar 2006 16:05:40 +0100, Thomas Bruederli <[EMAIL PROTECTED]> wrote:
>
> Hmmh, seems that the encoding behavior is different from GET to POST
> method. The 0.1beta has the following line in the .htaccess file:
> AddDefaultCharset UTF-8
> I thought that this would solve the encoding problem in general (at
> least on Apache servers)
It's been comented out in CVS. I just un commented it in my .htaccess
[EMAIL PROTECTED]:/var/www/html/roundcubemail$ cat .htaccess
# AddDefaultCharset UTF-8
php_flag display_errors Off
php_value upload_max_filesize 2m
<FilesMatch "(\.inc|\~)$|^_">
Order allow,deny
Deny from all
</FilesMatch>
Order deny,allow
Allow from all
[EMAIL PROTECTED]:/var/www/html/roundcubemail$ cvs diff .htaccess
Index: .htaccess
===================================================================
RCS file: /cvsroot/roundcubemail/roundcubemail/.htaccess,v
retrieving revision 1.4
diff -u -r1.4 .htaccess
--- .htaccess 3 Mar 2006 16:34:30 -0000 1.4
+++ .htaccess 14 Mar 2006 18:31:32 -0000
@@ -1,5 +1,5 @@
# AddDefaultCharset UTF-8
-php_flag display_errors On
+php_flag display_errors Off
php_value upload_max_filesize 2m
<FilesMatch "(\.inc|\~)$|^_">
> If a message specifies it's charset in the Content-Type header, RC will
> attempt to convert it to UT
By the way, when trying to reply to this message (like right now) with RC, the
message gets cut right here. Very odd.
--
---------------------------------------------------------
Lic. Martín Marqués | SELECT 'mmarques' ||
Centro de Telemática | '@' || 'unl.edu.ar';
Universidad Nacional | DBA, Programador,
del Litoral | Administrador
---------------------------------------------------------
