# Embedded comments dates are still not localized

**URL:** https://meta.discourse.org/t/embedded-comments-dates-are-still-not-localized/400582
**Category:** Bug
**Tags:** embedding
**Created:** [14 april 2026 om 05:15 UTC](https://meta.discourse.org/t/embedded-comments-dates-are-still-not-localized/400582 "2026-04-14T05:15:24Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![MarkoK](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/markok/32/377309_2.png) [@MarkoK](https://meta.discourse.org/u/MarkoK)
#### Post date: [14 april 2026 om 05:15 UTC](https://meta.discourse.org/t/embedded-comments-dates-are-still-not-localized/400582/1 "2026-04-14T05:15:24Z")

</div>

Hi,

this topic is based on a discussion on **[ask.discourse.com](http://ask.discourse.com)**, where we noticed what appears to be the same issue as in this older Meta topic:

[Embed: dates are not localized](https://meta.discourse.org/t/embed-dates-are-not-localized/27997)

We are using the **default Discourse embedded comments setup** as documented here, without any special customization of the embed output:

[Embed Discourse comments on another website via Javascript](https://meta.discourse.org/t/embed-discourse-comments-on-another-website-via-javascript/31963)

I tried the new fullApp method and it had finnish dates but I like the older approach here better for this site.

## What we see

The embedded comments UI is localized correctly, but the **post date text is still shown in English**.

For example, in the embed we may see:

`April 2025`

and the tooltip/title contains an English date/time such as:

`April 9, 2025, 3.31pm`

 ![kuva](https://global.discourse-cdn.com/meta/original/4X/0/a/8/0a8d3b2632a736b07f621044ff91d7228886edff.jpeg)

## Expected behavior

The embedded comment dates should follow the site or user locale instead of always appearing in English.

In our case, we would expect Finnish-localized date formatting in the default embed.

## Dirty workaround

With help of Claude I did quite dirty workaround using custom component and added javascript to embedded\_header section - I already had some css based on if the class is normal (discourse-upotus) or dark (discourse-upotus-tumma).

```plaintext
<script type="text/javascript">
const selector = '.discourse-upotus a.post-date, .discourse-upotus-tumma a.post-date';

document.querySelectorAll(selector).forEach(el => {
  const title = el.getAttribute('title');
  if (!title) return;

  const match = title.match(/(\w+) (\d+), (\d{4}),\s*([\d]+)\.([\d]+)(am|pm)/i);
  if (!match) return;

  const [, month, day, year, hours, minutes, ampm] = match;
  const date = new Date(`${month} ${day}, ${year}`);
  if (isNaN(date)) return;

  let h = parseInt(hours);
  if (ampm.toLowerCase() === 'pm' && h !== 12) h += 12;
  if (ampm.toLowerCase() === 'am' && h === 12) h = 0;
  date.setHours(h, parseInt(minutes));

  const pvm = date.toLocaleDateString('fi-FI', { day: 'numeric', month: 'long', year: 'numeric' });
  const klo = date.toLocaleTimeString('fi-FI', { hour: '2-digit', minute: '2-digit' });

  el.textContent = pvm;
  el.setAttribute('title', `${pvm} klo ${klo}`);
});
</script>

```

## Notes

- this happens with the **standard/default embed**
- no custom date formatting logic was added originally
- we are referring specifically to the date output inside the embedded comments iframe
- running latest and greatest Discourse

Could someone confirm whether this is still a known issue, and whether there is already a newer fix or related topic for it?

Thanks!