TYPO3 Core

Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/14683

Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/14683

Patch set 3 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/14683

Patch set 4 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/14683

Patch set 5 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/14683

Patch set 6 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/14683

Patch set 7 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/14683

Patch set 8 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/14683

Patch set 9 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/14683

Patch set 10 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/14683

Patch set 11 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/14683

Patch set 12 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/14683

Patch set 13 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/14683

Patch set 14 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/14683

Patch set 15 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/14683

Any reason why the lists are not using the full high in Chrome?

@Philipp: Because the lists would then be too long and complex. Additionally the used the jQuery plugin "DataTables" needs a fixed height to be correctly displayed.

Update: The table height adjusts now automatically to fit the window size.

Patch set 16 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/14683

Patch set 17 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/14683

Patch set 18 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/14683

Should we use the registry instead of the caching framework?

In my mind a registry behaves as a long-term memory and a cache like a short-term memory. Since the extension / language combinations are only deposited a short time (max. one day), they have to be stored into the cache, not the registry. And if it's stored in the registry, I have to take care myself that the entries are overwritten after a certain time with the new. Moreover, a backend user is then no longer be able to force a reload of the translation states by clearing the cache. And therefore, we should continue to use the caching framework.