[TYPO3-english] Problems with high-ASCII in front end only...

[Bob]

Thanks Kay. But unfortunately not!

Our client has specified the version they need us to use (so that it's 
the same as their other sites). I think that's going to be a redundant 
requirement pretty soon, but for now we have to live with it...

Bob


On 09/10/2011 18:58, Kay Strobach wrote:
> Hi,
>
> can you please update to 4.4.11 or later first?
> http://typo3.org/download/packages/
>
> Thanks
> Kay
>
> Am 09.10.2011 17:57, schrieb Bob:
>> Thanks Kay. It's TYPO3 4.4.6.
>>
>> Looking at the rendered pages, it seems that the back-end is using
>> ISO-8859-1 while the front-end is using UTF-8.
>>
>> Since the back-end works correctly while the front-end doesn't, I
>> assumed I'd need to set the front-end character set to be ISO-8859-1
>> too. However, that gave me two characters for each of the high-ASCII
>> characters!
>>
>> Leaving the front-end as UTF-8 and changing the back-end to UTF-8 too
>> instead fixes the problem for *new* content, but any existing content
>> becomes corrupted - with questions marks in black diamonds in place of
>> the high-ASCII characters.
>>
>> Do we need to choose the latter option and re-enter all our content? Or
>> is there a better solution?
>>
>> Thanks again,
>>
>> Bob
>>
>>
>> On 09/10/2011 12:31, Kay Strobach wrote:
>>> HI,
>>>
>>> set the charset. Which TYPO3 version do you use?
>>>
>>> Regards
>>> Kay
>>>
>>> Am 09.10.2011 13:02, schrieb Bob:
>>>> I have a site in development where editors copy and paste content from
>>>> various sources. Although we can strip away the formatting, this content
>>>> often contains high-ASCII, i.e. characters such as single left quotes
>>>> and single right quotes, m-dashes and n-dashes, etc.
>>>>
>>>> These all behave perfectly in the back-end - whether pasted directly
>>>> into a field (e.g. Header) or into the RTE. But in the front-end they
>>>> render as small boxes containing the hexadecimal ASCII code. (The source
>>>> code contains these characters too, so it doesn't appear to be a browser
>>>> issue.)
>>>>
>>>> Any idea how we can resolve this?
>>>>
>>>> Thanks,
>>>>
>>>> Bob
>>>
>>>
>>
>
>