There are two mechanisms for providing translations:
* The Symfony Translations component, injected into the Twig instances for HTML and Mail output and used in the Presenters and Controllers
* The raw messages are injected as a global Twig variable and output as JSON in the base template of the `laika` skin. Currently, the base "messages" files differ between the skins, because `laika` needs a different placeholder format, different messages and has different wording.
Most of the Symfony Translations will be obsolete once `laika` is the only skin. To make the application more performant (memory and CPU-wise) we should consolidate the translations as follows:
* Remove the Translator instance from all Presentation and controller classes. The instances translate validation errors but all client-side code ignores the messages and only uses the message keys.
* Remove all calls to `trans`from `app/mail_templates` with simple lookups. The "translations" are mostly conversions of days of the week, payment interval names and payment types.
* Remove Symfony Translation from the application (`composer.json`, `FunFunFactory`, delete `TranslationFactory`, etc)
* Delete `messages.json` in the fundraising-frontend-content repository, rename `laika-messages.json` to `messages.json`