- Issue created by @SV
- last update
12 months ago CI aborted - last update
12 months ago Build Successful - last update
12 months ago 25,914 pass, 1,797 fail - last update
12 months ago 25,967 pass, 1,789 fail - 🇩🇪Germany lmoeni
I noticed this in my projects too. The patch fixes the issue for me.
- 🇮🇳India anandhi karnan Chennai
anandhi karnan → made their first commit to this issue’s fork.
- Merge request !9711Issue #3410052 Impossible to translate ago for timestamp_ago formatter fix → (Open) created by anandhi karnan
- 🇮🇳India anandhi karnan Chennai
I was able to reproduce this issue in Drupal 11.x.
Here are the steps I followed:
- Language and Content Translation modules are enabled.
- Multiple languages have been configured under Configuration > Regional and Language > Languages.
- Navigation to Configuration > Regional and Language > Content language and translation was done to enable translation for the content type.
- A content item with a date field was created and published.
- The content was translated into the second language.
- Navigated to the page displaying the content.
- Observed that "ago" and "in" in the timestamp format are untranslated.
I have created a merge request (MR) against Drupal 11.x. Please verify.
Thanks