[TYPO3-core] RFC: #3391 HTML-Source in Error-Pages not valid (FE)

[Ernesto Baschny [cron IT]]

Martin Kutschker schrieb am 28.06.2006 14:16:

>> The TYPO3 error page is not valid anything. This error page is displayed
>> to the FE-user for example if there is no template, or she is trying to
>> access a page ID that does not exist or if the path to RealURL is not
>> valid (the ominous "Segment XXX was not a keyword for a postVarSet as
>> expected!"), etc. So its pretty common to see this output.
>>
>> Solution:
>>
>> Attached patch changes that error page to be valid XHTML 1.1. It also
>> moves from the table layout to some CSS-styling (this is the also what
>> Apache does in its error messages).
> 
> Fine. But is it guaranteed the messages are in UTF-8?

True, good point. I am pretty confident that we have ASCII only messages
(english), because when such an error is shown we surely don't even have
a TYPO3-setup where charset settings are available. I'll dig into that.

Cheers,
Ernesto