TYPO3 Core

Carsten Bleicker wrote:

So i want to discuss, why not use the static_info_language als Sys Language and also its uid for L={uid}.
If this will be done, there can also be a TS general default setup vor languages with conditions vor each language becauls the L Parameter is fixed by static_info_language.

we then would need to ship some country data too, some basic data at least

it would also won't work if you use different colPos for different projects.

t3d should be used when importing and exporting with same structures.
using static_info_languages will bring more troubles than good, especially when it isn't a core extension.

use same sys_language table and you are fine!

mh, in my opinion a country has nothing to do with a language. especialy not with a system language.
cant figure out why it should ship with a country data. or do you mean a langIso2 code for the language like "de"?