#49363 [Ver->Csd]: [DE] wrong encoding

ID: 49363 Updated by: wiesemann@php.net Reported By: admin at mysqldumper dot de -Status: Verified +Status: Closed Bug Type: Translation problem Operating System: Win XP PHP Version: Irrelevant Assigned To: wiesemann New Comment: This bug has been fixed in the documentation's XML sources. Since the online and downloadable versions of the documentation need some time to get updated, we would like to ask you to be a bit patient. Thank you for the report, and for helping us make our documentation better. Previous Comments: ------------------------------------------------------------------------ [2009-08-28 22:34:18] svn@php.net Automatic comment from SVN on behalf of wiesemann Revision: http://svn.php.net/viewvc/?view=revision&revision=287870 Log: - Bug #49363: [DE] wrong encoding (wrong value in "encoding" attribute) - typo fixes ------------------------------------------------------------------------ [2009-08-25 16:49:22] admin at mysqldumper dot de Description: ------------ The manual states: "Note: This is the preferred way to change the charset. Using mysql_query() to execute SET NAMES .. is not recommended. " I am missing any technical explanation here why this is recommended. Sending "SET NAMES 'charset'" via mysql_query() always worked fine on many different servers for me. So I want to know more detailed what is the disadvantage and what is the advantage using mysql-set-charset(). Funnily the German translation page of mysql_set_charset has some incorrectly encoded German umlauts on the page. e.x.: "Setzt den Standardzeichensatz für die angegebene Verbindung. " instead of "Setzt den Standardzeichensatz für die angegebene Verbindung." Reproduce code: --------------- --- From manual page: function.mysql-set-charset --- ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=49363&edit=1