[TYPO3] Characters not in iso 8859-1

Fri May 25 16:23:32 CEST 2007

Hi Helge. You don't need to remove the XML prolog. You just have to make it 
switch position with the doctype, as some browsers (IE6 ald older) doesn't 
like the xml prolog as first element.

This should fix the problem.
-- cut --
// --- SET DOCTYPE TO XHTML_TRANS ----------------------
config.doctype = xhtml_trans
config.xhtml_cleaning = all

[browser = msie] && [version=  <7]
config.doctypeSwitch = 1
[GLOBAL]
-- cut --

If the browser is MSIE and the version is lower that version 7, then the 
doctype and prolog position is switched.

To test it, you can try adding these 2 lines to your TS setup.

-- cut --
page.headerData.1 = TEXT
page.headerData.1.value = <script>alert(document.compatMode);</script>
-- cut --

if your page is setup correctly, then you should get an alert with 
"CSS1Compat", otherwise it will show "BackCompat".

-- 
Peter Klein/Umloud Untd

"Helge Preuss" <scout at hyperspace-travel.de> skrev i en meddelelse 
news:mailman.255816.1180021366.21067.typo3-english at lists.netfielders.de...
> Rob De Vries wrote:
>>>>> <?xml version="1.0" encoding="utf-8"?>
>>>>> <!DOCTYPE html
>>>>>     PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
>>>>>     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
>>>>> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
>>>>> <head>
>>>>>    <meta http-equiv="Content-Type" content="text/html;
>>>>> charset=utf-8" />
>>>>>
>>>>> ...
>>>>>
>>>>>    <meta http-equiv="Content-Type" content="text/html;
>>>>> charset=iso-8859-1" />
>>>>>
>>
>>
>>
>> If I look at your header, First thing is see is the xml prolog, do you
>> think is usefull for your website?
>>
> I don't think it is, but I don't know how to turn it off either. The
> DOCTYPE is defined in the template, but removing it did not get rid of
> the prolog. Any hints?
>> Second:
>> the first meta about your characters gets overwritten by your second one
>> (the iso)
>> One reason for this is that you forgot to strip this when using a
>> template parser and still placing on in your 'head'.
>>
> You are right about this, but regrettably this didn't solve my problem.
> The HTML header now correctly contains the line
>
> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
>
> only once, but my special chars still show up as "?".
>
> Is there anything else to try? I fear even if I solve this, the next
> problem will be flexible content elements anyway, because they are
> stored in the field tx_templavoila_flex of tt_content as XML defined as
>
> <?xml version="1.0" encoding="iso-8859-1" standalone="yes" ?> 