Last modified: 2013-10-23 18:16:59 UTC
The current DatabaseError ("Sorry! This site is experiencing technical difficulties.") and the google search form are served without a html header and without coding information. This breaks multibyte characters like german umlaute on that page, because the page is served in utf-8 from MediaWiki (default behaviour) but the IE is using another coding (when automatic selection is on). In my opinion should it possible to give a valid html page on a database error. You have not to use the database in that moment for valid html. Thanks.
Yes, encoding is a better word. Thanks.
Reporting seems to go through MWException::reportHTML()'s non-OutputPage path, which explicitly sends "Content-Type: text/xhtml; charset=utf-8". This should set the encoding just fine, and shouldn't require anything additional -- unless something else has started output already by mistake, such as PHP's error reporting. What are the exact circumstances of the error you're seeing? Can you reproduce it regularly for testing?
Is it really on trunk? I fixed that problem not too long ago, precisely by adding that header in r103339.
(In reply to comment #3) > Is it really on trunk? I fixed that problem not too long ago, precisely by > adding that header in r103339. The errors were under 1.18. But that fix looks good, making FIXED.
