Non-ascii characters caused problems with SVN function and were replaced
authorjangliss <jangliss@7612ce4b-ef26-0410-bec9-ea0150e637f0>
Sun, 25 May 2003 13:05:34 +0000 (13:05 +0000)
committerjangliss <jangliss@7612ce4b-ef26-0410-bec9-ea0150e637f0>
Sun, 25 May 2003 13:05:34 +0000 (13:05 +0000)
commita747d9712060960573e845094f747d88ef391a43
tree42d51da571b74f7c2447e5cc70ce4384ff9e2c65
parent969a0af6a44fbaea7d56f542f067277109546516
Non-ascii characters caused problems with SVN function and were replaced
with a ? by SourceForge.net in your original log message, which follows:

Certain characters in translations would mess up on the post, such as an
umlaut would appear as &amp;ouml; in html, but after being posted it appears as
? so matching would always fail, making it impossible for those with
chars like that to mod/delete servers. (Bug #742705)

git-svn-id: https://svn.code.sf.net/p/squirrelmail/code/trunk/squirrelmail@4937 7612ce4b-ef26-0410-bec9-ea0150e637f0
plugins/mail_fetch/options.php