15634[!!!][BUGFIX] Localization fallback does not work in Backend
Commit message
Review
-
Code review CR +2
- Xavier Perseguers +2
- Dominique Feyer +1
- Steffen Ritter +1
-
Verified V +2
- Xavier Perseguers +2
- Dominique Feyer +1
- Steffen Ritter +1
Files 2
Review log 11
-
Xavier Perseguers commented on patch set 1 10/16/12, 12:02
(2 inline comments) Added explanation for the patch. Please see the Forge entry for an how to reproduce procedure.LocallangXmlParser.php:83parsedData is an array that should have for each label key a subkey 'source' with English version and possibly 'target' with the translation. If we are populating the 'source' element, we want to parse the ll-XML file, that's obvious because English is always present but if we are currently preparing the default language, we want to have the 'target' element to the English text, thus we systematically parse the file and push all texts to parsedDataLocallangXmlParser.php:86If we are currently reading the translated labels ($element === 'target') but not for the default language, then we want to start with an empty list of translated labels and only populate it with actually translated records. The original version populated parsedData with English labels and possibly overrided them with the real translation. But this provides a "translation" for labels in every case with a hard-coded fallback to English and we cannot then do a proper fall-back because 'target' is never empty, thus it seems that a translation always exists in the requested language. -
Xavier Perseguers commented on patch set 2 10/16/12, 12:02
Adjusted unit tests -
Xavier Perseguers uploaded patch set 2 10/16/12, 12:02
-
Steffen Ritter commented on patch set 1 10/16/12, 12:02
Verified; Looks good to me, but someone else must approve -
Steffen Ritter commented on patch set 2 10/16/12, 12:02
Verified; Looks good to me, but someone else must approve -
Mattias Nilsson commented on patch set 1 10/16/12, 12:02
Looks good to me, but someone else must approve -
Dominique Feyer commented on patch set 2 10/16/12, 12:02
Verified; Looks good to me, but someone else must approve Review yesterday evening ... but forget to click on the button. Event better with the unit test -
Mr. Jenkins commented on patch set 1 10/16/12, 12:02
Build Successful https://ci.typo3.org/job/typo3-v4-core-gerrit/6300/ : SUCCESS -
Mr. Jenkins commented on patch set 2 10/16/12, 12:02
Build Successful https://ci.typo3.org/job/typo3-v4-core-gerrit/6315/ : SUCCESS -
Xavier Perseguers commented on patch set 2 V 0 10/16/12, 12:02
by team member; Looks good to me, approved -
Xavier Perseguers merged patch set 2 10/16/12, 12:02