Project

General

Profile

Actions

Bug #29386

closed

L10n: locales dependency is not taken into account

Added by Xavier Perseguers over 12 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
Start date:
2011-08-31
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
4.6
PHP Version:
Tags:
Complexity:
medium
Is Regression:
Sprint Focus:

Description

Localization support comes with a dependencies between locales. By default the main language is taken as "mother language":

fr_CA -> fr
pt_BR -> pt

A user may easily define his/her own locales dependency:

$TYPO3_CONF_VARS['SYS']['localization']['locales'] = array(
        'dependencies' => array(
                'fr_CA' => array('pt_BR', 'fr'),
        ),
);

which would make 'fr_CA' depend on 'pt_BR' and then 'fr'.

These dependencies are taken into account when retrieving translations using the (new) Extension Manager but are not taken into account when retrieving a label in a given language.

It should naturally fall back on the dependency languages to search for missing label translations before using default English label.


Files

29386_v1.diff (7.09 KB) 29386_v1.diff Initial try Xavier Perseguers, 2011-08-31 16:48
29386_v2.diff (1.79 KB) 29386_v2.diff Xavier Perseguers, 2011-09-01 14:20

Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Feature #17368: Add a second language fallback in sysext/lang/Closed2007-06-08

Actions
Related to TYPO3 Core - Feature #39597: Multiple locale names for TS config.locale_allClosed2012-08-07

Actions
Actions

Also available in: Atom PDF