[TYPO3-v4] Moving from UTF-8 as default to UTF-8 only in 4.6?
    Jigal van Hemert 
    jigal at xs4all.nl
       
    Sat Mar 19 09:38:00 CET 2011
    
    
  
Hi,
On 18-3-2011 20:06, Helmut Hummel wrote:
> I'd like to suggest to drop all support for other character encodings
> besides UTF-8 in TYPO3 4.6, at least for internal processing.
What's "internal processing"? (See also my remark below)
> For backend rendering, data storage in the database and frontend
> rendering there's no point in using other encodings.
Frontend rendering should still be possible in other encodings. TYPO3 
output may be used for different things, not only output directly to a 
browser. I know of at least one organisation which uses the output for 
further processing in a system which collects the website contents from 
various sources.
Output in various formats is possible and for further processing it may 
be required to be in other encodings that utf-8.
> The only usecase for other encodings could be sending mails,
Why? If HTML output can be utf-8, why would mail content be different? 
Or the other way around: if mail content can be in other encodings, why 
should HTML / XML / whatever output be utf-8-only?
I also agree with Xavier that utf-8 support for various databases should 
be investigated.
-- 
Kind regards / met vriendelijke groet,
Jigal van Hemert.
    
    
More information about the TYPO3-project-v4
mailing list