Bug #17279
Tidy changes Meta-Tag charset
| Status: | Needs Feedback | Start date: | 2007-05-05 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| TYPO3 Version: | 4.1 | Complexity: | ||
| PHP Version: | 4.3 | |||
| Votes: | 0 |
Description
Tidy changes the correct Meta-Tag from
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
to
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />
Vlidators like http://validator.w3.org find foult in the difference between sended header and the metatag charset.
So TYPO3 should set the correct tidy option by config.metaCharset.
$TYPO3_CONF_VARS["FE"]["tidy_path"] = 'tidy ###CHARSET### -i -f /var/log/apache/tidy-log --quiet true -wrap 0 --tidy-mark no --hide-comments no --indent no';
(issue imported from #M5567)
History
Updated by Martin Kutschker about 6 years ago
The patch has a problem: there are many character sets more that TYPO3 supports, so you may not only support to UTF-8 and latin1 (iso-8859-1).
Furthermore there seems to a be a problem with tidy. I have created a simple HTML file with <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />. I have run tidy with -latin1 and yet it has changed the line to <meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />.
Updated by Alexander Opitz about 1 month ago
- Status changed from New to Needs Feedback
- Target version deleted (
0)
The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?