Bug 104600

maybe an groff problem or wrong usage of the german umlauts
within the manual page (directly coded in iso-8859-1 instead
of using `Named Characters' like \[:a],\ [:o], \[:u], \[ss])

OK, no manual page. Btw: It seems to work in Japanese.
Please report _more_ details.

Can you *please* describe in more detail how to reproduce the problem?

Sorry, at the moment I'm out of time to investigate the problem more detailed.  
Additionally, I've booted 9.3 at the moment. However, I didn't want you to go 
begging ;-)  
  
Just some notes - perhaps they already help you.  
  
To reproduce the problem, I just have to open phpMyAdmin (language: german) in  
a browser and log in as any MySQL user. There are already some broken umlauts  
at the welcome page of phpMyAdmin.  
  
I just looked into 9.3's phpMyAdmin (which has the same problem). The welcome  
page contains  
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />  
but the umlauts are iso-8859-1(5)-encoded.  
  
I don't know if it's related to the problem, but I always install new SUSE  
releases as update, so there may be some not-updated config files or something  
like that. I also prefer iso-8859-15 as system-wide charset - but the problem  
also appeared when I (accidently ;-) used utf-8 shortly after installation of  
10.0 beta1.  
  
(BTW: I remove the "sample" umlauts from subject until bugzilla can correctly  
encode the subject in mails. Unencoded special chars in the mail header count  
too high in spamfilters.)  

What is the output of "w3m -dump_head" on the welcome page
of phpMyAdmin on your system?

Christian Boltz> (BTW: I remove the "sample" umlauts from subject
Christian Boltz> until bugzilla can correctly encode the subject in
Christian Boltz> mails. Unencoded special chars in the mail header
Christian Boltz> count too high in spamfilters.)

The bugzilla guys are working on a fix for that. See bug #78338.

I asked for the output of "w3m -dump_head" because I guess it is
a configuration problem of Apache.

The welcome page in German works just fine for me on SuSE Linux 10.0 Beta2.
I use UTF-8 as the system wide encoding, the page has

   <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

in the source and everything looks OK.

I finally had the time to investigate the problem. 
 
> What is the output of "w3m -dump_head" on the welcome  
> page of phpMyAdmin on your system? 
 
beta1@cboltz:~> w3m -dump_head  
'http://localhost/phpMyAdmin/main.php?lang=de-utf-8&server=1&collation_connection=utf8_general_ci' 
Username for phpMyAdmin auf localhost: fontlinge 
Password: 
HTTP/1.1 200 OK 
Date: Sun, 21 Aug 2005 18:52:43 GMT 
Server: Apache/2.0.54 (Linux/SUSE) 
X-Powered-By: PHP/4.4.0 
Set-Cookie: pma_lang=de-utf-8; expires=Tue, 20 Sep 2005 18:52:44 GMT; 
path=/phpMyAdmin 
Set-Cookie: pma_charset=iso-8859-1; expires=Tue, 20 Sep 2005 18:52:44 GMT; 
path=/phpMyAdmin 
X-ob_mode: 1 
Expires: Sun, 21 Aug 2005 18:52:44 GMT 
Last-Modified: Sun, 21 Aug 2005 18:52:44 GMT 
Cache-Control: no-store, no-cache, must-revalidate, pre-check=0, post-check=0, 
max-age=0 
Pragma: no-cache 
Content-Encoding: gzip 
Vary: Accept-Encoding 
Connection: close 
Content-Type: text/html; charset=utf-8 
 
 
In between, I could track down the problem to config.inc.php. Here's a diff to 
the original config file: 
 
--- config.default.php  2005-03-19 22:46:25.000000000 +0100 
+++ config.inc.php      2005-08-21 21:03:56.000000000 +0200 
[authentification changes skipped] 
@@ -395,1 +395,1 @@ 
-$cfg['DefaultLang'] = 'en-iso-8859-1'; 
+$cfg['DefaultLang'] = 'german'; 
@@ -399,0 +401 @@ 
+$cfg['Lang']     = 'de-iso-8859-1'; 
 
After removing the last one ($cfg['Lang']) it works again and phpMyAdmin sends 
out utf-8 encoded umlauts which match the charset header. That fixes/works 
around the mentioned problem. 
 
Why did I say "works around"? According to the comments in config.default.php 
and libraries/select_lang.lib.php, phpMyAdmin officially supports 
de-iso-8859-1  - so it should also work without charset problems with this 
setting ;-) 
 
Sending out the umlauts in the requested encoding (iso-8859-1) works 
correctly, but the headers contain the wrong encoding (utf-8) and do not honor 
the configuration setting. This results in "broken" umlauts in the browser. 
 
Since this problem does not appear in default configuration, it's your choice 
to reduce the severity of this bug, to forward it to the phpMyAdmin developers 
or to close it completely. 

Ok I make bug entry in phpMyAdmin bugzilla
https://sourceforge.net/tracker/index.php?func=detail&aid=1266626&group_id=23067&atid=377408

Michal Čihař fixed for us ;) fix will be in
http://cvs.sourceforge.net/viewcvs.py/phpmyadmin/phpMyAdmin/libraries/database_interface.lib.php?r1=2.19&r2=2.20

fixed and submited to STABLE

Wow - that was really fast! 
 
I just tested it (with 9.3's phpMyAdmin) - it works perfectly :-) 
 
Thanks! 
 

(In reply to comment #6)
> Christian Boltz> (BTW: I remove the "sample" umlauts from subject
> Christian Boltz> until bugzilla can correctly encode the subject in
> Christian Boltz> mails. Unencoded special chars in the mail header
> Christian Boltz> count too high in spamfilters.)
> 
> The bugzilla guys are working on a fix for that. See bug #78338.

Actually, it's bug 78557.