[TYPO3-core] Question regarding character conversion support
michael.stucki at typo3.org
Tue Mar 19 11:12:02 CET 2013
I agree that the native implementation should be removed in the long
run. I am not sure exactly why iconv should be used, but I suggest to
keep it too. Here's an article about it:
My suggestion is to keep all code for now but mark the native
implementation as well as recode as deprecated.
Changing the default to mbstring right now seems like a good thing IMHO.
Am 19.03.2013 10:57, schrieb Christian Kuhn:
> I'm currently thinking about a "auto configure" system in the install
> tool that aims to set sane defaults / suggestions based on system
> In this process I again stumbled upon our charset conversion (formerly
> t3lib_cs) class. Currently, it implements 4 solutions: mbstring, iconv,
> recode and 'own code', defaulting to 'own code'. The default solution is
> extremely slow, some different default should be set.
> For the last couple of years I didn't see any PHP without mbstring in
> the wild. Even debian lenny (php 5.2.6) delivered with it enabled in the
> base package.
> So, my question is if we could just rely on mbstring and drop the rest?
> Is it ok if we expect mbstring to be available? Are there *common*
> setups without enabled mbstring? Question is towards usual linux
> distros, windows and mac systems, but not to handcrafted systems like
> My goal is to either fully rely on mbstring (it the quickest one), or to
> enforce mbstring or iconv (recode is broken anyway). At least I would
> like to get rid of the 'own slow code' solution. Is that ok?
> Before posting to this list, please have a look to the posting rules
> on the following websites:
> TYPO3-team-core mailing list
> TYPO3-team-core at lists.typo3.org
More information about the TYPO3-team-core