[Typo3-linux] Encoding problems when upgrading from 3.6.2 to 3.8

Thorsten Kahler thorsten.kahler at dkd.de
Tue Aug 9 00:11:16 CEST 2005


Hi Jan,

there's been a slight change of the charset configuration between version  
3.6 and version 3.7.

If you have set config.siteCharset in you TS setup try to change it to  
config.renderCharset.

If this doesn't help, try to submit some more information like the setting  
of $TYPO3_CONF_VARS[BE][forceCharset], or any TS setup that looks like it  
could be about charset handling.

HTH
Thorsten


On Wed, 03 Aug 2005 10:08:29 +0200, Jan <jan.hancic at ks-con.si> wrote:

> Hi list
>
> my sys admin and I have been trying to upgrade typo3 3.6.2 to 3.8 for a  
> long time now. The problem is that when we upgrade all the "special"  
> charachters are broken (&#269;&#268;žŽšŠ), and we have not changed  
> encoding of the database or any other encoding.
> The upgrade was done by a standard procedure, nothing special.
>
> Does anybody have the same probblems and has a solution? If you need any  
> more information about the system please let me know...
>
>
> - Jan (cwizo)
>
> -----------------------
> The mailing list archive is found here:
> http://typo3.org/documentation/mailing-lists/install-linux-archive/
> 				



-- 
No Subject - No Realname - No Service!
Respect the List/Newsgroup Rules!
  >> http://typo3.org/1438.0.html <<

It's not a bug - it's an undesired feature.



More information about the TYPO3-linux mailing list