History API - Date format used in the history balloon

AI
1

Different date format in tracked changes balloon

Hello,

I have a question about the date format used in the document history.

The date displayed in the History panel is shown in the format that I provide in the History API response, and it appears correctly.

However, when I open a historical version and click on a tracked deletion (or another tracked change), the balloon/tooltip displays the date in a completely different format.

For example:

  • History panel: 02/07/2026 14:30 (the format I provide)

  • Tracked change balloon: a different date format (for example, English locale or another format)

My questions are:

  1. Which date is used in the tracked change balloon?

  2. Is this date taken from the document itself instead of the History API?

  3. Is it possible to customize the date format displayed in the tracked change balloon?

  4. Is the format determined by the editor locale or is it fixed by Document Server?

Thank you!

image
image446×524 5.77 KB

Captura de tela 2026-07-02 123111
Captura de tela 2026-07-02 1231111700×117 8.33 KB

2

Hi @matheus.ribeiro, welcome to the community!

The two dates come from different places — that’s why the formats differ.

  • Version History panel — displays the created string from your History API response as-is. No formatting on our side.
  • Tracked-change balloon — reads the w:date timestamp stored on the w:ins / w:del element inside the document, and formats it using the editor locale (editorConfig.lang / region).

Reproduced on DS 9.4 with the same file opened in three languages: de → 07.07.26, 18:04, pt-br / en → 7/7/26, 6:04 PM. The Version History panel dates were byte-identical across all three, because the panel just echoes the string sent via History API.

Answers: (1) from the tracked change inside the document, (2) yes — document, not History API, (3) not currently configurable, (4) editor locale.

Closest workaround today: on your side, format the created string to match what the balloon produces for each locale (observed on our lab: pt-br → 7/7/26, 6:04 PM, de → 07.07.26, 18:04, en → same as pt-br). There’s no public spec for the balloon’s format per locale, so this is trial-and-error against your target languages.