#107436Add symfony/translation component
Description
We can utilize the symfony/translation component over our custom implementation.
Reviews 10
- main 91947[TASK] Manage localization fallback and load override files using Symfony Translator
- main 92480[BUGFIX] Resolve XLIFF files for locale with language and country code
- main 91994[TASK] Make use of proper formated XLIFF files more robust
- main 91924[TASK] Improve performance of cache warmup for translation files
- main 92094[BUGFIX] Properly throw ValueError in locallang translate handling
- main 91025[TASK] Move more LLL resolver logic into EXT:core
- main 90755[TASK] Remove "en" fallback in LocalizationFactory
- main 90658[!!!][FEATURE] Use symfony/translation for translatable labels
- main 90673[TASK] Avoid using "default" as fallback locale in LLL translation files
- main 90671[BUGFIX] Make sure LANG.loader is a map
Related issues 11
- Feature #93334New syntax for labels
- Bug #107448XliffLoader is appended to SYS/LANG/loader everytime
- Task #107451Avoid using "default" as fallback locale in LLL translation files
- Task #107461Split Label File resolving into separate class
- Task #107517Remove double runtime caches in LocalizationFactory
- Task #107686Move more code from Extbase/Form into LanguageService
- Task #108352Improve performance of Localization\LocalizationFactory::getMessageCatalogue to make cache:warmup faster
- Bug #108362LabelFileResolver::getOrderedFileResources adds every file to key en
- Task #108374Use Symfony Translator catalogue to implement localization fallbacks and overrides
- Task #108386Xliff loader should decide source vs target use by file and not by locale
- Bug #108466Properly throw ValueError in locallang translate handling