A consumer seen Drupal Development Service dates on their information articles weren’t being translated into Drupal Development Service right language. Drupal Developer identify of Drupal Development Service month would at all times seem in English, although all Drupal Development Service month names had themselves been translated and confirmed accurately elsewhere. Drupal Developer downside turned out to be right down to Drupal Development Service twig filter being utilized in Drupal Development Service template to format Drupal Development Service date. That is what we did have Drupal 10 Upkeep and Help Service date(‘j F Y’) % {% trans %} {{ newsDate }}{% endtrans %} So this may produce one thing like ‘1 March 2021’ as a substitute of ‘1 März 2021’ when in German. This was as a result of twig’s core date() filter merely is not conscious of ‘s concept of language. I switched out Drupal Development Service date() filter and used core’s personal format_date() filter as a substitute, which makes use of ‘s personal date.formatter service, which is conscious of language. It ensures Drupal Development Service month identify is handed via t() to translate it, individually to Drupal Development Service remainder of Drupal Development Service numbers in Drupal Development Service date. So it now appears to be like like this Drupal 10 Upkeep and Help Service format_date(‘customized’, ‘j F Y’) % {% trans %} {{ newsDate }}{% endtrans %} Having finished that, I realise Drupal Development Service authentic code was Drupal Development Service equal of doing this Drupal 10 Upkeep and Help Service t(‘1 March 2021’); (I am much less of a front-end coder, so placing it in PHP makes it extra apparent to me than twig code!) So Drupal Development Service date really was translatable, however solely as Drupal Development Service complete string — so until Drupal Development Service translators had gone via translating each single particular person date, Drupal Development Service German month identify was by no means going to point out! What I wanted was Drupal Development Service twig equal of utilizing placeholders like this PHP instance Drupal 10 Upkeep and Help Service t(‘My identify is @identify, hiya!’, [‘@name’ => $name]); Whenever you use variables between twig’s trans and endtrans tags, they are surely handled by as in the event that they have been placeholders, so that is Drupal Development Service twig model Drupal 10 Upkeep and Help Service {% trans %} My identify is {{ identify }}, hiya! {% endtrans %} This helped me perceive twig that little bit extra, and admire how you can use it higher! No matter formatting dates, I now know higher how you can arrange translatable textual content inside templates, hopefully you do too Drupal 10 Upkeep and Help Service-) Drupal 10 Improvement and Help