View Single Post
Old 05-15-2012, 09:54 AM   #4
knc1
Helpdesk Junkie
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 6,998
Karma: 6314536
Join Date: Feb 2012
Device: Too many.
Quote:
Originally Posted by Alexander Turcic View Post
Definitely going to look into that today!
While fixing things - the login form is not international:
Quote:
Originally Posted by wed-dev
--
[07:51:51.159] A form was submitted in the windows-1252 encoding which cannot encode all Unicode characters, so user input may get corrupted. To avoid this problem, the page should be changed so that the form is submitted in the UTF-8 encoding either by changing the encoding of the page itself to UTF-8 or by specifying accept-charset=utf-8 on the form element. @ http://www.mobileread.com/forums/forumdisplay.php?f=150
That's "forumdisplay.php" if you can't read the entire name.
EDIT 1:
Same problem with "new reply" -
Quote:
Originally Posted by web-dev
--
[07:54:26.491] A form was submitted in the windows-1252 encoding which cannot encode all Unicode characters, so user input may get corrupted. To avoid this problem, the page should be changed so that the form is submitted in the UTF-8 encoding either by changing the encoding of the page itself to UTF-8 or by specifying accept-charset=utf-8 on the form element. @ http://www.mobileread.com/forums/new...eply&p=2081612
And this one is "newreply.php"
Edit 2:
Ah, but the "quick edit reply" does not use the windows-1252 character set - web-dev did not report the character set, so I assume the "quick edit reply" is using UTF-8.

Edit 3:
And then, if you choose the "go advanced" in the "quick edit reply" then you are back to windows-1252 character set.
Quote:
Originally Posted by web-dev
--
[08:02:20.348] A form was submitted in the windows-1252 encoding which cannot encode all Unicode characters, so user input may get corrupted. To avoid this problem, the page should be changed so that the form is submitted in the UTF-8 encoding either by changing the encoding of the page itself to UTF-8 or by specifying accept-charset=utf-8 on the form element. @ http://www.mobileread.com/forums/edi...postid=2081839
This one is "editpost.php"
These differences may be part of the stray characters problem(s).

Last edited by knc1; 05-15-2012 at 10:10 AM.
knc1 is offline   Reply With Quote