Form Localization
TYPO3
Show in appDescription
EXT:form translates three types of content using XLF files including form element properties, validation messages, and finisher options. There is a consistent fallback chain from most specific to most generic. Translation arguments can inject dynamic values into translated strings.
Goals
- I know how to register XLF translation files in a prototype configuration.
- I know the fallback chain for form element properties (form + element → element → type) and how to construct the corresponding keys.
- I know that validation messages are identified by numerical Extbase error codes and follow a four-level fallback chain.
- I know the two-level fallback chain for finisher options and the translation priority: YAML default → FlexForm override → XLF value.
- I know how to use %s placeholders and renderingOptions.translation.arguments to inject dynamic values into translated labels and finisher options.
- I know that HTML in translated labels must be wrapped in CDATA in the XLF file and output via <f:format.raw> in Fluid.
Maintainer
Oliver Thiele
Web Development Oliver Thiele