[TYPO3-dev] [Typo3-Dev] indiscriminate of i18n and languages in typo3.

Dennis Cheung hkdennis2k at gmail.com
Wed Jan 25 14:52:45 CET 2006


> > I think the question is not who will it or how long it takes.
> In fact, this is a very important question :)
I agree it is important, but nobody can do it before how long backward
compatibility will keep.

> > I see 4.0 is coming, and this is a good time to decide a border line
> > of backward compatibility. People will accept old extension not
> > compatible from 3.x to 4.x.
> So, they may not be able to upgrade to this new version if they use a
> number of popular extensions (like sr_language_selector, for example).
> Not a good idea.
Of couse, If it is going to do. They will be tested.
And new version of these extension will relese.

I don't think typo3 core should ALWAYS conside the extension.
And extension may follow the core upgrade.


> > The other thing have to consider is current website already using
> > these numbers. How to do migration.
> I think no migration and no change is needed at all. I use current
> laanguage system for quite a long time already and the only problem with
> it is the name of the default language, which is impossible to set.
> Otherwise I am pretty happy and do not want anything to be changed. I
> would better spend time on new client projects than on updating old ones
> for this change, which I believe does not add any value to the system.
It works, why change?
This is almost the same question of everyhing.
You can ask the same question to half of the updates.

I think better unicode support is one point.



Dennis




More information about the TYPO3-dev mailing list