TYPO3 v7 has reached its end-of-life November 30th, 2018 and is not maintained by the community anymore. Looking for a stable version? Use the version switch on the top left.
There is no further ELTS support. It is recommended that you upgrade your project and use a supported version of TYPO3.
TYPO3 is designed to be fully localizable. Hard-coded strings should
thus be avoided unless there are some technical limitations (e.g. some
very early or low-level stuff where a
is not yet available).
Defining localized strings¶
Here are some rules to respect when working with labels in
Always check the existing locallang files to see if a given localized string already exists, in particular
Localized strings should never be all uppercase. If uppercase is needed, then appropriate methods should be used to transform them to uppercase.
Localized strings must not be split into several parts to include stuff in their middle. Rather use a single string with
When a localized string contains several
sprintf()markers, it must use numbered arguments (e.g.
Localized strings should never contain configuration options (e.g.
index_config:timer_frequency, which would display a link or
EXT:wizard_crpages/cshimages/wizards_1.png, which would show an image). Configuration like this does not belong in language labels, but in TypoScript.
Localized strings are not supposed to contain HTML tags, except for CSH. They should be avoided whenever possible.
Punctuation marks must be included in the localized string – including trailing marks – as different punctuation marks (e.g. "?" and "¿") may be used in various languages. Also some languages include blanks before some punctuation marks.
Once a localized string appears in a released version of TYPO3, it cannot be changed (unless it needs grammar or spelling fixes). Nor can it be removed. If the label of a localized string has to be changed, a new one should be introduced instead.
Using localized strings¶
Localized strings are displayed using the available API: Mostly
$GLOBALS['LANG']::getLL() when the corresponding locallang file
$GLOBALS['LANG']::sL() otherwise. In both these
methods, the second call parameter should be left out, unless there's a
compelling reason to set it to
TRUE (which triggers the use of